VB: how to set PXE-linux default reboot time debian-edu squeeze

Hi,

It occasionaly happens, but one time I know it will happen is if i reboot tjener... As when doing updates etc and then rebooting. I usually do that from home in the weekends, and there are always some clients left on.. this problem seems to be restricted to only thinclients, not discless workstations.
Somehow the clients reconnects when it comes to syslog... but they are still stalled until being rebooted. Maybe there are some way to stop them from reconnecting and sending logs to tjener that I dont know of.
Once one has started it sends the same message over and over again in a quite rapid speed... since it goes to syslog it makes it impossible to use tail or anything on syslogs to do different tasks.. As all you will ever see are all those squash-fs messages.. Of course you can grab after it, if you know the expected output, but it becomes very slow as the log grows...

Anyhow, it was a thought. Thanks for your idea about the watchdog. Will search and see if I can find something usefull.

/George

Från: Petter Reinholdtsen <pere@hungry.com>
Till: debian-edu@lists.debian.org
Skickat: söndag, 26 maj 2013 7:23
Ämne: Re: how to set PXE-linux default reboot time debian-edu squeeze

[George]
> Hi,
>
> I sometimes have problem with thin clients getting in to a "stalled"
> state just filling up the logs of the tjener with "squash-fs"
> messages.. That is, the client has somehow lost contact with tjener.

Hm, perhaps a good idea. Any idea why it lost contact with tjener?

> I read on http://www.syslinux.org/wiki/index.php/PXELINUX that you
> could set a default reboot time for the client, to reboot say 30
> minutes after loosing contact. That is a dhcp option.
>
> How can I set/change this in tjener? Are the clients supposed to
> reboot in case of loosing contact in the default debian-edu squeeze
> edition?
>
> Option 211: pxelinux.reboottime

I doubt it do what you hope, though I have never used it myself. It
is a setting to pxelinux, the program running very early in the boot
to fetch the kernel and the initrd, and will most likely only affect
the operation of that part of the boot. Once the kernel take over and
the Linux system start, I suspect it will be ignored.

To do something similiar from within linux, I suspect a watchdog
process of some kind is the best option, checking if the NFS server is
reachable and/or the root file system is available.

--
Happy hacking
Petter Reinholdtsen

--
To UNSUBSCRIBE, email to debian-edu-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: [🔎] 20130526052356.GC21276@ulrik.uio.no">http://lists.debian.org/[🔎] 20130526052356.GC21276@ulrik.uio.no