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
sysklogd used to work fine. Recently it has started dumping core. I
purged and reloaded the -15 version of the package and it still does the
same thing.
Here is the error message during boot (runlevel 2):
Starting system log daemon: syslogd klogd/etc/init.d/sysklogd: line
51: 429 Segmentation
5 matches
Mail list logo