Re: [lfs-dev] sysklogd replacement
On 2020-10-31 3:00 am, Tim Tassonis via lfs-dev wrote: > > > On 10/29/20 1:31 PM, Bruce Dubbs via lfs-dev wrote: >> On 10/29/20 12:49 AM, Geoff Swan via lfs-dev wrote: >>> Hi, >>> >>> I've build many LFS systems using sysklogd as per the book. However new >>> remote logging systems are asking for logging features that sysklogd >>> does not possess. >>> These include port changes (other than what is in /etc/services, which >>> is where syklogd picks up its port) and logs being sent over TCP with >>> TLS on a configurable port (RFC5424/25). >>> I examined a couple of replacements and see that rsyslog appears to >>> include these features . >>> Before starting on replacing the logger in my system build I thought >>> I'd >>> ask the question as to whether any thoughts had been given to upgrading >>> LFS from sysklogd to a more modern package for remote logging? >> >> It's something to consider. I don't think many users actually use >> remote logging over TLS, but it would be nice to have that available. >> >> If you do add rsyslog, would you please get back to us to let us know >> anything you find out including build and configuration instructions. >> We probably would not add instructions for remote logging to the >> book, but a hint for that would be appropriate. > > I do that for myself for years, as I need the additional features > rsyslog brings, so I can contribute some build scripts, if needed. > > Be aware thought that rsyslog is a bit of a maintenance nightmare, as > it requires at least three separate libraries by the same author, > which are not used by anyone/anything else in the whole wide world, > and are not included in the source distribution of rsyslog. > > I have created a scripts that pre-builds them statically inside the > rsyslog source tree, in order not to bloat my system with the > unnecessary overhead of three libraries only needed by it: > > > LIBE=`pwd`/libe export LIBE > > tar xf /lfs-src/libestr-0.1.10.tar.gz > cd libestr-0.1.10 > ./configure --prefix=$LIBE --enable-static --disable-shared --with-pic > make || ext > make install > > cd .. > tar xf /lfs-src/libee-0.4.1.tar.gz > cd libee-0.4.1 > PKG_CONFIG_PATH=$LIBE/lib/pkgconfig ./configure --prefix=$LIBE > --enable-static --disable-shared --with-pic > make || exit > make install > cd .. > > tar xf /lfs-src/libfastjson-0.99.8.tar.gz > cd libfastjson-0.99.8 > PKG_CONFIG_PATH=$LIBE/lib/pkgconfig ./configure --prefix=$LIBE > --enable-static --disable-shared --with-pic > > > make || exit > make install > cd .. > > > # and finally rsyslog > PKG_CONFIG_PATH=$LIBE/lib/pkgconfig ./configure --prefix=/usr > --disable-libgcrypt --disable-liblogging-stdlog > > > > > Bye > > Tim Thanks Tim, I agree with your approach to statically linking the libs that are only of relevance to this package. I'll work with your approach to replace sysklogd in my systems that require remote logging facilities using TCP. - Geoff -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] sysklogd replacement
On 10/30/20 11:00 AM, Tim Tassonis via lfs-dev wrote: On 10/29/20 1:31 PM, Bruce Dubbs via lfs-dev wrote: On 10/29/20 12:49 AM, Geoff Swan via lfs-dev wrote: Hi, I've build many LFS systems using sysklogd as per the book. However new remote logging systems are asking for logging features that sysklogd does not possess. These include port changes (other than what is in /etc/services, which is where syklogd picks up its port) and logs being sent over TCP with TLS on a configurable port (RFC5424/25). I examined a couple of replacements and see that rsyslog appears to include these features . Before starting on replacing the logger in my system build I thought I'd ask the question as to whether any thoughts had been given to upgrading LFS from sysklogd to a more modern package for remote logging? It's something to consider. I don't think many users actually use remote logging over TLS, but it would be nice to have that available. If you do add rsyslog, would you please get back to us to let us know anything you find out including build and configuration instructions. We probably would not add instructions for remote logging to the book, but a hint for that would be appropriate. I do that for myself for years, as I need the additional features rsyslog brings, so I can contribute some build scripts, if needed. Be aware thought that rsyslog is a bit of a maintenance nightmare, as it requires at least three separate libraries by the same author, which are not used by anyone/anything else in the whole wide world, and are not included in the source distribution of rsyslog. I have created a scripts that pre-builds them statically inside the rsyslog source tree, in order not to bloat my system with the unnecessary overhead of three libraries only needed by it: LIBE=`pwd`/libe export LIBE tar xf /lfs-src/libestr-0.1.10.tar.gz cd libestr-0.1.10 ./configure --prefix=$LIBE --enable-static --disable-shared --with-pic make || ext make install cd .. tar xf /lfs-src/libee-0.4.1.tar.gz cd libee-0.4.1 PKG_CONFIG_PATH=$LIBE/lib/pkgconfig ./configure --prefix=$LIBE --enable-static --disable-shared --with-pic make || exit make install cd .. tar xf /lfs-src/libfastjson-0.99.8.tar.gz cd libfastjson-0.99.8 PKG_CONFIG_PATH=$LIBE/lib/pkgconfig ./configure --prefix=$LIBE --enable-static --disable-shared --with-pic make || exit make install cd .. # and finally rsyslog PKG_CONFIG_PATH=$LIBE/lib/pkgconfig ./configure --prefix=/usr --disable-libgcrypt --disable-liblogging-stdlog Thanks Tim. I don't think we want to add that much overhead to LFS, but I'll listen to other opinions. A hint or possibly a BLFS page seems more appropriate. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] sysklogd replacement
On 10/29/20 1:31 PM, Bruce Dubbs via lfs-dev wrote: On 10/29/20 12:49 AM, Geoff Swan via lfs-dev wrote: Hi, I've build many LFS systems using sysklogd as per the book. However new remote logging systems are asking for logging features that sysklogd does not possess. These include port changes (other than what is in /etc/services, which is where syklogd picks up its port) and logs being sent over TCP with TLS on a configurable port (RFC5424/25). I examined a couple of replacements and see that rsyslog appears to include these features . Before starting on replacing the logger in my system build I thought I'd ask the question as to whether any thoughts had been given to upgrading LFS from sysklogd to a more modern package for remote logging? It's something to consider. I don't think many users actually use remote logging over TLS, but it would be nice to have that available. If you do add rsyslog, would you please get back to us to let us know anything you find out including build and configuration instructions. We probably would not add instructions for remote logging to the book, but a hint for that would be appropriate. I do that for myself for years, as I need the additional features rsyslog brings, so I can contribute some build scripts, if needed. Be aware thought that rsyslog is a bit of a maintenance nightmare, as it requires at least three separate libraries by the same author, which are not used by anyone/anything else in the whole wide world, and are not included in the source distribution of rsyslog. I have created a scripts that pre-builds them statically inside the rsyslog source tree, in order not to bloat my system with the unnecessary overhead of three libraries only needed by it: LIBE=`pwd`/libe export LIBE tar xf /lfs-src/libestr-0.1.10.tar.gz cd libestr-0.1.10 ./configure --prefix=$LIBE --enable-static --disable-shared --with-pic make || ext make install cd .. tar xf /lfs-src/libee-0.4.1.tar.gz cd libee-0.4.1 PKG_CONFIG_PATH=$LIBE/lib/pkgconfig ./configure --prefix=$LIBE --enable-static --disable-shared --with-pic make || exit make install cd .. tar xf /lfs-src/libfastjson-0.99.8.tar.gz cd libfastjson-0.99.8 PKG_CONFIG_PATH=$LIBE/lib/pkgconfig ./configure --prefix=$LIBE --enable-static --disable-shared --with-pic make || exit make install cd .. # and finally rsyslog PKG_CONFIG_PATH=$LIBE/lib/pkgconfig ./configure --prefix=/usr --disable-libgcrypt --disable-liblogging-stdlog Bye Tim -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] sysklogd replacement
On 10/29/20 12:49 AM, Geoff Swan via lfs-dev wrote: Hi, I've build many LFS systems using sysklogd as per the book. However new remote logging systems are asking for logging features that sysklogd does not possess. These include port changes (other than what is in /etc/services, which is where syklogd picks up its port) and logs being sent over TCP with TLS on a configurable port (RFC5424/25). I examined a couple of replacements and see that rsyslog appears to include these features . Before starting on replacing the logger in my system build I thought I'd ask the question as to whether any thoughts had been given to upgrading LFS from sysklogd to a more modern package for remote logging? It's something to consider. I don't think many users actually use remote logging over TLS, but it would be nice to have that available. If you do add rsyslog, would you please get back to us to let us know anything you find out including build and configuration instructions. We probably would not add instructions for remote logging to the book, but a hint for that would be appropriate. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
[lfs-dev] sysklogd replacement
Hi, I've build many LFS systems using sysklogd as per the book. However new remote logging systems are asking for logging features that sysklogd does not possess. These include port changes (other than what is in /etc/services, which is where syklogd picks up its port) and logs being sent over TCP with TLS on a configurable port (RFC5424/25). I examined a couple of replacements and see that rsyslog appears to include these features . Before starting on replacing the logger in my system build I thought I'd ask the question as to whether any thoughts had been given to upgrading LFS from sysklogd to a more modern package for remote logging? - Geoff -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] sysklogd
On Sat, 2020-03-28 at 17:59 +0100, Pierre Labastie via lfs-dev wrote:
> 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...
s/pk/ok/ I cannot type
--
http://lists.linuxfromscratch.org/listinfo/lfs-dev
FAQ: http://www.linuxfromscratch.org/faq/
Unsubscribe: See the above information page
Re: [lfs-dev] sysklogd
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
Re: [lfs-dev] sysklogd
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. -- Bruce -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
Re: [lfs-dev] sysklogd
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... Pierre -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
[lfs-dev] sysklogd
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? lfs-bootscripts_sysklogd-2.1.patch Description: Binary data -- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
