Linux - General This Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
|
04-22-2003, 03:20 PM
|
#1
|
Senior Member
Registered: Nov 2002
Location: British Columbia, Canada
Distribution: Gentoo x86_64; FreeBSD; OS X
Posts: 3,764
Rep:
|
syslog
Hello all,
I made some changes to my syslog.conf file, but they seem not to have taken effect yet. Is there a command I need to run to get syslog to reread this file? Do I need to restart syslog?
The syslog and syslog.conf man pages don't have the answer.
Any help appreciated.
|
|
|
04-22-2003, 03:26 PM
|
#2
|
Member
Registered: Sep 2002
Location: .at
Distribution: SuSE, Knoppix
Posts: 532
Rep:
|
either do a "/etc/init.d/syslogd restart" or "kill -1 $PID_OF_SYSLOGD"
.......
man syslogd:
[...]
Syslogd reacts to a set of signals. You may easily send a
signal to syslogd using the following:
kill -SIGNAL `cat /var/run/syslogd.pid`
SIGHUP This lets syslogd perform a re-initialization. All
open files are closed, the configuration file
(default is /etc/syslog.conf) will be reread and
the syslog(3) facility is started again.
[...]
|
|
|
04-22-2003, 03:35 PM
|
#3
|
Senior Member
Registered: Nov 2002
Location: British Columbia, Canada
Distribution: Gentoo x86_64; FreeBSD; OS X
Posts: 3,764
Original Poster
Rep:
|
Hmmm,
I tried
kill -1 41 (syslogd's pid #)
kill -SIGHUP `cat /var/run/syslogd.pid`
kill -SIGHUP 41
None are working. syslogd remains the same pid, and is not being restarted. Thanks for the response though...
|
|
|
04-22-2003, 04:41 PM
|
#4
|
Moderator
Registered: Apr 2002
Location: earth
Distribution: slackware by choice, others too :} ... android.
Posts: 23,067
|
Quote:
None are working. syslogd remains the same pid, and is not being restarted. Thanks for the response though...
|
Do you mean its behaviour didn't change?
The PID shouldn't, that's why you use SIGHUP
in the first place, rather than kill -9 ;)
Cheers,
Tink
|
|
|
04-22-2003, 04:45 PM
|
#5
|
Senior Member
Registered: Nov 2002
Location: British Columbia, Canada
Distribution: Gentoo x86_64; FreeBSD; OS X
Posts: 3,764
Original Poster
Rep:
|
Jeez, excuse my greenness,
I didn't know the pid would be the same, it worked fine.
Thanks for the help guys....
|
|
|
All times are GMT -5. The time now is 10:37 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|