Logging, Syslog and Log Anaylsys Forums
September 08, 2010, 08:50:34 am
Welcome,
Guest
. Please
login
or
register
.
Did you miss your
activation email?
1 Hour
1 Day
1 Week
1 Month
Forever
Login with username, password and session length
News
:
Home
WIKI
BLOG
Help
Search
Recent Topics
GoogleTagged
Login
Register
Logging, Syslog and Log Anaylsys Forums
>
Forums
>
Syslog & syslogd
>
syslogd and pipe
Pages: [
1
]
« previous
next »
Print
Author
Topic: syslogd and pipe (Read 1188 times)
luongo
Newbie
Offline
Posts: 1
syslogd and pipe
«
on:
August 03, 2009, 06:59:13 pm »
Hello,
I have syslogd writing to a named pipe, which is read by another client program. At the same time, I also have logrotate running to keep the log file small. As part of the post action of logrotate, I send HUP signal to syslogd. The reason I do this is I think since the old file is now with new name and a new log file is created with same name, I want to force syslogd to open the log file again so that it does not write to the old log file which has a different name now. However, the problem I have is that after the syslogd is restarted, the named pipe seems to be clogged, the client doesnt seem to receive any message from the pipe. But if I manually does a cat <named-pipe>, I can see the messages. Is there anything I miss when restarting syslogd? Do I need to make the client program that reads the pipe also reopen those pipes?
Thanks in advance for your help.
-LG
Logged
Admin
Administrator
Newbie
Offline
Posts: 178
Re: syslogd and pipe
«
Reply #1 on:
August 07, 2009, 03:47:09 pm »
I suspect that you need to hup the app that is reading from the named pipe.
Logged
Pages: [
1
]
Print
GoogleTagged:
syslogd pipe named pipe
« previous
next »
Jump to:
Please select a destination:
-----------------------------
Forums
-----------------------------
=> Syslog & syslogd
=> syslog-ng
=> Log Data and Analysis
=> Windows Event Log
=> Web Server Logs
=> Security Event Management
=> General Discussion
===> Red Light District
Loading...