Trac-admin fails to hotcopy without write permession

[jlisee]

Issue

If you have logging enabled and a user who just has read access to the project attempts a hotcopy, trac/scripts/admin.py attempts to create an Environment object which accesses the log. The requires write access to log file which of course the user does not have. A quick examination of the trunk reveals the same behavior.

Possible Solutions

• There could be a —no-log option added to the hotcopy command that set the config file options such that not logging will be performed before the hotcopy and then restores them afterwards.
• Slightly harder but not user action required there could be an os call to determine whether user has write access to the log file. If they don't have write access apply the method above to suppress the error.

Problems Issues

I am not sure if this runs counter to the reason for logging. With this option users could be silently duplicated the trac environment. Although they can do this already through the standard unix 'cp' command. Which won't be recored in the log at all.

[Emmanuel Blot]

If you want to run admin tasks without admin rights, use syslog instead of a log file to avoid this kind of troubles.