Date: Fri, 13 Jan 2012 20:52:48 +0100 From: Pawel Jakub Dawidek <pjd@FreeBSD.org> To: David O'Brien <obrien@freebsd.org> Cc: freebsd-rc@freebsd.org Subject: Re: Problem with LOGIN and cron Message-ID: <20120113195245.GE1694@garage.freebsd.pl> In-Reply-To: <20120113192810.GA87287@dragon.NUXI.org> References: <20120112234424.GA41056@dragon.NUXI.org> <CADLo838ygJPVCdkai-Ui6eRKt4cZ3tX9Xj67KxmRKc10tLcDag@mail.gmail.com> <20120113192810.GA87287@dragon.NUXI.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --]
On Fri, Jan 13, 2012 at 11:28:10AM -0800, David O'Brien wrote:
> On Fri, Jan 13, 2012 at 07:11:01AM +0000, Chris Rees wrote:
> > On 12 January 2012 23:44, David O'Brien <obrien@freebsd.org> wrote:
> > > 'LOGIN' states:
> > > This is a dummy dependency to ensure user services such as xdm,
> > > inetd, cron and kerberos are started after everything else, in
> > > case the administrator has increased the system security level
> > > and wants to delay user logins until the system is (almost) fully
> > > operational.
> > >
> > > So based on that, 'securelevel' should have:
> > > +# REQUIRE: sysctl
> > > +# BEFORE: LOGIN
> > > Otherwise a cronjob could act against securelevel=1+ for a short peroid
> > > of time.
> >
> > Hm, but what if I have an @reboot line in crontab, that relies on
> > securelevel <1?
>
> Can you give an example?
>
> $ man cron | grep @reboot
> {empty}
> $ man crontab | grep @reboot
> {empty}
$ man 5 crontab | grep @reboot
@reboot Run once, at startup.
--
Pawel Jakub Dawidek http://www.wheelsystems.com
FreeBSD committer http://www.FreeBSD.org
Am I Evil? Yes, I Am! http://yomoli.com
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (FreeBSD)
iEYEARECAAYFAk8Qi40ACgkQForvXbEpPzROgQCfX7E9VS2mXdTMZ4pMpqbsvdGc
pG4AoN6PsF2Gb/zJBhlVouyQTCNrozd0
=xzL4
-----END PGP SIGNATURE-----
help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120113195245.GE1694>