logger breaks rhel5 boot

Vernon Schryver vjs@calcite.rhyolite.com
Fri May 9 13:34:37 UTC 2008


> From: "Mihai Vintila" <mihaiv@4psa.com>

> Logger from dcc installs itself in /usr/sbin 

On the contrary, nothing in the DCC tarball is installed in /usr/sbin
with the default ./configure parameters.
There is a file named logger in the misc directory of the DCC source,
but it is installed with the Makefile parameter $(DCC_BINDIR) along
with the other DCC specific programs that need not and so should not
be in any directory in the PATH environment variable (or $path for csh,
tcsh, etc.) for any user, including the DCC `./configure --with-uid=UID`
user.

If the DCC misc/logger file is being installed in /usr/sbin, it is only
because of a surprising and evidently unwise choice for
`./configure --libexecdir=DIR` or perhaps `./configure --homedir=HOMEDIR`

Note that have long been working, presumably rebooting installations
of the DCC code on CentOS includint at least versions 4.2,, 4.3, and 5.
Besides references in this mailing list, see some of the hits for
http://www.google.com/search?q=centos+dcc+configure


>                                              this breaks redhat/centos =
> boot since logger from dcc does not support -i  parameter=20
> Affected line : /etc/sysconfig/network-scripts/network-functions:      =
> logger -p local7.notice -t "NET" -i "$0 : updated /etc/resolv.conf";
>
>
> Logger script should support all parameters even if it does nothing with =
> them
> usage: logger [-is] [-f file] [-p pri] [-t tag] [-u socket] [ message =
> ... ]

While `logger -i` is common among `logger` programs on UNIX-like systems,
it is impossible for anything in the DCC tarball to be an upward
compatible replacement for all varients of any program commonly found
in UNIX varients.  There is just too much variation.  The DCC logger
script exists only because of just such variations in the common logger
program.

The DCC logger script is only a wrapper for the local logger program
used when the local program lacks `logger -s`.  Not only would it be
too ugly to force other applications to run the DCC logger script that
would then run the real logger program, the DCC logger script does the
wrong thing for applications that do not want their messages sent to
stderr.

One might argue that the DCC logger script should be named something
like dcc-logger, but that is unnecessary.  It is better to install
the DCC internal programs in their own directory where they cannot
bother other applications.


Vernon Schryver    vjs@rhyolite.com



More information about the DCC mailing list

Contact vjs@rhyolite.com by mail or use the form.