Problem with LOGIN and cron

[Pawel Jakub Dawidek]

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 at 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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-rc/attachments/20120113/96acf29a/attachment.pgp