[471] in athena10
Re: counterlog design discussion
daemon@ATHENA.MIT.EDU (Kenneth Arnold)
Wed Aug 27 14:01:46 2008
Message-ID: <48B59529.5060504@mit.edu>
Date: Wed, 27 Aug 2008 13:55:53 -0400
From: Kenneth Arnold <kcarnold@MIT.EDU>
MIME-Version: 1.0
To: ghudson@mit.edu
CC: athena10@mit.edu
In-Reply-To: <200808271637.m7RGbfZK017153@outgoing.mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
ghudson@MIT.EDU wrote:
> 2. Phoning home via syslogging requires a syslog configuration with
> central logging, which I don't think we want to put into
> -clients. So I'm in the market for a lightweight way to phone
> home with a machine identifier. Doesn't have to be particularly
> reliably. The options I can think of are:
>
> * Use nc to transmit a network syslog packet to wslogger. I
> don't know how hard this is since I'm not sure what network
> protocol syslog uses. It might be harder to implement (1a)
> this way since SIPB doesn't run a logging server.
>
Python's batteries include a 'syslog' package that will do exactly that
in a line or two. But why syslog?
> * Use wget or curl to post the data to a URL on the apt server
> (athena10.mit.edu or debathena.mit.edu as found in
> sources.list), and have a CGI script record it. Adds a little
> complexity to the web server setup but shouldn't be too bad.
>
Could send an email also. Or write to some special AFS location (don't
know about the permissions there). Depends on how much you want to care
about this data getting falsified.
-Ken
