[EMAIL PROTECTED] wrote:
I've got some problems with time while deploying image with SI. I created an image, time is correct. When I deploy this image, fsck tells it didn't check filesystem for 40000 days and of course launch a fsck. When I log in, time is correct, cause I use ntpdate juste before. The phenomenon appears on differents motherboards so I don't think it's hardware.
Oh, I've seen this with SystemImager for years ! When the newly cloned client boots for the first time, it shows the fsck behavior that you describe. I always thought this was a feature rather than a bug, since it's quite sensible to fsck the filesystem the first time that you ever boot it, and it only adds a few seconds to the booting time. If you think this behavior is a bug, you should probably submit a bug report on http://sourceforge.net/tracker/?group_id=259&atid=100259 (beware, however, that bug fixing through this system seems to have very low priority with the developers...). However, I prefer the current behavior, and I suggest to add a "force fsck at first reboot" option in case this isn't the default any more. Ole Holm Nielsen Department of Physics, Technical University of Denmark ------------------------------------------------------- SF.Net email is sponsored by: Discover Easy Linux Migration Strategies from IBM. Find simple to follow Roadmaps, straightforward articles, informative Webcasts and more! Get everything you need to get up to speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click _______________________________________________ Sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
