Red Hat Bugzilla – Bug 449777
/usr/bin/logger cannot be used when /usr is non-root partition
Last modified: 2009-06-20 00:10:22 EDT
Description of problem:
If the /usr partition is a separate partition from / then it cannot be used to
replace initlog in any init scripts that run before /usr gets mounted.
Version-Release number of selected component (if applicable):
With the below setup, every time.
Steps to Reproduce:
1. Have /usr as a separate partition and use logger in an /etc/sysconfig/modules
logger: command not found
The message gets logged out to the syslog.
This problem occurs when it is necessary to log a message from an init script.
In RHEL4 we used initlog for this purpose. However in RHEL5 the following
message prints out:
WARNING: initlog is deprecated and will be removed in a future release
We take the deprecation seriously and attempted to be proactive about not using
initlog. However due to this bug we do not have a good alternative to the
This request was evaluated by Red Hat Product Management for inclusion in a Red
Hat Enterprise Linux maintenance release. Product Management has requested
further review of this request by Red Hat Engineering, for potential
inclusion in a Red Hat Enterprise Linux Update release for currently deployed
products. This request is not yet committed for inclusion in an Update
Just a note. This fix is busted as it relocates logger from /usr/bin to /bin. This will cause problems for anyone that is calling logger via absolute path, including the redhat-lsb package. See bug 461266.
*** Bug 461266 has been marked as a duplicate of this bug. ***
(In reply to comment #5)
> Just a note. This fix is busted as it relocates logger from /usr/bin to /bin.
> This will cause problems for anyone that is calling logger via absolute path,
> including the redhat-lsb package. See bug 461266.
Fixed. Errata updated. Thanks.
The /usr/bin/logger symlink fix is confirmed with 2.13-0.49.el5.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.