Hi, since 2017/06/07, spooled at(1) files have to be owned by group crontab, and at(1) makes sure that this is the case for newly created at(1) jobs.
However, if you create an at(1) job while still running OpenBSD-6.1 and then update to OpenBSD-6.2 *before* that at(1) job had been run, it will be dropped. Example (that's what I ran into this day): Existing at(1) job, created on OpenBSD-6.1 (note the group 'polly' which would be 'crontab' with the new at(1)): -rwx------ 1 polly polly 358 Oct 3 12:01 1508148000.c Message from /var/cron/log today (after updating to OpenBSD-6.2 a couple of days ago): Oct 16 12:00:01 dead-parrot cron[46001]: (polly) WRONG FILE GROUP (1508148000.c) I'm not sure wether anyone except me is scheduling at(1) jobs far enough in the future to cross an update. But in case anyone else does, would this addition to the upgrade faq help? Index: upgrade62.html =================================================================== RCS file: /cvs/www/faq/upgrade62.html,v retrieving revision 1.4 diff -u -p -r1.4 upgrade62.html --- upgrade62.html 7 Oct 2017 21:06:39 -0000 1.4 +++ upgrade62.html 16 Oct 2017 21:35:06 -0000 @@ -102,6 +102,15 @@ to the <a href="../stable.html">stable b <li><b>resize <tt>/usr/obj</tt>.</b> If you build your own releases on the amd64 or i386 platforms, you need to make sure that you have at least 3G available on <tt>/usr/obj</tt>. + + <p> + <li><b>adjust group ownership of existing at(1) jobs.</b> + The <a href="https://man.openbsd.org/OpenBSD-6.2/cron";>cron(8)</a> daemon + requires at(1) files in the spool to be owned by group crontab. + + <blockquote><pre> + # <b>chgrp -R crontab /var/cron/atjobs</b> <!-- + --></pre></blockquote> </ul> Ciao, Kili
