Re: Any particular reason we don't have sshd oomprotected by default?
Cy Schubert <[email protected]>
| Newsgroups | gmane.os.freebsd.architechture |
|---|---|
| Message-ID | <[email protected]> |
In message <[email protected]>, Philip Paeps wri tes: > On 2023-11-09 16:09:00 (+0800), Robert Clausecker wrote: > > I encountered the same issue a while ago, leaving my system in a > > vegetative state. I would propose to add syslogd and cron to the > > list. Syslogd because when it dies and you don't notice, you may go > > for > > a long time without syslogs, cron because a dead cron means no > > housekeeping tasks happen, including some which the administrator may > > have intended to fix an issue causing an OOM condition (e.g. > > periodically restarting services with known memory leaks or cleaning > > tmpfs-based file systems). > > In my experience, cron is more often the cause of an OOM condition than > a help to making it stop. :-) Would that be cron or something that cron has started? -- Cheers, Cy Schubert <[email protected]> FreeBSD UNIX: <[email protected]> Web: https://FreeBSD.org NTP: <[email protected]> Web: https://nwtime.org e^(i*pi)+1=0