I don't think this is actually a problem with ltsp, but I'm just hoping someone has run into this problem before.
I've imaged an LTSP server running SLES 10 and shipped off this image to IBM, so I need to deal with this problem about 1800 times without any human interaction. The problem is basically this: Upon first boot of this image, the time gets adjusted 44 hours into the future (maybe /etc/adjtime... Doesn't matter why, we can't change the image). The NFS service starts up with this time in place and of course so do all the other services. When I synch up with an NTP server, and the time is corrected, LTSP clients will no longer connect to NFS and successfully boot. If I set the time back to the future date, thin clients boot fine (the instant I change the date). My question is "How do I safely correct the time backwards to the correct time without breaking NFS?" Once again, this is not LTSP's fault, so I understand if no-one can help, but I figured I'd stick this question out there and see if anyone had come across this situation before. One option is to power down the server for 44 hours and then it should start working again... Unfortunately, we don't like that option very well. Jeremy Young Sr. Programmer/Analyst O'Reilly Auto Parts (417) 862-2674 x1858 ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _____________________________________________________________________ Ltsp-discuss mailing list. To un-subscribe, or change prefs, goto: https://lists.sourceforge.net/lists/listinfo/ltsp-discuss For additional LTSP help, try #ltsp channel on irc.freenode.net
