Bug#453123: debconf interaction not closed

2008-11-10 Thread Ferenc Wagner
man debconf-devel (on an Etch system) says: If your postinst launches a daemon, make sure you tell debconf to STOP at the end, since debconf can become a little confused about when your postinst is done otherwise. So why not follow good advice? Adding db_stop to the end of

Bug#453123: [Pkg-net-snmp-devel] Bug#453123: debconf interaction not closed

2008-11-10 Thread Jochen Friedrich
forcemerge 391203 453123 thanks Hi Ferenc, Of course not leaking file descriptors is a good practice, but it isn't the responsibility of all the daemons of the world to close all possible file descriptors their parent might have leaked to them (see for example

Bug#453123: [Pkg-net-snmp-devel] Bug#453123: debconf interaction not closed

2008-11-10 Thread Ferenc Wagner
Of course not leaking file descriptors is a good practice, but it isn't the responsibility of all the daemons of the world to close all possible file descriptors their parent might have leaked to them (see for example http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=486826#37). I don't agree