Summary: | sys-apps/logwatch config file location | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Georgi Georgiev <chutz+bugs.gentoo.org> |
Component: | Current packages | Assignee: | Jared H. Hudson (RETIRED) <jhhudso> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alessandro.pisani |
Priority: | Normal | ||
Version: | 1.4_rc1 | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Georgi Georgiev
2003-01-05 11:11:21 UTC
mainly because AFAIK /etc/log.d is a RedHat extension and, if I remember it right, in some other distros/progs /etc/log.d is used by other applications (do not remember which one). So, when I originally wrote the ebuild I found more correct to use the directory where the program resides and to symlink it on /etc with a unique name (logwatch) instead of log.d . It seemed to be a reasonable alternative, btw I might be wrong... PS: you can't make the perl script use /etc directly since the config file path is hardwired in the script itself (in must be in scripdir/conf). I created the symlink on /etc as an helper for the users, so they can easily find the config instead having to search it in /usr. This seemed reasonable to me too; btw, again, I might be wrong... bye, Alessandro Agreed. New ebuild conforms as suggested. sys-apps/logwatch-4.3.2 |