Once again, I'm back with a seemingly odd situation. Running my server
on Mandrake 10.1.
Syslogd has been showing a non-stop list of log entries on my server's
monitor. The server is starting in console mode (X, XFS and DM are not
set to start on bootup, but can be started manually), and it
On Saturday 12 March 2005 01:12 am, Mr. Geek wrote:
Once again, I'm back with a seemingly odd situation. Running my server
on Mandrake 10.1.
Syslogd has been showing a non-stop list of log entries on my server's
monitor. The server is starting in console mode (X, XFS and DM are not
set to
Aron Smith wrote:
On Saturday 12 March 2005 01:12 am, Mr. Geek wrote:
Once again, I'm back with a seemingly odd situation. Running my server
on Mandrake 10.1.
Syslogd has been showing a non-stop list of log entries on my server's
monitor. The server is starting in console mode (X, XFS and DM are
On Sat, 12 Mar 2005 06:50:12 -0500
Mr. Geek [EMAIL PROTECTED] wrote:
How do I prevent syslogd from showing events on the screen? Is it not
normal to simply pass these events to the correct log file in /var/log
?
question, can you confirm that any of the messages being displayed on
the
Steve Jeppesen wrote:
On Sat, 12 Mar 2005 06:50:12 -0500
Mr. Geek [EMAIL PROTECTED] wrote:
How do I prevent syslogd from showing events on the screen? Is it not
normal to simply pass these events to the correct log file in /var/log
?
question, can you confirm that any of the messages being
Mr. Geek wrote:
Once again, I'm back with a seemingly odd situation. Running my server
on Mandrake 10.1.
Syslogd has been showing a non-stop list of log entries on my server's
monitor. The server is starting in console mode (X, XFS and DM are not
set to start on bootup, but can be started
Mikkel L. Ellertson wrote:
It actualy sounds like the daemons are not running. As root, run
service syslog status and make sure both syslogd and klogd are
running. If they both report that they are running, then chack
/etc/syslog.conf - there should be only one entry that uses *, tty,
tty0, or
Mr. Geek wrote:
Mikkel L. Ellertson wrote:
It actualy sounds like the daemons are not running. As root, run
service syslog status and make sure both syslogd and klogd are
running. If they both report that they are running, then chack
/etc/syslog.conf - there should be only one entry that uses
Mikkel L. Ellertson wrote:
You should not be getting the error. You may want to run
rpm -V syslogd and see what errors it reports. You may also want to
run a package like chkrootkit to make sure your box wasn't hacked. A
look at the log files is also in order. The /etc/syslog.conf file got
Mr. Geek wrote:
Mikkel L. Ellertson wrote:
You should not be getting the error. You may want to run
rpm -V syslogd and see what errors it reports. You may also want to
run a package like chkrootkit to make sure your box wasn't hacked. A
look at the log files is also in order. The
Mikkel L. Ellertson wrote:
One thing I forgot to put in the last message - the changes you make in
/etc/syslog.conf will not take affect untill you restart syslog.
Normaly, I would run service syslog restart to do this. But you may
have to fix what ever is wrong in /etc/sysconfig/syslog first.
Mr. Geek wrote:
Mikkel L. Ellertson wrote:
One thing I forgot to put in the last message - the changes you make
in /etc/syslog.conf will not take affect untill you restart syslog.
Normaly, I would run service syslog restart to do this. But you may
have to fix what ever is wrong in
Mikkel L. Ellertson wrote:
Mr. Geek wrote:
Mikkel L. Ellertson wrote:
One thing I forgot to put in the last message - the changes you make
in /etc/syslog.conf will not take affect untill you restart syslog.
Normaly, I would run service syslog restart to do this. But you may
have to fix what
On Fri, 13 Dec 2002 10:07, Stephen Kuhn wrote:
On Fri, 2002-12-13 at 07:28, George Baker wrote:
Last night a process called syslogd -m started and my hard drive went
mad for over 7 hours until I killed the process. What is it doing and how
often - will it always carry on for so long or was
Last night a process called syslogd -m started and my hard drive went mad
for over 7 hours until I killed the process. What is it doing and how
often - will it always carry on for so long or was it just a once off due to
me moving MDK to a new drive??
Please advise
George
Want to buy your
On Fri, 2002-12-13 at 07:28, George Baker wrote:
Last night a process called syslogd -m started and my hard drive went mad
for over 7 hours until I killed the process. What is it doing and how
often - will it always carry on for so long or was it just a once off due to
me moving MDK to a new
16 matches
Mail list logo
