| Jeff Abrahamson on 25 Oct 2004 14:25:03 -0000 |
|
Hey, that's cool. Thanks.
But it looks like the host on which the program runs has to be
configured to log to my machine. This wouldn't happen. Plus, I don't
have control over where my program is run, I just want to keep tabs on
it.
man syslog
http://docs.python.org/lib/module-syslog.html
Pythons logging module might be possible, though. I see that there's
socket support. I just have to arrange, again, for a reliable
listener.
http://docs.python.org/lib/module-logging.html
I probably could use inetd, but I'm a bit worried, again, about the
UDP close problem. I could also use TCP instead and let inetd handle
the details for me.
Of course, then I'd have to install inetd, which I normally don't
install for concern about security.
-Jeff
On Mon, Oct 25, 2004 at 10:04:51AM -0400, Dan Widyono wrote:
> [11 lines, 58 words, 556 characters] Top characters:_ nlioeat
>
> syslog allows logging to remote machines. logger(1) program makes it easy to
> interface to syslog. also syslog(2) system call. Python has an API as well :)
>
> Dan W.
>
> > The program in question is running on a different machine on a
> > different subnet.
> ___________________________________________________________________________
> Philadelphia Linux Users Group -- http://www.phillylinux.org
> Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce
> General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
--
Jeff
Jeff Abrahamson <http://www.purple.com/jeff/> +1 215/837-2287
GPG fingerprint: 1A1A BA95 D082 A558 A276 63C6 16BF 8C4C 0D1D AE4B
A cool book of games, highly worth checking out:
http://www.amazon.com/exec/obidos/ASIN/1931686963/purple-20
Attachment:
signature.asc
|
|