Re: fifo log problem

In message <200811170603.mAH63Q54011870@xxxxxxxxxxxxxx>, Mike Tancsa writes:

I could fear that you have two fifologs running at the same time,
possibly as a result of syslogd doing something strange on sighup...

There is nothing really strange about the config. Any idea on how to resolve?

Not right now, there is nothing that rings a bell here and I have not
seen it on any of my systems.

As I said, I would fear that the SIGHUB to syslog results in some
weird config where two writers are competing or something like that
but that is purely a guess...

--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@xxxxxxxxxxx | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • RE: FreeBSD 4.7 Syslogs
    ... Copyright 1992-2002 The FreeBSD Project. ... Invalid command or syntax. ... config> di lnc0 ... Well since you are new to FBSD and since the syslogd -d commands ...
    (freebsd-questions)
  • Re: getting 404 for all .NET 2.0 aspx files?
    ... In Web Server Extensions, ASP.NET 2.0 was prohibited. ... Seems rather strange this would be the config out of the box, as Sharepoint, ... .NET Framework 2.0 is installed. ...
    (microsoft.public.windows.server.sbs)
  • Re: Very unusual problem - Explorer very slow
    ... Right-click is slow or weird behavior caused by context menu handlers: ... > My config: ... > application install. ... Really strange. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: fifo log problem
    ... The strange thing is that reading from it gives ... possibly as a result of syslogd doing something strange on sighup... ...
    (freebsd-stable)
  • Re: Syslog Server
    ... i've configured the logging host and facility ... > it's just seems that the syslog server isn't listening on port UDP/514. ... Check what you have in config file /etc/sysconfig/syslog ... syslogd does not bind itself to 514/udp port by ...
    (comp.os.linux.security)