| Summary: | Improve sys-libs/pam tallylog elog message handling | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Petteri Räty (RETIRED) <betelgeuse> |
| Component: | [OLD] Core system | Assignee: | PAM Gentoo Team (OBSOLETE) <pam-bugs+disabled> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
*** This bug has been marked as a duplicate of bug 344499 *** |
elog "" elog "Because of a bug present up to version 1.1.1-r2, you might have" elog "an executable /var/log/tallylog file. If it is so, you can safely" elog "correct it by running the command" elog " chmod -x /var/log/tallylog" elog "" I think it would be better if the ebuild looked at if ${ROOT}/var/log/tallylog is broken or not.