On Thu, 30.05.13 00:05, [email protected] ([email protected])
wrote:
>
> Andrey Borzenkov,
>
> > May be if you explain what you are trying to achieve
>
> A nightly "cron job" with post-execution reboot upon successful completion.
> We may use cron if systemd can't do it. I expect
On Sat, 25.05.13 23:19, [email protected] ([email protected])
wrote:
> How to reboot from a systemd timer? We have
>
> systemd timer calls
> systemd unit calls
> bash script calls
> systemctl reboot
>
> The script runs fine each day, except for its last step, "systemct
В Sat, 01 Jun 2013 04:08:27 +
[email protected] пишет:
> > You can likely create a timer unit, and start that once...Auke
>
> Maybe, but I nurse doubts given systemctl oddities under discussion.
Which oddities? I reviewed this thread and you never ever explained,
*what* does not work.
> You can likely create a timer unit, and start that once...Auke
Maybe, but I nurse doubts given systemctl oddities under discussion. Try
it and see what you can do, then post working code as I did. I drove at
this idea earlier talking about a second timer, but sounded muddled, I
gather.
Thanks!
'Twas brillig, and Kok, Auke-jan H at 31/05/13 06:27 did gyre and gimble:
> You can likely create a timer unit, and start that once...
That's the premise he started with, but it seems to cause a sort of
deadlock... See the first message in the thread.
Col
--
Colin Guthrie
gmane(at)colin.guthr.
On Thu, May 30, 2013 at 9:34 PM, wrote:
> Simple "at" did the trick from nightjanitor.sh
>
> echo "systemctl start reboot.target" | at now + 3 min
>
> If a more purist systemd method exists, I'd love to see it.
You can likely create a timer unit, and start that once...
Auke
__
Simple "at" did the trick from nightjanitor.sh
echo "systemctl start reboot.target" | at now + 3 min
If a more purist systemd method exists, I'd love to see it.
footnote:
"at" install for Arch Linux, pkg not present by default,
your distro may be similar
$ sudo pacman -S at
$ sudo systemctl
Andrey Borzenkov,
> May be if you explain what you are trying to achieve
A nightly "cron job" with post-execution reboot upon successful completion.
We may use cron if systemd can't do it. I expect it can, but know not how.
Obvious things and list advice didn't work. Thanks.
Files under test:
ht
В Wed, 29 May 2013 04:24:41 +
[email protected] пишет:
> Tried all advice so far, no dice, but thanks. A more advanced
> timer/service layout may be needful in this rev of systemd (204), though
> I'm fairly clueless what.
>
> Last try was
> ( sleep 30 && systemctl --no-block start rebo
Tried all advice so far, no dice, but thanks. A more advanced
timer/service layout may be needful in this rev of systemd (204), though
I'm fairly clueless what.
Last try was
( sleep 30 && systemctl --no-block start reboot.target ) &
If anyone succeeds making something work, please post and thank
'Twas brillig, and [email protected] at 26/05/13 06:29 did gyre
and gimble:
> Jan Alexander Steffens,
>
> So in this timer, where/how apply reboot.target,
> or else tell systemd to invoke? Thx
>
> --
> # /etc/systemd/system/nightjanitor.timer
> [
Jan Alexander Steffens,
So in this timer, where/how apply reboot.target,
or else tell systemd to invoke? Thx
--
# /etc/systemd/system/nightjanitor.timer
[Unit]
Description=Nightly wee-hours heartbeat
[Timer]
OnCalendar=*-*-* 01:23:45
Unit=nightjanitor.
On Sun, May 26, 2013 at 1:19 AM, wrote:
>
> How to reboot from a systemd timer? We have
>
> systemd timer calls
> systemd unit calls
> bash script calls
> systemctl reboot
>
> The script runs fine each day, except for its last step, "systemctl
> reboot." What's the right protocol? Is i
How to reboot from a systemd timer? We have
systemd timer calls
systemd unit calls
bash script calls
systemctl reboot
The script runs fine each day, except for its last step, "systemctl
reboot." What's the right protocol? Is it wrong to call systemctl from a
script?
Thanks
--
http:
14 matches
Mail list logo
