___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
I have a number of servers with roughly 60 jails running on each of them. On
these hosts, I've had to disable the periodic security scans due to overly high
disk load when they run (which is redundant in jails anyway). However, I still
have an issue at 3:01am where the CPU is consumed by dozens
Is the problem caused by newsyslog or by the periodic scripts?
Newsyslog normally runs from cron directly, not through periodic. In
any case, here are a few suggestions:
1) Turn on cron jitter, as you suggested. Even if 60s isn't enough,
it can't hurt.
2) Try gz compression instead of xz compress
The biggest offender that I see is /usr/local/etc/periodic/daily/411.pkg-backup
During the high CPU event, my process list contains hundreds of these:
83811 - RJ 0:03.42 xz -c
83816 - S 0:00.02 /usr/local/sbin/pkg shell .dump
83818 - SJ 0:00.
Adding something like:
'sleep $(( $(sysctl -n security.jail.param.jid) * 15 )) && '
in front of more resource-intensive commands in /etc/crontab can reliably
spread out the load from a larger number of jails.
(But if you start and stop jails frequently enough to spread out the
current list o
Dustin Wenz wrote on 2017/02/16 22:47:
I have a number of servers with roughly 60 jails running on each of them. On
these hosts
60 is way more than we have on our jailers. Daily / security scripts are
very disk IO intensive so we end up with changing time in /etc/crontab
in each jail for per
What about:
@daily sleep ${RANDOM:0:2}m ; /some/cron/job.sh
Which gives you a jitter of up to 99 minutes.
Cheers,
Guy
-Original Message-
From: owner-freebsd-sta...@freebsd.org
[mailto:owner-freebsd-sta...@freebsd.org] On Behalf Of Miroslav Lachman
Sent: 17 February 2017 01:20
To: Dust
