 Relationships |
|
| Anonymous | Login | 2024-04-30 15:15 CEST |
| Main | My View | View Issues |
| Viewing Issue Simple Details [ Jump to Notes ] | [ View Advanced ] [ Issue History ] [ Print ] | ||||||
| ID | Category | Severity | Reproducibility | Date Submitted | Last Update | ||
| 0003965 | [sudo] packaging | feature | always | 2009-10-15 02:13 | 2012-07-25 13:45 | ||
| Reporter | dkohfield | View Status | public | ||||
| Assigned To | maciej | ||||||
| Priority | normal | Resolution | fixed | ||||
| Status | closed | ||||||
| Summary | 0003965: sudo has 'logfile' hard-coded to /var/opt/csw/sudo/logs/sudolog | ||||||
| Description | sudo has 'logfile' hard-coded to /var/opt/csw/sudo/logs/sudolog. This can be overridden in sudoers. Suggested approach is to remove hard-coded logfile and leave use of logfile a flag configuration within sudoers | ||||||
| Additional Information | |||||||
| Tags | No tags attached. | ||||||
| Attached Files | |||||||
|
|
|||||||
|
Relationships |
|
|
Notes |
|
|
(0006880) gadavis (reporter) 2009-10-19 21:09 |
Additionally, the package doesn't create the path /var/opt/csw/sudo/logs/sudolog on installation so you get a bunch of complaint emails from sudo after the package is upgraded. |
|
(0007593) maciej (reporter) 2010-03-03 20:08 |
The other issue has been resolved, the path is now created. I don't understand the bit about the hardcoded log path. If you don't give the option at the configure stage, it still has a default. Do you mean that if the configure option is used, it cannot be changed in sudoers? |
|
(0007595) gadavis (reporter) 2010-03-03 20:14 |
By default, sudo just logs to syslog rather than going to a separate log file location. I believe this is what the original reporter is referring to. |
|
(0010058) jh (developer) 2012-07-25 13:45 |
sudo is build now with --with-logging=both so it can log to syslog or to a log file. |
| Copyright © 2000 - 2008 Mantis Group |  |
