Date: Tue, 3 Dec 2013 11:44:40 +0000 From: dgmm <freebsd01@dgmm.net> To: freebsd-questions@freebsd.org Subject: Re: System reboots ~3am during daily periodic 450.status-security run Message-ID: <201312031144.40570.freebsd01@dgmm.net> In-Reply-To: <CALfReycK0hWugawE903iAk7hGDcrS=K0ezpbAe4xUjHEhj5mxA@mail.gmail.com> References: <201312012352.01075.freebsd01@dgmm.net> <201312030924.10969.jmc-freebsd2@milibyte.co.uk> <CALfReycK0hWugawE903iAk7hGDcrS=K0ezpbAe4xUjHEhj5mxA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tuesday 03 December 2013 09:48:04 krad wrote: > or you could use the @reboot option, that would mean it always runs at > crons start, which may not be what you want, Yes, that was my first thought but the overheads at boot time might be inconvenient although I'll try it to find out. > Alternatively you could cron > your script every x period and get it to touch a file in /tmp, if its > younger than x, the script terminates, if not you retouch and carry on. > More messy but no extra software. That's a good thought. > With regards to partition layouts, I think sticking everything on / is > crazy, and is geared up more for novice users who want flexibility. However > if you want flexibility you should really use zfs in my opinion if at all > possible. On a production ufs system I always keep the / fs purely read > only apart from system updates. If I want to save mountpoints, i will drop > /usr and /usr/local, but never /var /tmp, and /home zfs as boot drive was still reletively complex to set up, in my mind at least, when I built this box and yes, I also thought "everything on root" possibly wasn't the right way to go, but I thought I'd give it a try since the handbook recommended it. /home is seperate, but next build will have seperate mount points, whether zfs or ufs :-) > On 3 December 2013 09:24, Mike Clarke <jmc-freebsd2@milibyte.co.uk> wrote: > > On Monday 02 Dec 2013 20:40:11 dgmm wrote: > > > This does bring to mind something I'd not previously thought of. > > > Except for the rare times I leave a job running overnight, periodic > > > never runs. I'll have a to make a decision on what to do about that. > > > > Consider sysutils/anacron > > > > Anacron can be used to execute commands periodically, with a frequency > > specified in days. Unlike cron(8), it does not assume that the machine > > is running continuously. Hence, it can be used on machines that aren't > > running > > 24 hours a day, to control daily, weekly, and monthly jobs that are > > usually controlled by cron. > > > > -- > > Mike Clarke > > _______________________________________________ > > freebsd-questions@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > > To unsubscribe, send any mail to " > > freebsd-questions-unsubscribe@freebsd.org" > > _______________________________________________ > freebsd-questions@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to > "freebsd-questions-unsubscribe@freebsd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201312031144.40570.freebsd01>