On Sat, 2020-03-28 at 10:04 -0500, Bruce Dubbs via lfs-dev wrote:
> On 3/28/20 7:48 AM, Pierre Labastie via lfs-dev wrote:
> > On Sat, 2020-03-28 at 00:04 -1000, Dean Takemori via lfs-dev wrote:
> > > The version of sysklogd that LFS uses (1.5.1 - from
> > > https://www.infodrom.org/projects/sysklogd/) has not been updated
> > > in
> > > over 5 years (late 2014).
> > >
> > > There is a successor project with active development (
> > > https://github.com/troglobit/sysklogd), which consolidates klogd
> > > into
> > > syslogd, adds remote logging, autotools build system among many
> > > other
> > > things.
> > >
> > > With standard
> > > ./configure --prefix=/usr —-sbindir=/sbin --sysconfdir=/etc --
> > > localstatedir=/var
> > > make
> > > make install
> > >
> > > and the attached boot script patch, this new version has been
> > > working
> > > quite well in my setup
> > >
> > > Should LFS mgirate over?
> > +1, but maybe wait for things to settle: there have been 7 releases
> > in
> > 5 months...
>
> What are the real advantages? What we have now seems to work pretty
> well. Both syslogd and klogd are in the same package and build in
> less
> than 0.1 SBU (one second in my log). There is only one bootscript
> that
> launches both daemons. syslogd handles remote logging.
>
> We do have a couple of minor seds, but I am reluctant to change a
> working package just because something is newer.
From what I see on the site, it implements a new rfc for syslog, and
fix a couple of glitches with remote logging. I think the code itself
is pk, because it has a long history on {free,net}bsd. It is the
porting to autotools, which needs still some polishing...
Pierre
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
