Re: redirect to syslog
- From: anno4000@xxxxxxxxxxxxxxxxxxxxxxx (Anno Siegel)
- Date: 22 Nov 2005 17:46:28 GMT
Jim Gibson <jgibson@xxxxxxxxxxxxxxxxx> wrote in comp.lang.perl.misc:
> In article <1132597230.814493.91670@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>, sbk
> <skendric@xxxxxxxxx> wrote:
>
> > hi,
> >
> > i have an application which insists on writing to its own log file,
> > rather than to syslog. rather than modifying the application, i would
> > like to intercept what it sends to this file and redirect it to syslog
>
> Then it will be necessary to modify that program. It is not possible,
> as far as I know, to externally change output to a regular file into
> output to a named pipe, unless there are some redirection tricks I
> don't know about.
Why on earth not? Instead of letting the program create its log file,
pre-create it as a named pipe and let the program pick it up. A demon
can listen on the read end and forward the info to syslog. No tricks
involved. I'm not saying it's the best solution, but it's certainly
possible.
[sensible alternatives snipped]
Anno
--
If you want to post a followup via groups.google.com, don't use
the broken "Reply" link at the bottom of the article. Click on
"show options" at the top of the article, then click on the
"Reply" at the bottom of the article headers.
.
- Follow-Ups:
- Re: redirect to syslog
- From: Jim Gibson
- Re: redirect to syslog
- References:
- redirect to syslog
- From: sbk
- Re: redirect to syslog
- From: Jim Gibson
- redirect to syslog
- Prev by Date: Re: Modify string on command line
- Next by Date: Re: Net::Server and data sharing
- Previous by thread: Re: redirect to syslog
- Next by thread: Re: redirect to syslog
- Index(es):
Relevant Pages
|
|