[BlueOnyx:22621] Re: Updates overwrote root cron job file?

[Dirk Estenfeld]

Hello,

yes please we have a lot of servers with several cronjobs and all are gone now :(
This is not funny :/
Did you do a backup of the old root crontab file before killing it?

Regards,
Dirk


---

blackpoint GmbH – Friedberger Straße 106b – 61118 Bad Vilbel

-----Ursprüngliche Nachricht-----
Von: Blueonyx <blueonyx-bounces at mail.blueonyx.it> Im Auftrag von Michael Stauber
Gesendet: Donnerstag, 24. Januar 2019 15:27
An: blueonyx at mail.blueonyx.it
Betreff: [BlueOnyx:22618] Re: Updates overwrote root cron job file?

Hi Robert,

> I found the /var/spool/cron/root file updated last night and it 
> removed a job I had defined in the file. Would that be through updates?

Ah, yes. Sorry about that. The installation of blueonyx-le-acme (the new Let's Encrypt client) did run a ...

crontab /usr/sausalito/acme/crontab.cron

... in order to set up its cronjob. Usually BlueOnyx didn't set up cronjobs that way, so I assumed it to be safe. But if you had previously set up cronjobs manually via the crontab command, then it would wipe your cronjobs.

> If so, what is the best way to setup custom cron jobs?

Keep doing it the same way. I'll update the RPM to not replace custom cronjobs but to do a merge instead.

--
With best regards

Michael Stauber
_______________________________________________
Blueonyx mailing list
Blueonyx at mail.blueonyx.it
http://mail.blueonyx.it/mailman/listinfo/blueonyx
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5526 bytes
Desc: not available
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20190124/cffb02ee/attachment.p7s>