[resending to the correct address; lxc-users@ bounced] On 20.01.2011 19:09, Jean-Philippe Menil wrote: > Hi, > > i've just found something that is being anoying me: > > when i restart the snmpd daemon on my host, it shutdown the snmpd daemon > on my container.
This, and many similar cases, happens - most likely - due to bugs in system startup scripts on the host. Host sees all processes running in the system, including all the processes named "snmpd" running in all LXC containers. What the startup script should do is to kill/restart only the _proper_ process, - the one who's pid is listed in host's /var/run/snmpd.pid. > The host is a debian squeeze, with a 2.6.37 kernel, and the version > 0.7.3-1 packaged from debian. > Guest are debian squeeze too. [...] > I see that, in debian, the init.d script for snmp contains the following > stop) > echo -n "Stopping network management services:" > start-stop-daemon --quiet --stop --oknodo --exec /usr/sbin/snmpd > > So it's not based on the pid of the process, but on the executable file. Here we go. > Is there a solution to bypass this problem, that i'm not aware of? See above. And file a bugreport against debian snmpd startup script. It is actually (albiet very low) security issue too: the startup script will kill unrelated user processes named "snmpd" too. /mjt ------------------------------------------------------------------------------ Protect Your Site and Customers from Malware Attacks Learn about various malware tactics and how to avoid them. Understand malware threats, the impact they can have on your business, and how you can protect your company and customers by using code signing. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Lxc-devel mailing list Lxc-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-devel
