| Commit message (Collapse) | Author | Age | Files | Lines |
| | |
|
| |
|
|
|
|
| |
We have a report about spurious reboots of machines in exam mode while
in use, so try to rule out that this was caused by idle-daemon logic by
logging any such action it would perform through a wrapper script.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
It was reported that WOL is disabled at runtime on some machines, even
though there is a udev rule in place that enables it right when the
interfaces get registered. We can only assume this is a race condition
with adapter initialization, but worst case something else is running
that is interfering with the WOL setting. Now we forcefully re-enable
WOL at boot, every hour, and before standby, for good measure.
|
| |
|
|
|
|
| |
Since we can set PATH for everything spawned by systemd, this
boilerplate code is not needed anymore. Makes future changes much
easier.
|
| |
|
|
|
| |
Generate .xscreensaver as if saver is allowed, then when we check what
the user selected in vmchooser, patch .xscreensaver if necessary.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
vmchooser's sessionstart sets an environment var to tell us whether we
should enable the screen saver for a particular user. Honor this var and
write or delete the flag file idle-daemon depends on.
|
| |
|
|
|
|
|
|
|
|
| |
Keep existing schedule entries (we have --min-idle 7200) but add entries
for 23:00 and 4:00 to non-empty schedules. We might skip a tightly
scheduled entry due to --min-idle, e.g. an exam lasts until 19:30 and
the schedule says poweroff at 20:00. We'll miss that entry if the user
didn't log out before, since two hours didn't pass yet.
If the schedule was empty however, do nothing, since it might be desired
that the machines keep running until they die.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
vmware ungrab code has to fake mouse cursor movement, resetting PC idle
time :-( - Now we can't record the PC idle time the moment the screen
saver turned on anymore, since it will be reset at that point.
|
| |
|
|
|
|
|
| |
In case a shutdown/reboot/... is manually triggered (i.e. via web
interface), the according timestamp won't be in the idleaction hint file
for the xscreensaver hack. Update the timestamp in case a reboot is
imminent, so the screeensaver can update the countdown.
|
| | |
|
| | |
|
| |
|
|
|
|
| |
If a user unlocks the session and locks it again within two minutes,
the idle timeout will not be reset. Even worse, this also happens when
you manage to logout and in (as a different user) within two mins.
|
| |
|
|
|
|
|
| |
The screensaver info is off by 5 minutes for reboot/shutdown, since
there's an additional delay of 5 minutes if someone's logged in.
Always add those 5 minutes, since the message will only ever be seen if
someone is actually logged in.
|
| | |
|
| | |
|
| |
|
|
| |
Closes #3364
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
| |
If the wakeup is scheduled exactly at the time a scheduled
shutdown is, the cronjob for the shutdown would not run, as
the client is still about to wake up at that time.
If we wake up two minutes early, the cron daemon should have
enough time to fully wake up, notice the clock jump, and then
finally trigger the scheduled shutdown.
|
| | |
|
| | |
|
| |
|