[Redhat-s390-list] kernel-2.4.0-0.99.20 breaks crond/crontab?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi...

We have a machine installed from s/390-Rawhide, on which I have been experiencing strange behaviour.
It was initially installed with the kernel-BOOTvrdr-2.2.18-0.16, and that worked fine.
But I decided to test the kernel-BOOTvrdr-2.4.0-0.99.20 so I rebuilt it from the src.rpm ("rpm -bb kernel-2.4.0-0.99.20.src.rpm"
Booting the new kernel everything worked fine, or so it seemed...

After leaving the system running for a weekend I tried to log on to it using SSH, but could not connect,
so I logged on using the from the VM/ESA side, and what I found was a couple of hundred CROND processes
(I could not count them before the system locked up, probably since it was running low on resources).
I figured there would be a bug in crond, and installed the vixie-cron-3.0.1-38.5.2 (rebuilt from src.rpm), but that did not help...

What I finally did to avoid the problem was to comment out the "rmmod -as" from "/etc/cron.d/kmod".
This stopped the problem from occuring, but I think there might be a problem here somewhere so maybe it should be looked in to.

	/John Fogelvik


----
	John Fogelvik
	Ericsson Internet Support
	Västberga, Sweden
	Ericsson Process & Application Consulting
	John.Fogelvik@Ericsson.COM




[Index of Archives]     [Fedora General Discussion]     [LKML]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Linux s390]     [Gimp]     [Yosemite News]

  Powered by Linux