GNU bug report logs -
#40499
mcron missing initial directories?
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 40499 in the body.
You can then email your comments to 40499 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-guix <at> gnu.org
:
bug#40499
; Package
guix
.
(Tue, 07 Apr 2020 22:36:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Danny Milosavljevic <dannym <at> scratchpost.org>
:
New bug report received and forwarded. Copy sent to
bug-guix <at> gnu.org
.
(Tue, 07 Apr 2020 22:36:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
$ crontab -e
In unknown file:
0 (copy-file "/tmp/crontab.10313" "/var/cron/tabs/dannym")
ERROR: In procedure copy-file:
In procedure copy-file: No such file or directory
/var/cron doesn't exit either. Maybe we should automatically create /var/cron ?
[Message part 2 (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#40499
; Package
guix
.
(Wed, 08 Apr 2020 09:56:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 40499 <at> debbugs.gnu.org (full text, mbox):
Hi Danny,
Danny Milosavljevic <dannym <at> scratchpost.org> skribis:
> $ crontab -e
>
> In unknown file:
> 0 (copy-file "/tmp/crontab.10313" "/var/cron/tabs/dannym")
>
> ERROR: In procedure copy-file:
> In procedure copy-file: No such file or directory
>
> /var/cron doesn't exit either. Maybe we should automatically create /var/cron ?
Yes, this should be done in an activation snippet.
Ludo’.
Information forwarded
to
bug-guix <at> gnu.org
:
bug#40499
; Package
guix
.
(Thu, 09 Apr 2020 20:41:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 40499 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Wed, Apr 08, 2020 at 11:55:05AM +0200, Ludovic Courtès wrote:
> Hi Danny,
>
> Danny Milosavljevic <dannym <at> scratchpost.org> skribis:
>
> > $ crontab -e
> >
> > In unknown file:
> > 0 (copy-file "/tmp/crontab.10313" "/var/cron/tabs/dannym")
> >
> > ERROR: In procedure copy-file:
> > In procedure copy-file: No such file or directory
> >
> > /var/cron doesn't exit either. Maybe we should automatically create /var/cron ?
>
> Yes, this should be done in an activation snippet.
>
Should this be part of a crontab service or does the mere existence of
the files allow cron tasks to start working?
--
Efraim Flashner <efraim <at> flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[signature.asc (application/pgp-signature, inline)]
Information forwarded
to
bug-guix <at> gnu.org
:
bug#40499
; Package
guix
.
(Fri, 10 Apr 2020 08:28:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 40499 <at> debbugs.gnu.org (full text, mbox):
Hi,
Efraim Flashner <efraim <at> flashner.co.il> skribis:
> On Wed, Apr 08, 2020 at 11:55:05AM +0200, Ludovic Courtès wrote:
>> Hi Danny,
>>
>> Danny Milosavljevic <dannym <at> scratchpost.org> skribis:
>>
>> > $ crontab -e
>> >
>> > In unknown file:
>> > 0 (copy-file "/tmp/crontab.10313" "/var/cron/tabs/dannym")
>> >
>> > ERROR: In procedure copy-file:
>> > In procedure copy-file: No such file or directory
>> >
>> > /var/cron doesn't exit either. Maybe we should automatically create /var/cron ?
>>
>> Yes, this should be done in an activation snippet.
>>
>
> Should this be part of a crontab service
That’s what I had in mind.
> or does the mere existence of the files allow cron tasks to start
> working?
Good question. Actually I think the crontab compatibility bit is rather
separate in mcron: AIUI, you have to run ‘crond’, not ‘mcron’, if you
want that to get that functionality (info "(mcron) Invoking cron or
crond").
So perhaps all this is moot unless/until we have an mcron-crond service.
Ludo’.
Reply sent
to
Maxim Cournoyer <maxim.cournoyer <at> gmail.com>
:
You have taken responsibility.
(Tue, 24 Aug 2021 03:50:01 GMT)
Full text and
rfc822 format available.
Notification sent
to
Danny Milosavljevic <dannym <at> scratchpost.org>
:
bug acknowledged by developer.
(Tue, 24 Aug 2021 03:50:02 GMT)
Full text and
rfc822 format available.
Message #19 received at 40499-done <at> debbugs.gnu.org (full text, mbox):
Hello,
Ludovic Courtès <ludo <at> gnu.org> writes:
> Hi,
>
> Efraim Flashner <efraim <at> flashner.co.il> skribis:
>
>> On Wed, Apr 08, 2020 at 11:55:05AM +0200, Ludovic Courtès wrote:
>>> Hi Danny,
>>>
>>> Danny Milosavljevic <dannym <at> scratchpost.org> skribis:
>>>
>>> > $ crontab -e
>>> >
>>> > In unknown file:
>>> > 0 (copy-file "/tmp/crontab.10313" "/var/cron/tabs/dannym")
>>> >
>>> > ERROR: In procedure copy-file:
>>> > In procedure copy-file: No such file or directory
>>> >
>>> > /var/cron doesn't exit either. Maybe we should automatically create /var/cron ?
>>>
>>> Yes, this should be done in an activation snippet.
>>>
>>
>> Should this be part of a crontab service
>
> That’s what I had in mind.
>
>> or does the mere existence of the files allow cron tasks to start
>> working?
>
> Good question. Actually I think the crontab compatibility bit is rather
> separate in mcron: AIUI, you have to run ‘crond’, not ‘mcron’, if you
> want that to get that functionality (info "(mcron) Invoking cron or
> crond").
>
> So perhaps all this is moot unless/until we have an mcron-crond service.
I think so. And since Dale Mellor, the original author of GNU Mcron
advises to keep the crond service per-user rather than for the system
[0], if we want a crond service it seems we should turn ourselves to
Guix Home.
Closing.
[0] https://issues.guix.gnu.org/40950#5
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Tue, 21 Sep 2021 11:24:06 GMT)
Full text and
rfc822 format available.
This bug report was last modified 2 years and 216 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.