[10:33] Greetings all [10:34] Can someone tell me an alternative to cron which has the ability to do jobs in a specific year? [10:36] apart from the obvious workaround, checking the year inside the job? [10:38] Mh, didn't considering using year check in the script. [10:39] systemd.timer(5) units seem to be able to specify an absolute timestamp with OnCalendar= [10:39] Thanks, will check it out :) [11:15] Lovely.. Attempted to remove disk file system, and we can't allow that [11:16] https://paste.ubuntu.com/p/CsgTnb39p7/ - What I have thus far. Could be wrong, but still attempting to improve it. [11:16] But thus far, getting: /etc/systemd/system/./inferno-daily.timer:8: Unknown section 'Service'. Ignoring. Attempted to remove disk file system, and we can't allow that. === jancoow is now known as {jancoow} === {jancoow} is now known as [jancoow] === [jancoow] is now known as jancoow [11:27] Hi! I've got a question for you guys. I have a Raspberry Pi 3B+ with Ubuntu Server 18.04 LTS installed, and USB webcam attached. I am trying to stream the webcam A/V using VLC, thus far I have had success streaming the Video, but not yet the audio, I note no audio device are registered in the system. What software would I need to install to get the [11:27] microphone from the webcam to show as an audio device? [11:27] Any help would be greatly appreciated! [12:36] Wow this systemd timer is annoying... [12:36] enable name.timer works just fine, but when I attempt to start it getting error printed out "Refusing to start, unit to trigger not loaded" [12:39] Skyrider: a timer needs a service unit as well, do you have that, with the same name? [12:39] * ahasenack reads up [12:39] Ya, I do. Otherwise the SH file couldn't run with enable. [12:40] When I run the enable command, the sh from service is being run. Just can't start it. [12:40] the service has to stay put, not started. On what do you run the enable command? [12:40] `systemctl enable backup.timer` - `systemctl start backup.timer` [12:40] Only trying to start the timer file. [12:41] and what does "systemctl list-timers" say about the backup timer? [12:41] I don't remember now if one has to "start" the timer [12:41] 0 listed timers, using --all it shows the inactive timer I setup, all with n/a [12:42] 0 timers? Is this a normal ubuntu system, or something stripped down? [12:42] you should have many timers listed, without --all [12:42] I filtered by my timer name. [12:42] Without any filters, the rest of the system timers shows up in the list :) [12:42] ok, good :) [12:42] I'll pastebin the 2 files :p might make it easier.. maybe I messed up. [12:42] lemme see your paste [12:43] https://paste.ubuntu.com/p/CsgTnb39p7/ is what you pasted before, right [12:43] Ya, I messed up the above paste. Wasn't aware service & timer had to be there as 2 files. I assumed timer was one. [12:43] a timer doesn't have... ah, ok [12:43] 1 sec [12:43] a timer is just another way to start a service, in the end [12:44] Service file: https://paste.ubuntu.com/p/vydKfxjQzY/ [12:44] Timer: https://paste.ubuntu.com/p/zQWSBfxvJF/ [12:44] I included "requires" on a later time when it wasn't working. I often check google for some help. [12:45] Still doesn't work I might add ^_^ [12:45] Aw, crap.. I see why it doesn't work now.. I'm stupid [12:45] I think type should be oneshot [12:47] Got it to work. Thanks for your assistance. I was stupid that I didn't catch on the unit name. [12:47] happy to help :) [12:48] Systemd has no specific seconds that it can time, does it? [12:48] what do you mean? [12:49] I'll ask again later when I remember what I wanted to ask ^_^, thanks. [12:50] :) [12:50] systemd.timer(5) has tons of options, as usual [12:50] not easily digestable in one go [12:55] Noticed, just a shame it takes up extra files rather than a single user cron file ^_^ [13:01] Ah, right.. think I know what to ask.. I think with cron, it's impossible to run cron jobs at 59's second of each minute. (1 second before hitting 1 minute) [13:01] Wonder if you can do that with systemd. [13:05] I use this https://crontab.guru/ to double check the cron timers in the past. Does something similar exists for systemd timer? [13:39] ahasenack: Do you happen to know if I wish to make a systemd timer to run between 9 and 59 at every 10 minutes, it checks at every 10 min? Systemd seems to check only the first 9th min to run, and start after that. But doesn't check every 10 minute when to run after when its past that 9th minute. [13:40] With cron I was able to use 9-59/10 * * * * for that [13:50] maybe 09/10 will do the trick [17:16] Skyrider: timers have a random "fuzz" added to the time, so they don't always run at the exact same time [17:16] Skyrider: that is configurable, but there are many options about it and it can be confusing