-mark
Brian Elliott Finley wrote:
Mark,
I like your comments, and your humor. ;-)
Can you send me a patch to netbootmond with the behaviour you believe it should have?
Thanks!
-Brian
Thus spake Mark Seger ([EMAIL PROTECTED]):
Actually this is pretty slick/sick (depending on your perspecitve) 8-)
The copy is supposed to fail! The process, netbootmond (which has a bug I'll get to in a minute now that you reminded me about it) watches the tail of the rcync log for that very message to occur and once it sees that, know the installation completed successfully and write an empty file such as C0A8F829 to the /tftboot/pxelinux.cfg directory. On the next pxe boot, this tells the client not to load a remote image but rather boot locally. This whole mechanism only works if you
1 - edit /etc/systemimager/systemimager.conf and change the last entry to NET_BOOT_DEFAULT = local
2 - service systemimager-server-netbootmond start
works like a champ to prevent an installed node from reinstalling. naturally when you want to reinstall a node you need to manually remove that file - C0A8F829 - which is actually an encoding of the network address, 1 octet to each 2 chars. There can also be done via mkclientnetboot.
now for the bug in netbootmontd...
as written, netbootmond sits in a loop and looks at the last record in the rsync log, but a colleague and myself have experienced a situation where a 3 line error messages gets long and the line containing the string "scripts/imaging_complete" is missed! The fix is to look deeper into the rsync file (in my case at least -n 3), the challenge is to avoid messages that were already seen/processed.
-mark
Message: 2 Date: Wed, 12 May 2004 04:29:58 -0500 From: Thomas Schenk <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: Re: [Sisuite-users] mkautoinstalldiskette problem Reply-To: [EMAIL PROTECTED]
I didn't really mean to be such a smart ass in my reply and I did solve the problem by recompilining the kernel that get's installed on the boot floppy. I was just stressing that day due to a migraine.
On another note, however, there was still a problem (although not a show stopper). The final step of the install resulted in an error when a rsync attempt was made by the master script which tried to do something with the <systemimager root>/scripts/imaging_complete directory. (I think that is correct...I'm doing this from memory). Anyhow, supposedly it was supposed to do something with that file or directory and it couldn't because it didn't exist. Perhaps another packaging error in the RedHat RPMS?
Tom S.
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ Sisuite-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-users
