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
On Tue, Jan 01, 2008 at 09:32:35PM +, Andy Farnell wrote:
On Tue, 1 Jan 2008 21:57:18 +0100
[EMAIL PROTECTED] (Peter Plessas) wrote:
* Derek Holzer [EMAIL PROTECTED] [2007-12-31 18:47]:
So I made sure to mount all my drives read-only, and that everything
would start from a
hm ..
how about locks and other stuff ?
there always some things which want to be written to somewhere in /var!
the gentoo runscripts use /var/lib/init.d/
i reckon having a bit of space writable in /var and /tmp symlinked to
/var ..could be usefull, keep one or two day's logs as well and log them
The whole idea of read-only is for two reasons:
1) To protect the HD in case of unexpected shutdowns (which could happen
nightly in a typical museum situation)
2) To preserve the CF memory, which has a limited number of write
cycles, in the case of a HD-less system
If the computer needs to be
* Derek Holzer [EMAIL PROTECTED] [2008-01-02 21:12]:
The whole idea of read-only is for two reasons:
1) To protect the HD in case of unexpected shutdowns (which could happen
nightly in a typical museum situation)
2) To preserve the CF memory, which has a limited number of write
cycles, in
Flash memory, regardless of format, supports only a limited number of
erase/write cycles before a particular sector can no longer be
written. Memory specifications generally allow 10,000[1] to 1,000,000
write cycles. Typically the controller in a CompactFlash attempts to
prevent premature
Come to think of it, are there any Linux distros for x86 architectures
which don't use this multi-user/networked server paradigm and instead
follow the embedded model more closely? This would be very interesting
for exactly the situations I describe, where you would want the computer
to behave
On Wed, 2 Jan 2008, Derek Holzer wrote:
The whole idea of read-only is for two reasons:
1) To protect the HD in case of unexpected shutdowns (which could happen
nightly in a typical museum situation)
The whole idea of a separate volume for /var that you see on Linux, and
the whole idea of
* Derek Holzer [EMAIL PROTECTED] [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
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
* Derek Holzer [EMAIL PROTECTED] [2008-01-01 22:18]:
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
On Tue, 1 Jan 2008 21:57:18 +0100
[EMAIL PROTECTED] (Peter Plessas) wrote:
* Derek Holzer [EMAIL PROTECTED] [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
Can't use logrotate if the partition is mounted readonly. I can see the
point if the idea wasn't to fill up disk space, but my whole idea is to
not write to the disk at all. Symlink is also a good idea, though.
best,
d.
Andy Farnell wrote:
On Tue, 1 Jan 2008 21:57:18 +0100
[EMAIL
For installations, I've always tried to make the computer as
bulletproof as possible. Usually, you have these guards or museum
assistants who simply turn everything off (often with one mains switch!)
every night, for example. You can make whatever documentation you want,
but you can also
Hello Michael,
The keyword I read here is installation, so the first three things on your
list should be reliability, reliability and reliability. Nobody wants to see
This installation is out of order, and you don't want people seeing that
right next to your name while you are 1000 miles away
15 matches
Mail list logo
