Bug#924551: startup script affects bind running inside a container

2019-07-09 Thread Harald Dunkel
Obviously the list of processes (as produced by ps -ef, pgrep, whatever) does not provide sufficient information to find the right process id to send a signal to. Additional information has to be included. AFAICS thats the PID file in /run. If this file doesn't exist, then the only reasonable ass

Bug#924551: startup script affects bind running inside a container

2019-07-07 Thread Bernhard Schmidt
Control: tags -1 + moreinfo Am 14.03.19 um 11:39 schrieb Harald Dunkel: Hi, > "/etc/init.d/bind9 stop" kills a named running in a LXC > container, if there is no named running on the host. Same > for "restart". Sample session (on the host): > > # ps -ef | grep named > opensmt+  234963    3421 

Bug#924551: startup script affects bind running inside a container

2019-03-14 Thread Harald Dunkel
Package: bind9 Version: 1:9.10.3.dfsg.P4-12.3+deb9u4 "/etc/init.d/bind9 stop" kills a named running in a LXC container, if there is no named running on the host. Same for "restart". Sample session (on the host): # ps -ef | grep named opensmt+ 2349633421 0 11:14 ?00:00:00 /usr/sbin/