I think MS doesn't recommend that LocalSystem account be used for any
network-related work. In theory, LocalSystem is not allowed to access
any network resources at all. So, you can run tracd under a specific
account, or under NetworkService. For this specific situation,
NetworkService probably won't work well because of drive mapping.
You can experiment with using "net use /persistent:yes" instruction to
see if it improves anything, although "officially" it only means that
once initiated, the mapping will be restored on the next logon of the
user to created it.
HTH,
Sergey.
Todor Totev wrote:
Now how to fix it?
1. Run tracd/Apache under your account.
2. Make LocalSystem account to see z: as share.
If you are using tracd as a service, you can modify its source to execute
"NET use z: \\server\trac_share" near its start.
3. If you are using Apache I really dont know how to handle this.
I can speculate that if you use the tool from sysinternals.com
that allows you to log as localsystem (I can't remeber its name right
now)
and run Explorer, you can make permanent network share mapping that
will be restored on reboot. But I have never checked that scenario
and can neither tell if it will work nor I can tell the security
ramifications.
_______________________________________________
Trac mailing list
[email protected]
http://lists.edgewall.com/mailman/listinfo/trac
