Mark Post wrote:
On Mon, May 12, 2008 at 2:51 PM, in message
<[EMAIL PROTECTED]>,
James Melin <[EMAIL PROTECTED]> wrote:
-snip-
Back in the day at the recommendation of the 'Lpar to virtual server'
redbook, I did the bastille hardening which appended this to syslog.conf
Mike et. al. recommended Bastille? I didn't think much of anyone did that any
more.
Someone did, I remember it. I looked at Bastille once and didn't like
it, but obviously some had a different opinion.
-snip-
So this is clearly why syslog has /dev/tty7, 8 and 12 allocated.
You can have the same level of logging, just point them to real files in
/var/log/ somewhere.
More likely the /dev logs duplicate information already logged
appropriately.
Consider logging the information to a central logging system. If you
don't like that idea, delete those lines and practice your replication.
the problem exists on the golden mastet structure on my cloning system and
every linux derived from it, so I suspect the damage was done a long time
ago, back when I knew considerably less than I do now.
-snip-
THe question is.. how do I re-create these device entries so that the are not
regular files anymore?
Change your /etc/syslog.conf. Shut down syslog. Do an "rm /dev/tty7 /dev/tty8
/dev/tty12". Then:
mknod -m 620 /dev/tty7 c 4 7
mknod -m 620 /dev/tty8 c 4 8
mknod -m 620 /dev/tty12 c 4 12
chown root:tty rm /dev/tty7 /dev/tty8 /dev/tty12
1. Will that actually work on a Zed?
2. How will you read them?
I'd configure them out, delete the files and then kill -HUP the logger
--
Cheers
John
-- spambait
[EMAIL PROTECTED] [EMAIL PROTECTED]
-- Advice
http://webfoot.com/advice/email.top.php
http://www.catb.org/~esr/faqs/smart-questions.html
http://support.microsoft.com/kb/555375
You cannot reply off-list:-)
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
