Hello.
Problem
During build of distributions with Yocto Project (and others) the shadow-native tools are spamming host's syslog with image-related information, which aren't relevant.
Current workaround
There's a patch that hardcodes turning the syslog off that Yocto uses. This works, but it is a Yocto-specific hack.
Proposed solution
Add a proper configure option, for example ./configure --disable-syslog. When --disable-syslog is used, configure.h should define something like USE_SYSLOG 0, so that all SYSLOG() calls become no-ops without any #if 1 hacks.
This would allow tools like Yocto simply do something like PACKAGECONFIG[syslog] = "--enable-syslog,--disable-syslog,,," and eventually get rid of the ugly patch.
If you ok with this feature, I am ready to prepare a draft patch to apply it.
Hello.
Problem
During build of distributions with Yocto Project (and others) the
shadow-nativetools are spamming host's syslog with image-related information, which aren't relevant.Current workaround
There's a patch that hardcodes turning the syslog off that Yocto uses. This works, but it is a Yocto-specific hack.
Proposed solution
Add a proper configure option, for example
./configure --disable-syslog. When --disable-syslog is used, configure.h should define something likeUSE_SYSLOG 0, so that all SYSLOG() calls become no-ops without any #if 1 hacks.This would allow tools like Yocto simply do something like
PACKAGECONFIG[syslog] = "--enable-syslog,--disable-syslog,,,"and eventually get rid of the ugly patch.If you ok with this feature, I am ready to prepare a draft patch to apply it.