Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
what to do about crons?
View unanswered posts
View posts from last 24 hours

Goto page 1, 2, 3, 4  Next  
Reply to topic    Gentoo Forums Forum Index Gentoo Chat
View previous topic :: View next topic  

do you cron?
anacron (2009)
0%
 0%  [ 0 ]
bcron (2015)
0%
 0%  [ 0 ]
cronie (2019)
35%
 35%  [ 18 ]
dcron (2011)
7%
 7%  [ 4 ]
fcron (2016)
11%
 11%  [ 6 ]
vixie-cron (2004)
39%
 39%  [ 20 ]
systemd
1%
 1%  [ 1 ]
no i don't
3%
 3%  [ 2 ]
Total Votes : 51

Author Message
bunder
Bodhisattva
Bodhisattva


Joined: 10 Apr 2004
Posts: 5934

PostPosted: Mon Apr 01, 2019 4:15 am    Post subject: what to do about crons? Reply with quote

so gentoo's been on a purging spree lately, and they recently decided to disband the cron project, which moved all the cron daemons to maintainer-needed. i can stand behind wanting to get rid of dead, unmaintained wood, but crons aren't exactly something that need updating every week like the java jre does... :lol:

are crons still really relevant in 2019? maybe i'm just the odd person out? is this another reason for me to get on the systemd bandwagon? i'd like to hear people's thoughts on cron usage in 2019.
_________________
Neddyseagoon wrote:
The problem with leaving is that you can only do it once and it reduces your influence.

banned from #gentoo since sept 2017
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 9691
Location: almost Mile High in the USA

PostPosted: Mon Apr 01, 2019 4:36 am    Post subject: Reply with quote

Gosh I still use vixie-cron. Been trying to use anacron and/or cronie instead, but when I think cron, I think vixie-cron, and all my machines have some flavor of cron.

Server using cron handles keeping /usr/portage up to date, scrubs the RAID, and does a lot of housecleaning.

Though I use systemd on other boxes, those systemd boxes rarely have time based services on them as they are not 24/7 machines.

What's next, getting rid of sys-process/at ? :(
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?
Back to top
View user's profile Send private message
bunder
Bodhisattva
Bodhisattva


Joined: 10 Apr 2004
Posts: 5934

PostPosted: Mon Apr 01, 2019 4:42 am    Post subject: Reply with quote

eccerr0r wrote:
What's next, getting rid of sys-process/at ? :(


yeah, at got caught up in that too, i didn't add it because while it does function similar to cron, i don't really consider it to be the same thing as a cron.
_________________
Neddyseagoon wrote:
The problem with leaving is that you can only do it once and it reduces your influence.

banned from #gentoo since sept 2017
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 9691
Location: almost Mile High in the USA

PostPosted: Mon Apr 01, 2019 5:01 am    Post subject: Reply with quote

I figure that the services of sys-process/at can be scripted if there is a working cron, so at(1)/atd(8) is superfluous. In fact older unix have the functionality of at(1)/atd(8) as part of cron...

However I'm sure tons of people are still using cron. How are Gentoo development systems dealing with regularly running maintenance scripts? Don't tell me they've all switched to systemd? :o

BTW, we need another systemd poll...maybe...
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?
Back to top
View user's profile Send private message
The Doctor
Moderator
Moderator


Joined: 27 Jul 2010
Posts: 2678

PostPosted: Mon Apr 01, 2019 5:06 am    Post subject: Reply with quote

Crons are vital for backups, virus scan (I know, I know), and other housekeeping. Rather important for functionality.

Sounds like someone is trying to force systemd on the plebs. This is a bad call. We are gaining users who want the freedom not to use it.
_________________
First things first, but not necessarily in that order.

Apologies if I take a while to respond. I'm currently working on the dematerialization circuit for my blue box.
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 8938

PostPosted: Mon Apr 01, 2019 5:13 am    Post subject: Reply with quote

Don't be disingenious. Disbanding a project does not mean its packages are being purged, but that individuals can take over package maintainence instead of an unresponsive (dead) project.
Back to top
View user's profile Send private message
bunder
Bodhisattva
Bodhisattva


Joined: 10 Apr 2004
Posts: 5934

PostPosted: Mon Apr 01, 2019 5:14 am    Post subject: Reply with quote

asturm wrote:
Don't be disingenious. Disbanding a project does not mean its packages are being purged, but that individuals can take over package maintainence instead of an unresponsive (dead) project.


no, but a package that is maintainer-needed after 30 days is a candidate for tree cleaning.
_________________
Neddyseagoon wrote:
The problem with leaving is that you can only do it once and it reduces your influence.

banned from #gentoo since sept 2017
Back to top
View user's profile Send private message
asturm
Developer
Developer


Joined: 05 Apr 2007
Posts: 8938

PostPosted: Mon Apr 01, 2019 5:18 am    Post subject: Reply with quote

bunder wrote:
no, but a package that is maintainer-needed after 30 days is a candidate for tree cleaning.

No. Although I will concede that it is easier to get rid of (if it e.g. is piling up bugs with no solution). Last-riting involves an announcement followed by a 30-day waiting time before removal, which is often a second chance for someone to take notice and pick up this package after all.
Back to top
View user's profile Send private message
Muso
Veteran
Veteran


Joined: 22 Oct 2002
Posts: 1052
Location: The Holy city of Honolulu

PostPosted: Mon Apr 01, 2019 5:24 am    Post subject: Reply with quote

Cronie now... mcron before that.
_________________
"You can lead a horticulture but you can't make her think" ~ Dorothy Parker
2021 is the year of the Linux Desktop!
Back to top
View user's profile Send private message
C5ace
Guru
Guru


Joined: 23 Dec 2013
Posts: 474
Location: Brisbane, Australia

PostPosted: Mon Apr 01, 2019 6:29 am    Post subject: Reply with quote

I maintain 24 systems with cronie installed.
_________________
Observation after 30 years working with computers:
All software has known and unknown bugs and vulnerabilities. Especially software written in complex, unstable and object oriented languages such as perl, python, C++, C#, Rust and the likes.
Back to top
View user's profile Send private message
Maitreya
Guru
Guru


Joined: 11 Jan 2006
Posts: 441

PostPosted: Mon Apr 01, 2019 7:30 am    Post subject: Reply with quote

Always used vixie-cron in the past as that was adviced in the Gentoo manuals I think.
Since a year or so switched to cronie.
Back to top
View user's profile Send private message
Ant P.
Watchman
Watchman


Joined: 18 Apr 2009
Posts: 6920

PostPosted: Mon Apr 01, 2019 7:38 am    Post subject: Reply with quote

Maitreya wrote:
Always used vixie-cron in the past as that was adviced in the Gentoo manuals I think.
Since a year or so switched to cronie.

This. Mainly because it includes anacron, but also because it's maintained.

vixie-cron's "-r15" in the version is a pretty large red flag that upstream is moribund.
Back to top
View user's profile Send private message
Jimmy Jazz
Guru
Guru


Joined: 04 Oct 2004
Posts: 330
Location: Strasbourg

PostPosted: Tue Apr 02, 2019 12:34 am    Post subject: Reply with quote

I run 4 fcrond deamons simultaneously. One for each runlevel :)
_________________
« La seule condition au triomphe du mal, c'est l'inaction des gens de bien » E.Burke
Code:

+----+----+----+
|    |::::|    |
|    |::::|    |
+----+----+----+

motto: WeLCRO
WritE Less Code, Repeat Often
Back to top
View user's profile Send private message
mike155
Advocate
Advocate


Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany

PostPosted: Tue Apr 02, 2019 1:00 am    Post subject: Reply with quote

What I really hate is that the syntax of configuration files differs between different implementations of cron.

For example, vixie-cron expects a username in column 6 of /etc/crontab and /etc/cron.d/*. dcron doesn't expect a username in column 6, but the command to be executed... If packages like sysstat write crontab files to /etc/cron.d, either vixie-cron or dcron users will get strange error messages...

I voted for vixie-cron, of course! Paul Vixie is one of our heroes!


Last edited by mike155 on Tue Apr 02, 2019 8:24 pm; edited 1 time in total
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7470

PostPosted: Tue Apr 02, 2019 4:41 pm    Post subject: Reply with quote

vixie-cron, what can i say, it just do the job well
Back to top
View user's profile Send private message
gtwrek
Tux's lil' helper
Tux's lil' helper


Joined: 10 Mar 2017
Posts: 110
Location: San Jose, CA

PostPosted: Tue Apr 02, 2019 6:45 pm    Post subject: Reply with quote

I had to poke around to even figure out which one I'm running. I don't recall specifically choosing cronie - probably the default. In any event, of course a cron is required. As long as it works. Be nice if the crontab was the same across all of them, although I modify these sorts of things so infrequently, I'll forget syntax and have to rely on man pages for whatever's installed anyway.
Back to top
View user's profile Send private message
Anon-E-moose
Watchman
Watchman


Joined: 23 May 2008
Posts: 6102
Location: Dallas area

PostPosted: Tue Apr 02, 2019 7:19 pm    Post subject: Reply with quote

My main machine is up 24x7 so I use cron daily.

distfiles and portage to backup storage nightly
fstrim daily/weekly (depending on filesystem)
rsync of filesystem for weekly and nightly backup
updating mlocate db nightly
weekly update man db
hourly check to see if ip (from isp) has changed and let me know if so
setting hwclock nightly (just because :lol: )
logrotate

vixie-cron, it works and haven't had problems with it, kind of like sysv-init, it may be old but it's simple and it does what's needed
_________________
PRIME x570-pro, 3700x, 6.1 zen kernel
gcc 13, profile 17.0 (custom bare multilib), openrc, wayland
Back to top
View user's profile Send private message
Tony0945
Watchman
Watchman


Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Tue Apr 02, 2019 8:57 pm    Post subject: Reply with quote

Anon-E-moose wrote:
... but it's simple and it does what's needed

That's the UNIX way. Too bad today's developers want to follow the Windows way, complex and cryptic.
Back to top
View user's profile Send private message
Fitzcarraldo
Advocate
Advocate


Joined: 30 Aug 2008
Posts: 2038
Location: United Kingdom

PostPosted: Tue Apr 02, 2019 11:20 pm    Post subject: Reply with quote

I use cronie on all my machines. And, yes, cron jobs are still very relevant today.

On a server, I use cronie for automatic periodic tasks including, but not limited to, the following:

- Checking the integrity of multiple RAID 1 pairs.
- Backing up users' NAS files and Cloud files to an external HDD.
- Updating the NIDS rules files provided by the NIDS developer.
- Updating my own NIDS rules files based on the latest unauthorized attempts to access my server.
- Updating the IP geolocation database used by GoAccess (real-time Web log analyser).
- Renewing the digital certificate of my Cloud server.
- Log rotation.
- Updating the mlocate index file.
- Updating the malware detection database in the NAS.

I've had the following trouble with vixie-cron, so I don't use it any more: I use the Web browser bookmarks manager Buku on three Linux machines to sync with a single bookmarks database residing on a Cloud server. Each of the machines also runs a cron job to create a text file of the database output also on the Cloud server, just in case I happen to be using a machine that is not running Buku (e.g. a Windows machine or a smartphone). The three Linux machines were originally using the cronie, cron, and vixie-cron daemons, respectively. However, I found that the text file on the machine running vixie-cron was always truncated. It appeared that somehow vixie-cron was not waiting for the Buku print command in the cron job to finish. So I stopped and disabled the vixie-cron daemon on that machine, uninstalled vixie-cron, installed cronie, enabled and started the cronie service, and everything now works fine. So I now avoid using vixie-cron in any installations.
_________________
Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC systemd-utils[udev] elogind KDE on both.

My blog
Back to top
View user's profile Send private message
Tony0945
Watchman
Watchman


Joined: 25 Jul 2006
Posts: 5127
Location: Illinois, USA

PostPosted: Tue Apr 02, 2019 11:42 pm    Post subject: Reply with quote

Fitzcarraldo, do you have a guide to moving from vixie-cron to cronie? Perhaps on your blog somewhere?
Or is it as easy as unmerging vixie-cron and emerging cronie? What about useflags?
They are different. Are the cronie default flags the way to go?
Code:
MSI ~ #MSI ~ # emerge -pv cronie vixie-cron

These are the packages that would be merged, in order:

Calculating dependencies... done!
[ebuild   R    ] sys-process/vixie-cron-4.1-r15::oldgentoo  USE="pam -debug (-selinux)" 0 KiB
[ebuild  N     ] sys-process/cronie-1.5.4::gentoo  USE="anacron inotify pam (-selinux)" 120 KiB
[blocks B      ] sys-process/cronie ("sys-process/cronie" is blocking sys-process/vixie-cron-4.1-r15)
[blocks B      ] sys-process/vixie-cron ("sys-process/vixie-cron" is blocking sys-process/cronie-1.5.4)
Back to top
View user's profile Send private message
Fitzcarraldo
Advocate
Advocate


Joined: 30 Aug 2008
Posts: 2038
Location: United Kingdom

PostPosted: Wed Apr 03, 2019 3:39 pm    Post subject: Reply with quote

Tony0945,

Code:
$ eix --installed vixie-cron
No matches found

Code:
$ eix --installed cronie
[I] sys-process/cronie
     Available versions:  1.5.2 ~1.5.4 {+anacron +inotify pam selinux}
     Installed versions:  1.5.2(21:30:31 25/11/18)(anacron inotify pam -selinux)
     Homepage:            https://github.com/cronie-crond/cronie
     Description:         Cronie is a standard UNIX daemon cron based on the original vixie-cron

Fitzcarraldo wrote:
I stopped and disabled the vixie-cron daemon on that machine, uninstalled vixie-cron, installed cronie, enabled and started the cronie service, and everything now works fine.

USE flags enabled/disabled are as shown above.
_________________
Clevo W230SS: amd64, VIDEO_CARDS="intel modesetting nvidia".
Compal NBLB2: ~amd64, xf86-video-ati. Dual boot Win 7 Pro 64-bit.
OpenRC systemd-utils[udev] elogind KDE on both.

My blog
Back to top
View user's profile Send private message
Dr.Willy
Guru
Guru


Joined: 15 Jul 2007
Posts: 547
Location: NRW, Germany

PostPosted: Wed Apr 03, 2019 9:08 pm    Post subject: Reply with quote

I actually had to look it up, but it appears im using dcron. I remember making that choice, but I don't remember why.
Back to top
View user's profile Send private message
depontius
Advocate
Advocate


Joined: 05 May 2004
Posts: 3509

PostPosted: Thu Apr 04, 2019 11:39 am    Post subject: Reply with quote

Fitzcarraldo wrote:
Tony0945,

Code:
$ eix --installed vixie-cron
No matches found

Code:
$ eix --installed cronie
[I] sys-process/cronie
     Available versions:  1.5.2 ~1.5.4 {+anacron +inotify pam selinux}
     Installed versions:  1.5.2(21:30:31 25/11/18)(anacron inotify pam -selinux)
     Homepage:            https://github.com/cronie-crond/cronie
     Description:         Cronie is a standard UNIX daemon cron based on the original vixie-cron

Fitzcarraldo wrote:
I stopped and disabled the vixie-cron daemon on that machine, uninstalled vixie-cron, installed cronie, enabled and started the cronie service, and everything now works fine.

USE flags enabled/disabled are as shown above.


I'm using vixie-cron, just because that's how I originally set things up, and it's been OK. Reading this thread, it looks as vixie-cron may not be very "alive", and I've also heard that cronie avoids writing to disk, which is better for SSDs. Switching has been moving toward a planned item for a few weeks. Hearing that it's a simple matter of switching packages, and that it will just use my existing cron files helps push that.
_________________
.sigs waste space and bandwidth
Back to top
View user's profile Send private message
krinn
Watchman
Watchman


Joined: 02 May 2003
Posts: 7470

PostPosted: Thu Apr 04, 2019 11:48 am    Post subject: Reply with quote

depontius wrote:
as vixie-cron may not be very "alive"

the problem with "stall" package is that it could be an effect of stability. why touching code of something that do the job?
i'm not to push something out just because it is stall ; if no glsa, and i fail to see when vixie-cron has crash on my computer (but to be honest, i'm not looking specially if it has crash), i'm happy with it.
Back to top
View user's profile Send private message
eccerr0r
Watchman
Watchman


Joined: 01 Jul 2004
Posts: 9691
Location: almost Mile High in the USA

PostPosted: Thu Apr 04, 2019 1:59 pm    Post subject: Reply with quote

There is one problem with stale packages, though I don't know if it applies to any of the crons:

The silly c and libc standards keep moving. Old programs sometimes need patches to compile/link properly as time moves forwards. Ideally someone is applying patches to keep up else they won't build anymore.
_________________
Intel Core i7 2700K/Radeon R7 250/24GB DDR3/256GB SSD
What am I supposed watching?
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Gentoo Chat All times are GMT
Goto page 1, 2, 3, 4  Next
Page 1 of 4

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum