Bug#405782: [xserver-xorg] "dpkg-reconfigure xserver-xorg" stuck

2007-01-06 Thread Boris Dores 
On Sat, Jan 06, 2007 at 06:04:54PM (GMT+0100), Brice Goglin wrote:
> Ok great, thanks. I have reproduced the problem with a chroot and a
> locally-nfs-mounted /tmp. The problem is caused by /usr/bin/dexconf not
> closing a redirection before exiting. File descriptor 4 was kept open,
> pointing to /tmp/dexconf-tmp-/DRI. Adding exec 4<&- solves the
> problem. Patch attached.

  I confirm. Works fine now.
  Thanks a lot.

-- 
Boris Dorès

Bug#405782: [xserver-xorg] "dpkg-reconfigure xserver-xorg" stuck

2007-01-06 Thread Boris Dores 
Package: xserver-xorg
Version: 1:7.1.0-9
Severity: grave

  Hi everyone,

  It would seem that "dpkg-reconfigure xserver-xorg" never succeeds to
update /etc/X11/xorg.conf any more.

  At the end of the questions part, the following is displayed on the
console :

xserver-xorg postinst warning: overwriting possibly-customised configuration
   file; backup in /etc/X11/xorg.conf.20070106082628
rm: cannot remove directory `/tmp/dexconf-tmp-6475': Directory not empty.
xserver-xorg postinst warning: error while preparing new Xorg X server
   configuration file in /etc/X11/xorg.conf.dpkg-new; not attempting to
   update existing configuration

  However, /tmp/dexconf-tmp-* is always empty (afterwards at
least), and manually running dexconf generates a perfectly working
/etc/X11/xorg.conf (even though it displays the same "Directory not
empty" warning).

  I tried the same procedure on 4 newly installed hosts (debootstrap of
etch to a nfsroot), and again after manually running dexconf, it always
fails.

  Thanks.
  Best regards.

-- 
Boris Dorès

Bug#384943: start/stop zoneserver

2006-10-09 Thread Boris Dores 
On Mon, Oct 09, 2006 at 06:03:07PM (GMT-0300), Kai Hendry wrote:
> http://hendry.iki.fi/debian/unstable/maradns_1.2.12.03-1_i386.changes
> 
> Ok, I have prepared a test release. 
> 
> Boris could you please, pretty please, check test it out? :)

  Looks very good to me (package rebuilt and tested on sarge, as usual).

  Thanks !

-- 
Boris Dorès

Bug#384943: start/stop zoneserver

2006-10-09 Thread Boris Dores 
On Sun, Oct 08, 2006 at 09:07:53PM (GMT-0300), Kai Hendry wrote:
> I should have thought about it a little harder. Check out:
> http://hendry.iki.fi/debian/unstable/maradns_1.2.12.02-3.diff.gz

  Wrong again, but this time it's entirely my fault: "ps" right aligns
pids, so we cannot use "cut" (my patch only worked for pids between 1000
and ).

  The attached patch made against 1.2.12.02-3 (ready to be applied this
time) fixes this issue and also adds the following:
- it fixes the file layout (tabs which were converted to spaces in
  previous patches)
- it doesn't fail or even output a warning anymore if
  "(maradns|zoneserver) stop" is run multiple times (by removing the pid
  files, adding "--oknodo" in zoneserver and adapting my previous patch)

  Does it seem ok to you ?

  Thanks.

-- 
Boris Dorès
diff -r maradns-1.2.12.02-3/debian/maradns.init 
maradns-1.2.12.02/debian/maradns.init
48a49
>   rm -f /var/run/$SERVERNAME.pid
diff -r maradns-1.2.12.02-3/debian/maradns.zoneserver.init 
maradns-1.2.12.02/debian/maradns.zoneserver.init
40c40
<--exec $DAEMON -- -f $rcfile &1 | logger -p daemon.notice 
-t $SERVERNAME 2>/dev/null &
---
>   --exec $DAEMON -- -f $rcfile &1 | logger -p 
> daemon.notice -t $SERVERNAME 2>/dev/null &
53,55c53,61
< ps h --ppid `cat /var/run/$SERVERNAME.pid` | cut -d ' ' -f 2 | xargs 
kill
<   start-stop-daemon --stop -m --quiet --pidfile 
/var/run/$SERVERNAME.pid \
<   $DAEMON
---
>   PIDFILE=/var/run/$SERVERNAME.pid
>   if [ -f $PIDFILE ]; then
>   CHILDPROCESSES=`cat $PIDFILE | xargs ps h --ppid | awk 
> '{print $1}' | xargs`
>   if [ "$CHILDPROCESSES" ]; then
>   kill $CHILDPROCESSES
>  fi
>   fi
>   start-stop-daemon --oknodo --stop -m --quiet --pidfile $PIDFILE 
> $DAEMON
>   rm -f $PIDFILE

Bug#384943: start/stop zoneserver

2006-10-08 Thread Boris Dores 
On Sun, Oct 08, 2006 at 07:49:46PM (GMT-0300), Kai Hendry wrote:
> Could you please test:
> http://hendry.iki.fi/debian/unstable/maradns_1.2.12.02-2.diff.gz

  The line "ps h --ppid ..." should have been added in the "stop" case,
before line 53, not before line 39 (and tabs became spaces when I pasted
the patch, but that's a detail). I should have attached the patch
instead of placing it inline, would have been easier, sorry.

> Greetings from Buenos Aires,

  Must be sunny, lucky you :)

-- 
Boris Dorès

Bug#384943: start/stop zoneserver

2006-10-08 Thread Boris Dores 
  Hi everyone,

  Sorry for taking so long to reply, I am quite busy these days...

On Thu, Sep 07, 2006 at 11:43:46PM (GMT+), Sam Trenholme wrote:
> All zoneserver processes are correctly killed when using the upstream
> zoneserver process killer.  The script in question has this bit of
> code:
> 
> ps -ef | awk '{print $2":"$8}' | grep zoneserver | grep -v $$ | \
>   cut -f1 -d: | xargs kill > /dev/null 2>&1
> 
> English translation: Send a term signal to all processes running on 
> the machine with the name zoneserver

  So Kai, what would you think about adding the following line in
/etc/init.d/zoneserver to close this issue until version 1.2.13 is out ?
(if I understood Sam correctly, version 1.2.13 won't be released before
a little while, and at least not in time for etch I suppose)

--- zoneserver.1.2.12.022006-10-08 19:20:28.063770554 +0200
+++ zoneserver  2006-10-08 19:11:07.003991657 +0200
@@ -50,6 +50,7 @@
 if grep -q -i "^\(zone_transfer_acl\|tcp_convert_server\)" $rcfile; 
then
SERVERNAME=`echo $rcfile | sed 's/\//_/g;s/^_*//;' | awk -F. 
'{print $NF}'`
SERVERNAME=zoneserver.$SERVERNAME
+   ps h --ppid `cat /var/run/$SERVERNAME.pid` | cut -d ' ' -f 2 | 
xargs kill
start-stop-daemon --stop -m --quiet --pidfile 
/var/run/$SERVERNAME.pid \
$DAEMON
 fi

-- 
Boris Dorès