i'd suggest logging to a loghost, in clasic syslog.conf: *.* @loghost will send all logs to loghost machine, which has to be added to your hosts file. if you are using syslog-ng, it's slightly more complicated, but gives you more advantages! syslog-ng can send via TCP, so you can encrypt it with stunnel .. having an old-skool syslog at port 514(udp) is a potential security hole, but i do use it localy. once tried to have it over the internet - had about 5 people attacking me after a few hours!
i can post a syslog-ng.conf file if you wish .. i couldn't get stunnel working yet ;( but there tutorials ..
On Tue, Jan 01, 2008 at 10:18:13PM +0100, Derek Holzer wrote:
Either way could work, the ramdisk is a particularly good idea. Unless the installation is networked, there's not too much need for logfiles in the classic server or multiuser environment sort of sense. You could probably also just disable to logging daemon by removing it from the boot scripts using rc-update (on Gentoo at least, or with another distro-specific equivalent). I imagine that logging would simply just fail quietly if the partition were read-only... I mean, what would log the fact that the logs weren't logging? ;-)
best, d.
Peter Plessas wrote:
- Derek Holzer derek@umatic.nl [2007-12-31 18:47]:
So I made sure to mount all my drives read-only, and that everything would start from a script on power-up. Having the whole operating system on a Flash card/USB stick (again, no logging, read-only) is also quite
How do you do that? Do you mount /var/log as ramdisk which gets erased at reboot, or do you tell every service/daemon not to log?
-- derek holzer ::: http://www.umatic.nl ::: http://blog.myspace.com/macumbista ---Oblique Strategy # 184: "Where is the edge?"
PD-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list