Am 2018-07-27 17:39, schrieb marc:
Either keep an ssh session open indefinitely and
then do an "echo /proc/*" when the problem occurs

Or stop cron and see if the problem goes away. A poorly written cronjob
seems to be the most likely cause of an accidental fork bomb. An
"ulimit -u 100" in a problematic script might help to contain the
problem.

Also: if you post your problem to the list, try to keep posting
the rest of the thread there too, so that others can benefit from
any solution.

Good luck solving it

Thanks for the hints. Yesterday I purged network-manager, dbus, anacron and some other crap, left over from the original Odroid install image and unneccessary on a headless server. It's now running 24 hours without the problem. Looks good at the moment now.

Jochen
_______________________________________________
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng

Reply via email to