RE: [suse-security] lpd kills xdm and other useful processes + network failure on boot
just curious : did you update SuSE packages with patch rpm's for a long time without rebooting these workstations ? -----Message d'origine----- De : Mike Rose [mailto:mr349@cam.ac.uk] Envoyé : jeudi 2 décembre 2004 14:51 À : suse-security@suse.com Objet : [suse-security] lpd kills xdm and other useful processes + network failure on boot Hi, I know both of these things are slighly off topic, but I have heard nothing from Suse about the network failure on boot, and I am wondering if anyone else has hit the lpd problem: We just replaced /etc/printcap (trivial change) on a bunch of Suse9.1 workstations, restarted lpd (we are using the Suse provided lprng) and about half of the workstations were left in a bizarre state where printing via lpd left all the print jobs on the local computer and did not send them on, so to speak. Hmm, OK let's try and restart lpd on a computer that has this lpd problem: /etc/init.d/lpd restart results in xdm being killed along with a few other rather critical processes. This action logs me off the computer (as root) and the person who "was" using the console. Only a reboot will suffice. Most of the computers seem to have been fixable using: killall -KILL lpd; /etc/init.d/lpd start http://www.lprng.com/ thinks that: (For LPRng-3.8.28) is the latest version, whereas lprng-3.8.25-37 is what Suse provide in 9.1 between 3.8.25 and 3.8.28 there is a fix for a memory leak..... Also our process accouting logs seem to show lpd getting into a state where it is creating a new process every 10 seconds. Approximately 1 out of 30 boots of Suse 9.1 result the network service not starting during boot. After the boot it is always possible to start it ( /etc/init.d.network start) successfully, but not much use with other services relying upon it. Another boot of the same computer and everything is always fine, so no repeatiblity to speak of - yuk. Anyone else seen this? Mike Rose -- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
Nope. There was a kernel patch within the last month so computers had to be rebooted for that. I've just applied the latest kernel patch so another round of reboots should be due. curious: why do you ask, as Linux should not require a reboot for sofware changes to take effect unless they are somewhat kernel related, no? Mike Rose On Thu, 2 Dec 2004, Theytaz Antoine wrote:
just curious : did you update SuSE packages with patch rpm's for a long time without rebooting these workstations ?
-----Message d'origine----- De : Mike Rose [mailto:mr349@cam.ac.uk] Envoyé : jeudi 2 décembre 2004 14:51 À : suse-security@suse.com Objet : [suse-security] lpd kills xdm and other useful processes + network failure on boot
Hi,
I know both of these things are slighly off topic, but I have heard nothing from Suse about the network failure on boot, and I am wondering if anyone else has hit the lpd problem:
We just replaced /etc/printcap (trivial change) on a bunch of Suse9.1 workstations, restarted lpd (we are using the Suse provided lprng) and about half of the workstations were left in a bizarre state where printing via lpd left all the print jobs on the local computer and did not send them on, so to speak.
Hmm, OK let's try and restart lpd on a computer that has this lpd problem: /etc/init.d/lpd restart results in xdm being killed along with a few other rather critical processes. This action logs me off the computer (as root) and the person who "was" using the console. Only a reboot will suffice.
Most of the computers seem to have been fixable using: killall -KILL lpd; /etc/init.d/lpd start
http://www.lprng.com/ thinks that: (For LPRng-3.8.28) is the latest version, whereas lprng-3.8.25-37 is what Suse provide in 9.1
between 3.8.25 and 3.8.28 there is a fix for a memory leak.....
Also our process accouting logs seem to show lpd getting into a state where it is creating a new process every 10 seconds.
Approximately 1 out of 30 boots of Suse 9.1 result the network service not starting during boot. After the boot it is always possible to start it ( /etc/init.d.network start) successfully, but not much use with other services relying upon it. Another boot of the same computer and everything is always fine, so no repeatiblity to speak of - yuk.
Anyone else seen this?
Mike Rose
-- Check the headers for your unsubscription address For additional commands, e-mail: suse-security-help@suse.com Security-related bug reports go to security@suse.de, not here
participants (2)
-
Mike Rose -
Theytaz Antoine