Mantis - sudo
Viewing Issue Advanced Details
3965 packaging feature always 2009-10-15 02:13 2012-07-25 13:45
dkohfield  
maciej  
normal  
closed  
fixed  
none    
none  
0003965: sudo has 'logfile' hard-coded to /var/opt/csw/sudo/logs/sudolog
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
Issue History
2009-10-15 02:13 dkohfield New Issue
2009-10-15 02:28 mwatters Severity minor => feature
2009-10-15 02:28 mwatters Status new => assigned
2009-10-15 02:28 mwatters Category other => packaging
2009-10-15 02:28 mwatters Assigned To => mwatters
2009-10-19 21:09 gadavis Note Added: 0006880
2010-03-03 20:03 maciej Assigned To mwatters => maciej
2010-03-03 20:08 maciej Note Added: 0007593
2010-03-03 20:14 gadavis Note Added: 0007595
2012-04-13 10:23 dam Project sudo_common => sudo
2012-07-25 13:45 jh Note Added: 0010058
2012-07-25 13:45 jh Status assigned => closed
2012-07-25 13:45 jh Resolution open => fixed

Notes
(0006880)
gadavis   
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   
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   
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   
2012-07-25 13:45   
sudo is build now with --with-logging=both so it can log to syslog or to a log file.