So, the classroom imaged alright overnight. It seems like the server ran out of memory and had to kill a few processes during the course of the imaging process, but every workstation seemed to image fine. The beeping classroom was rather amusing when I came in. Might this locking up of the server be alleviated by popping in some more memory? (it's only got 512 right now, I believe, it's just exactly the same type of hardware as the workstations, really) or will it simply eat up as much memory as it gets and still lock up? Other than that, let me see...Ummm...ok, yeah, so when I do an si_updateclient, it seems to wipe out every change I make during the autoconfig script that first time, EXCEPT for the hostname, which keeps the workstation from realizing it needs to run the autoconfig script again. I can change it to test the contents of /etc/hosts/ instead of the $HOSTNAME variable, though I suppose I should really figure out how all the systemimager scripts work and see if maybe they would help me accomplish my goals in an easier way. Also, is there any way to trigger an autoinstall on the workstation and pass it the imagename? trying to do si_updateclient with both --autoinstall and --image doesn't seem to work... I hope this finds you all doing well. Take care! Sim?n
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ sisuite-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sisuite-users
