8 Feb
2007
8 Feb
'07
4:45 p.m.
Jens Breuer wrote:
Hello List,
Hello Alain,
thank you for implementing the feature in the current version.
Unfortunately I have to second what Gunner said as it seems that this
new feature introduced a weird behaviour.
I just tested the new version. I had my initrd build by cast-o-matic
and specified as extra command line parameters "--nokbd
--start-timeout 600". Additionally I always check the option "Reboot
system after udpcast" together with "full featured shell".
I waited 10 minutes because I wanted to see what happens when the
timeout exceeds and then I saw the following messages on the screen:
"Receiver error.
Error. Not rebooting."
The machine did not reboot what I don't think is the desired effect.
Regards
Jens
Yes, the "reboot" option in cast-o-matic was initially intended to
reboot the machine into the installed OS in case of success. However, if
--start-timeout is supplied and triggered, udp-receiver returns an error.
I've now added an "unconditional reboot" checkbox to cast-o-matic which
should address this issue.
Regards,
Alain