Re: [Etherboot-developers] Error reporting...
Brought to you by:
marty_connor,
stefanhajnoczi
|
From: <ke...@us...> - 2001-09-11 20:07:13
|
>> Just a thought from a non-network expert, but what about using syslog? >> It seems like it would be an easy packet to put together and send, and >> a syslog daemon would be easier to set up than SNMP. I don't know if >> you can broadcast a syslog packet or not, so you might have to have an >> address. This could be handled as a DHCP option if Etherboot has >> gotten that far, or maybe a compile-time option for when DHCP is not >> successful. > >That actually sounds a little better. If syslog has the property >where you can send a single udp packet that is a valid option as well. >Especially if I can broadcast a syslog packet... AFAIK syslog requires a directed packet. So to find the server you would need to extract it from the DHCP options. BTW, I don't see a syslog server option offhand, perhaps option 7 (MIT-LCS UDP log server) is the one to use. The other reason for preferring SNMP is that syslog is normally a reporting facility and that one would have to set up something to take action on the report; special syslog daemon, grep /var/log/messages, whereas SNMP agents can issue alerts, execute code, etc. Also syslog is Unixish as pointed out. |