Newsgroup follow up.
OK, after working with Craig earlier this week, I was able to determine
the exact combo of events it took to replicate this.
Turned out these specifics were needed to make this problem show up:
o Rush version 102.42a9 on both machines
o Submit from a Tiger workstation with "Submit Host:" pointing at a leopard jobserver
o Submitting user has no account on the jobserver, just their workstation
o Rush configured to force all renders to run as "render" user
o "render" user has a valid account on all machines (workstation and jobserver)
o Job submitted with a jobdonecommand
With this combo, the renders run ok, but the /jobdonecommand/ fails to run on
the leopard machine with this series of errors in the log:
>07/17,20:05:03 SECURITY RUSH: uid '0' outside configured range 100-65000
>07/17,20:05:03 INFO jobdonecommand 'ls' failed for jobid=leopard.2: RUSH: uid '0' outside configured range 100-65000
Now that I've got the problem canned, and replicated here at my office,
I should have it solved soon -- pretty sure now it's a bug in Rush.
|