>>> Add an option to cron to check lastlog and if within 5 or 10 minutes
>>> of the last reboot, then call run_reboot_jobs().
>>
>> Depending on timestamps might be okay as a temporary quick-and-dirty
>> workaround, but there is likely to be a case where it will also do the
>> wrong thing. ??What
On Sat, Nov 26, 2011 at 02:58:46PM -0500, APseudoUtopia wrote:
> On Fri, Nov 25, 2011 at 4:36 PM, Christian Kastner wrote:
> > On 2011-11-25 08:02, Jason Hellenthal wrote:
> >> So with that said... is there a way we could actually make this run
> >> @reboot only ?
> > Debian's cron[0] and Fedora'
On Fri, Nov 25, 2011 at 4:36 PM, Christian Kastner wrote:
> Hi,
>
> On 2011-11-25 08:02, Jason Hellenthal wrote:
>> So with that said... is there a way we could actually make this run @reboot
>> only ?
>
> Debian's cron[0] and Fedora's cronie[1] have solved this by touching a
> file on first star
On Fri, Nov 25, 2011 at 12:53:43PM -0500, Dieter BSD wrote:
> The system doesn't go multiuser until the rc jobs complete,
> even if you attempt to background them with '&'. ??This can be
> a problem with long running jobs. ??I started using cron @reboot
> for this reason.
>
> I haven't run into
On Sat, Nov 26, 2011 at 04:44:20PM +0100, Stefan Bethke wrote:
> Am 26.11.2011 um 11:54 schrieb Chris Rees:
>
> > PLEASE let's not go down the route of that. How long? What if I need to
> > restart cron shortly after boot? What if boot takes longer?
>
> Plus "interesting" time changes during
On Sat, Nov 26, 2011 at 07:05:00PM +, Chris Rees wrote:
> On 26 November 2011 19:00, Jason Hellenthal wrote:
> > On Sat, Nov 26, 2011 at 06:43:38AM +0100, Michael Ross wrote:
> >> Am 26.11.2011, 06:11 Uhr, schrieb Jason Hellenthal :
> >> > On Fri, Nov 25, 2011 at 10:36:40PM +0100, Christian
On 26 November 2011 19:00, Jason Hellenthal wrote:
> On Sat, Nov 26, 2011 at 06:43:38AM +0100, Michael Ross wrote:
>> Am 26.11.2011, 06:11 Uhr, schrieb Jason Hellenthal :
>> > On Fri, Nov 25, 2011 at 10:36:40PM +0100, Christian Kastner wrote:
>> >> Hi,
>> >>
>> >> On 2011-11-25 08:02, Jason Hellen
On Sat, Nov 26, 2011 at 06:43:38AM +0100, Michael Ross wrote:
> Am 26.11.2011, 06:11 Uhr, schrieb Jason Hellenthal :
>
> >
> >
> > On Fri, Nov 25, 2011 at 10:36:40PM +0100, Christian Kastner wrote:
> >> Hi,
> >>
> >> On 2011-11-25 08:02, Jason Hellenthal wrote:
> >> > So with that said... is the
Am 26.11.2011 um 11:54 schrieb Chris Rees:
> PLEASE let's not go down the route of that. How long? What if I need to
> restart cron shortly after boot? What if boot takes longer?
Plus "interesting" time changes during boot due to ntpdate/ntpd.
--
Stefan BethkeFon +49 151 14070811
_
Am 26.11.2011, 06:11 Uhr, schrieb Jason Hellenthal :
On Fri, Nov 25, 2011 at 10:36:40PM +0100, Christian Kastner wrote:
Hi,
On 2011-11-25 08:02, Jason Hellenthal wrote:
> So with that said... is there a way we could actually make this run
@reboot only ?
Debian's cron[0] and Fedora's cron
On 26 November 2011 07:25, Doug Barton wrote:
> On 11/25/2011 23:08, Cy Schubert wrote:
>> If average users really do need to run something at boot they're likely
>> running some kind of service
>
> I don't think second-guessing what users are doing is going to be a
> useful exercise here. I will
On 11/25/2011 23:08, Cy Schubert wrote:
> If average users really do need to run something at boot they're likely
> running some kind of service
I don't think second-guessing what users are doing is going to be a
useful exercise here. I will also tell you flat out that this is not the
only use fo
In message , Warren Block
writ
es:
> This message is in MIME format. The first part should be readable text,
> while the remaining parts are likely unreadable without MIME-aware tools.
>
> ---902635197-1839580335-1322243619=:80691
> Content-Type: TEXT/PLAIN; charset=UTF-8; format=flowed
> Co
On Fri, Nov 25, 2011 at 10:36:40PM +0100, Christian Kastner wrote:
> Hi,
>
> On 2011-11-25 08:02, Jason Hellenthal wrote:
> > So with that said... is there a way we could actually make this run @reboot
> > only ?
>
> Debian's cron[0] and Fedora's cronie[1] have solved this by touching a
> file
On 11/25/2011 16:16, Tim Kientzle wrote:
>
> On Nov 25, 2011, at 2:08 PM, Doug Barton wrote:
>
>> On 11/25/2011 08:09, Cy Schubert wrote:
>>> You're right. Sorry. It was late, after a long night of O/T.
>>
>> Actually I was in the same boat, which is why my reply was even grumpier
>> than usual,
On Nov 25, 2011, at 2:08 PM, Doug Barton wrote:
> On 11/25/2011 08:09, Cy Schubert wrote:
>> You're right. Sorry. It was late, after a long night of O/T.
>
> Actually I was in the same boat, which is why my reply was even grumpier
> than usual, sorry.
>
> Meanwhile I like your suggestion of hav
Hi,
On 2011-11-25 08:02, Jason Hellenthal wrote:
> So with that said... is there a way we could actually make this run @reboot
> only ?
Debian's cron[0] and Fedora's cronie[1] have solved this by touching a
file on first startup and running @reboot only when this file does not
yet exist.
Note t
On 11/25/2011 08:09, Cy Schubert wrote:
> You're right. Sorry. It was late, after a long night of O/T.
Actually I was in the same boat, which is why my reply was even grumpier
than usual, sorry.
Meanwhile I like your suggestion of having cron check that it's within
$time_period before running the
On Fri, 25 Nov 2011, Tom Evans wrote:
On Fri, Nov 25, 2011 at 4:09 PM, Cy Schubert wrote:
Changing the behaviour by default would change the semantics of @reboot,
altering the behaviour of cron jobs which rely on the brokenness. What if
both behaviours are wanted on the same system? Unlikely,
The system doesn't go multiuser until the rc jobs complete,
even if you attempt to background them with '&'. This can be
a problem with long running jobs. I started using cron @reboot
for this reason.
I haven't run into the problem since I've never needed to run
/etc/rc.d/cron restart.
> Add an
On Fri, Nov 25, 2011 at 8:37 AM, Tom Evans wrote:
> On Fri, Nov 25, 2011 at 4:09 PM, Cy Schubert
> wrote:
> > Changing the behaviour by default would change the semantics of @reboot,
> > altering the behaviour of cron jobs which rely on the brokenness. What
> if
> > both behaviours are wanted o
On Fri, Nov 25, 2011 at 4:09 PM, Cy Schubert wrote:
> Changing the behaviour by default would change the semantics of @reboot,
> altering the behaviour of cron jobs which rely on the brokenness. What if
> both behaviours are wanted on the same system? Unlikely, as I can't see
> anyone relying on
In message <4ecf54f1.50...@freebsd.org>, Doug Barton writes:
> On 11/25/2011 00:12, Cy Schubert wrote:
> > In message <2025070241.ga7...@dataix.net>, Jason Hellenthal writes:
> >> List,
> >>
> >> When using @reboot with cron you expect your proccesses to always start wh
> en
> >> the system bo
On Fri, Nov 25, 2011 at 7:02 AM, Jason Hellenthal wrote:
>
> List,
>
> When using @reboot with cron you expect your proccesses to always start when
> the system boots up and only when the system boots. But long after the system
> in question had been booted, my @reboot processes ran again! after
On 11/25/2011 00:29, Stefan Bethke wrote:
> I didn't even know cron had this feature. Why wouldn't you add custom rc.d
> scripts for these tasks, or add the commands to rc.local?
Personally I find this feature very useful for unprivileged users to do
their own stuff at startup.
Doug
--
On 11/25/2011 00:12, Cy Schubert wrote:
> In message <2025070241.ga7...@dataix.net>, Jason Hellenthal writes:
>> List,
>>
>> When using @reboot with cron you expect your proccesses to always start when
>> the system boots up and only when the system boots. But long after the system
>> in ques
Am 25.11.2011 um 08:02 schrieb Jason Hellenthal:
> When using @reboot with cron you expect your proccesses to always start when
> the system boots up and only when the system boots. But long after the system
> in question had been booted, my @reboot processes ran again! after a
> (/etc/rc.d/cro
In message <2025070241.ga7...@dataix.net>, Jason Hellenthal writes:
> List,
>
> When using @reboot with cron you expect your proccesses to always start when
> the system boots up and only when the system boots. But long after the system
> in question had been booted, my @reboot processes ran
List,
When using @reboot with cron you expect your proccesses to always start when
the system boots up and only when the system boots. But long after the system
in question had been booted, my @reboot processes ran again! after a
(/etc/rc.d/cron restart). This is normally fine and dandy until
29 matches
Mail list logo
