Dylan Penhale wrote:
[posted to rush.general]
|
|> Where does rush map these drives?
|
| Rush does NOT map drives, ever.
|
Sorry, I should have been more clear. Our rush submit scripts have been
modified to map drives but my question is which user are they be mapped as?
As the user the render is running as.
When you look in the log file for the render, see the "RunningAs:"
prompt to see which username the map is assigned to, ie:
###
### geneva.1: 0003
###
--------------- Rush 102.42a2 --------------
-- Host: geneva
-- Pid: 2140
-- Title: TEST
-- Jobid: geneva.1
-- Frame: 0003
-- Tries: 1
-- Owner: 3d (1004/1004)
-- RunningAs: render <---
-- [..]
..in this case, as the user 'render'.
Note that, under windows, Rush runs renders as the user the rushd
service is configured to 'Log On As' (in the services panel).
Rush can't 'become' the submitting user the way it can in unix,
due to limitations in the WIN32 API. (see below)
I assumed they would be mapped as either the domain user that is running
rushd or as the user that is submitting the job (in our case both are the
same).
Not in the case of windows.
This is because Windows has no mechanism similar to Unix's setuid();
there's no way for rush to 'become a user' without having that user's
password. In Unix, 'root' can become anyone without needing a password.
Hope that clears things up.
--
Greg Ercolano, erco@(email surpressed)
Rush Render Queue, http://seriss.com/rush/
Tel: (Tel# suppressed)
Cel: (Tel# suppressed)
Fax: (Tel# suppressed)
|