Jumpstart
2007-12-24 21:47:00
when it finishes. The finish part is easy; finish script. But the
begin part is more difficult since you can't run it in a begin script as
sendmail doesn't exist yet. One idea was load the mini-root and use
it's sendmail to fire one off but the problem is that the mini-root is
mounted read-only, which means the spooler queue is also read-only,
hence no mail again.
Another option was server side notification; write a wrapper for tftp in
inetd.conf. Maybe, but someone else suggested a listen daemon that
listens on the port and captures information. This would be enough to
figure out which client was requesting the jumpstart and could be
multi-purpose, unlike the tftp wrapper.
Does anyone out there have a mechanism to be notified when a client
*starts* a jumpstart? I'm talking at the IP request or sooner, during
the actual process is too late for us. The ultimate goal is to know
when a client starts so we know to expect a notification of completion.
That way we know for sure the client finished his jumpstart correctly,
no hiccups. If we don't get a start notification at the IP level or
sooner, it's possible that a client could barf before we even know it's
trying.
Thanks.
--
=====================
Jeff Kennedy
Unix Administrator
AMCC
jlkennedy at amcc.com
Comments
Got something to say?
You must be logged in to post a comment.
