Krzys Majewski wrote:
> This the potato sysklogd and a noflushd compiled from the
> sources in woody.
> Presumably the problem is noflushd logging a "Spinning
> down..." message, which gets flushed to the hard drive, heh.
> Now, I've prefixed all the filenames in /etc/syslog.conf with
> "-", like
Thanks for reply, Joey.
Both daemons seem to start fine, but do not seem to be logging
anything. 'plog' returns nothing, probably because ppp.log is empty.
Okay, /dev/log is a socket, but do you have any idea why it is not being
created?
-rw-r- 1 root adm 0 Jun 13 06:48 a
As far as I know, this is "normal" behavior. There was apparently some
sort of BadThing (TM) that occurred if syslogd did not pause on startup.
I suppose if you reboot a lot it gets annoying ...
At any rate I just hunted through the source code ... I found a flag
KLOGD_START_DELAY in the Makefile
Victor Torrico wrote:
>
> Alex Romosan wrote:
> >
> > i think the problem is with the latest dpkg packages (1.4.0.14). i've
> > downgraded to 1.4.0.8 from unstable and it works fine. it seemed to
> > have worked fine up until 1.4.0.13 but i could be wrong.
> >
> > --alex--
> >
>
> You hit the nai
On Fri, 9 May 1997, Alex Romosan wrote:
> i think the problem is with the latest dpkg packages (1.4.0.14). i've
> downgraded to 1.4.0.8 from unstable and it works fine. it seemed to
> have worked fine up until 1.4.0.13 but i could be wrong.
Along these lines, does anybody know why syslogd in pack
Alex Romosan wrote:
>
> i think the problem is with the latest dpkg packages (1.4.0.14). i've
> downgraded to 1.4.0.8 from unstable and it works fine. it seemed to
> have worked fine up until 1.4.0.13 but i could be wrong.
>
> --alex--
>
You hit the nail on the head and fixed my problem. I was
i think the problem is with the latest dpkg packages (1.4.0.14). i've
downgraded to 1.4.0.8 from unstable and it works fine. it seemed to
have worked fine up until 1.4.0.13 but i could be wrong.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the min
> "Mikael" == Mikael Hallendal <[EMAIL PROTECTED]> writes:
Mikael> Hi! Why is it that the new sysklogd in 'unstable' dependens
Mikael> on an old bash and not on the new one?
Mikael> Is there any packages that dependes on bash 2.0-2 or is it
Mikael> just to downgrade it to the one in secti
On Wed, 12 Jun 1996, Richard Lovison wrote:
> I just discovered that my system logging utilities stopped functioning two
> days ago after I did some upgrades. I attempted to reinstall sysklogd
> 1.3-6 but received the following error message:
>
> warning: /etc/init.d/sysklogd doesn't exist duri
Richard Lovison writes ("sysklogd upgrade"):
> I recently upgraded from syslogd 1.3-2 to sysklogd 1.3-6 manually using
> dpkg. When I started dselect I was informed that syslogd and sysklogd were
> in conflict, the configuration files for syslogd were still on the system.
> I proceeded to purge sys
Both of your problems are caused by the named pipe /dev/xconsole filling
up, which is a known problem. I get the same behaviour here on my
machine. I suspect named pauses for so long because it has a relatively
large amount of logging to report, and hence is most likely to be the
process which ca
11 matches
Mail list logo
