Greg Ercolano wrote:
Jeff Yana wrote:
Not sure what cleared this problem up but my suspicion is that the
artist has assigned an incorrect path to the imagedir. Why this caused
the cannot create log file error is beyond me. Any thoughts anyone?
Sounds like shadowy file server stuff.. possibly old data being
cached on this one machine, either an old scene file, or a bad
cached interpretation of the directory.
This might put suspicion on the file server's configuration of
opportunistic locking.
I've seen eg. Samba servers have trouble with op locks, for instance
on my own network I have oplocks turned off to prevent clients caching
incorrectly:
--- snip: smb.conf excerpt
# DISABLE OPLOCKS TO ALLOW UNIX AND NT TO ALTER SERVER DATA
# If no: clients won't cache, but will stay in sync
# If yes: clients cache, but out of sync with unix
#
oplocks = no
--- snip
Without that setting, my windows machines would often not see
changes made to files from other machines. I've seen this at
other companies too; disabling oplocks usually fixes it.
If it happens again, troubleshoot from the DOS prompt directly
at the machine having the problem. Do it quickly, since if it
is a caching problem, it may mysteriously 'solve itself' when
the cache expires.
Greg-
I think your suspicions are correct. Many artists accessing our Linux
Server have had trouble with file systems/path names not updating in the
RUSH submit dialog, leading to much confusion (and misdirected blame)
vis a vis RUSH. There has even been a whole host of problems getting
Windows explorer on some machines to accurately refresh, or not refresh
at all.
Honestly, the Oplocks setting in the smb.conf, while obvious now, never
occured to me.
Good suggestion, thanks.
Jeff
|