BPanther's Neutrino Forum

DeepStandby is executed by fp_control -e and reads also the timer.

Should be here right.

"fp_control -e" makes a shutdown like "halt" but fp_control reads the timers. If there are running any programs, recording or whatever -> shutdown. It's nearly the same as "reboot -f". No filesystems are unmountet (data may lost) etc. That's the cause you should not use the commands if not really, really needed.

The setting with "soft" to "deep" is an internal timer in neutrino. Neutrino ends then normal with Errorlevel 0 and then has the control again the rcS and makes the shutdown with fp_control -e after unmounting the filesystems. You can see this in the one log in the other thread (fp_control says "...good bye..." -> box off). If a recording already running, neutrino does wait if recording ends. If only planned in future, the shutdown runs normally, the reboot for recording must make the frontpanel, fp_control sets the timer (see also the log).

From the log:
Neutrino exit:

[neutrino] This is the end. exiting with code 0

fp_control called the first time:

fp_control: SW Version 1.04
Model: hdbox
vBoxType: 8
Selected Model: Fortis HDBOX frontpanel control utility
checkConfig
configs: DISPLAY = 1, DISPLAYCUSTOM = 1, CUSTOM = %H:%M:%S
, WAKEUPDECREMENT 300

Unmount filesys etc.:

Stopping automounter.
umount /dev/sda1
umount /dev/sda1
umount: can't umount /dev/sda1: Invalid argument
umount /dev/sdb1
umount /dev/sdb2
umount /dev/sdb3
Terminated
sh: can't kill pid 1294: No such process
Terminated

fp_control -e:

fp_control: SW Version 1.04
Model: hdbox
vBoxType: 8
Selected Model: Fortis HDBOX frontpanel control utility
checkConfig
configs: DISPLAY = 1, DISPLAYCUSTOM = 1, CUSTOM = %H:%M:%S
, WAKEUPDECREMENT 300
Current Time: 18:42:42 13-01-2014
Getting enigma2 wakeup time - Reading... /proc/stb/fp/wakeup_time - Done
Getting neutrino wakeup time - Reading... /var/tuxbox/config/timerd.conf - Done
wakeup Time: 04:14:07 19-01-2038
current Time: 18:42:42 13-01-2014
no timer found ... good bye ...
Set Time (UTC): 03:14:07 19-01-2038

Why a soft after a time? Or do you mean a sleep timer, then set it (main menu).

Thats right, but why do you use cron? I don't understand this...

That the wrog way. As I sayd, datas may lost if you make the shutdown with fp_control or other, cron does not wait. Just create a permanent timer for a soft standby.

Just see the timer list menu. You can add your own and set the timer action (see screenshot).