Skyrider | Greetings | 08:50 |
---|---|---|
mybalzitch | Hello | 08:52 |
Skyrider | I have a slight, problem. Im running timers/service files for a few of my scripts. But whenever the system restarts, the timers also run. https://paste.ubuntu.com/p/hzZgDsk8W6/ | 08:55 |
Skyrider | I was wondering what option I should use so timers run on on the set time, rather than right away on boot. | 08:56 |
mgedmin | Skyrider: your question is going to haunt me | 09:41 |
Skyrider | How so? | 09:41 |
mgedmin | according to the systemd.timer manual page it should already be happening that way, since you don't have Persistent=true in your timer unit | 09:42 |
mgedmin | is that the only unit file? no overrides etc? | 09:42 |
Skyrider | Those are the only files. Any many other timer/service files like that one. Just pinpointing to different sh script files. | 09:44 |
frickler | Skyrider: are you sure that the timer actually runs or does it just start your service because of your "Requires" statement? | 14:40 |
Skyrider | frickler: As far as I know, timer runs the service which runs the script. Has been working for over a year. | 15:32 |
Skyrider | Just the service runs at start-up. While I only enabled the timer | 15:33 |
teward | Skyrider: i would check your syslog to see when the timer executes, etc. Or journalctl to make sure it actually executes the timer. | 16:27 |
teward | timers DO run at boot if they're configured to I believe, and that's "Usual Behavior" | 16:28 |
teward | as is servic estartup :p | 16:28 |
Skyrider | Your first line, you refer to the boot up or if the timers actually work? | 16:29 |
Skyrider | `Or journalctl to make sure it actually executes the timer` - You mean if the service or timer starts on boot. | 16:30 |
teward | both. `journalctl -u whatever.timer` or `journalctl -u whatever.service` will show the respective information about either unit | 16:30 |
teward | compare times from when you booted your computer and you can determine if one or both actually execute on boot or if you're imagining it | 16:30 |
Skyrider | Can't imagen it.. XD, one of the scripts is set to RM a directory once a week. | 16:32 |
Skyrider | If the boot up suddenly erases the directory before the timer, then ya.. :p | 16:32 |
teward | so i think you meant to have that service be a oneshot unless it's a daemon | 16:32 |
teward | timers calling the oneshot on the specified time | 16:33 |
teward | but let's start by checking the journalctl output to see what's actually happening - whether the timer is running or the service is running on boot ;) | 16:33 |
Skyrider | Its weird though.. I only enabled the timer, not the service. | 16:33 |
Skyrider | But ya.. I'll just relaunch the lxc container and keep backups to check the logs. | 16:34 |
teward | i mean I still use `cron` jobs for things - because they don't have any weirdness with timer execution and such) | 16:44 |
teward | but that's just me :P | 16:44 |
RoyK | Seems Trump won't give up, just like the black night https://www.youtube.com/watch?v=2eMkth8FWno </slightlyofftopic> | 16:54 |
Skyrider | teward: Crons has its limits. | 20:21 |
Skyrider | Especially when it comes to seconds I believe. | 20:21 |
jayjo | I'm trying to automate a server installation that I'm installing with a USB... referencing https://ubuntu.com/server/docs/install/autoinstall. There is a line about "This is to make it harder to accidentally create a USB stick that will reformat a machine it is plugged into at boot." - how do I put the config on the bootable USB so it will install automatically? | 20:48 |
jayjo | Most examples are for netboots | 20:48 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!