RE: OT: service-based render can't see mapped drives.

Date : Mon, 4 Dec 2006 15:43:17 -0000
To : <XSI(at)Softimage.COM>
From : "Kim Aldis" <XSI(at)kim-aldis.co.uk>
Subject : RE: OT: service-based render can't see mapped drives.
Would this have anything to do with their ridiculous client license thing,
having to drop fairly quickly otherwise that 10 client limit rapidly fills
up and kills everything on the network?



> -----Original Message-----
> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> Behalf Of Halfdan Ingvarsson
> Sent: 04 December 2006 14:59
> To: XSI(at)Softimage.COM
> Subject: RE: OT: service-based render can't see mapped drives.
> 
> As long as the service sets up those mappings, *or* if the service
> starts as the user that owns the mappings, then you're fine.
> 
> The reason for this timeout thing is that Windows doesn't cache dead
> servers and so *each* and *every* *single* *fucking* *time* it tries
> again with a default (can't change it) timeout of about minute or so.
> So we added a mechanism in XSI to weed out dead paths and stick them in
> a five minute "dead path" cache.
> 
> In this day and age, if something on the network doesn't answer within
> a second, consider it dead. I suspect that this extra long timeout is
> there because their good ol' modem stack doesn't talk to the network
> stack and so just in case you were networking over the modem, it would
> give the modem enough time to dial up and logon.
> 
> On Linux it just simply works. (See Alan? I've got nothing against
> Linux :-)
> 
>  - ½
> 
> -----Original Message-----
> From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> Behalf Of Kim Aldis
> Sent: 4-Dec-06 07:35
> To: XSI(at)Softimage.COM
> Subject: RE: OT: service-based render can't see mapped drives.
> 
> Alan has just pointed out to me that XP won't allow you to access a
> mapped drive from a service, no matter what and a bit of research shows
> this to be the case. Sodding Windows.
> 
> > -----Original Message-----
> > From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> > Behalf Of Kim Aldis
> > Sent: 04 December 2006 12:25
> > To: XSI(at)Softimage.COM
> > Subject: RE: OT: service-based render can't see mapped drives.
> >
> > Thanks Morten. Another reason to dislike drive mappings. Jeez, the
> > time you waste on things like this doesn't bear thinking about, does
> it.
> >
> >
> >
> >
> > > -----Original Message-----
> > > From: owner-xsi(at)Softimage.COM [mailto:owner-xsi(at)Softimage.COM] On
> > > Behalf Of Morten Bartholdy
> > > Sent: 04 December 2006 12:26
> > > To: XSI(at)Softimage.COM
> > > Subject: Re: OT: service-based render can't see mapped drives.
> > >
> > > Kim, I had this constantly on my machine at home on 5.11 and I
> > > simply had to wait 300 sec for it to go look for my textures - more
> > > than a bit annoying.
> > > Running on QFE10 now and it works fine. Alexandra O'Connor sent me
> a
> > > list of fixes in this QFE:
> > >
> > > QFE 10:
> > >
> > > UDEV00230178 Part 1: UNC paths vs. mapped drives (Recent Scenes)
> > >
> > > So try and give support a shout if you have this problem.
> > >
> > >
> > > MB
> > >
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: "Alan Jones" <skyphyr(at)gmail.com>
> > > To: <XSI(at)Softimage.COM>
> > > Sent: Monday, December 04, 2006 12:58 PM
> > > Subject: Re: OT: service-based render can't see mapped drives.
> > >
> > >
> > > > It's a feature. Seriously. As far as I'm aware there is no way to
> > > > change it either.
> > > >
> > > > On 12/4/06, Kim Aldis <XSI(at)kim-aldis.co.uk> wrote:
> > > >>
> > > >>
> > > >>
> > > >>
> > > >> I've an interesting situation here. My renderfarm uses a service
> > to
> > > run
> > > >> jobs
> > > >> submitted remotely.  I have machine 'A' with a drive attached to
> > > >> it, mounted as Q: and shared with share name Q. The rendering
> > > >> service runs on
> > > both A
> > > >> and
> > > >> B and logs in as user 'Adminstrator'. Permissions on A's Q: give
> > > everbody
> > > >> full control. Adminstrator on B has Q: mapped to \\A\Q. Logged
> in
> > > >> to
> > > B,
> > > >> Adminstrator can start XSI, load scenes from Q: and render quite
> > > happily.
> > > >> However, the service log output is telling me that the scene on
> Q:
> > > can't
> > > >> be
> > > >> read and that drive Q: will be marked unreadable for 300
> seconds.
> > > >> If
> > > I
> > > >> add a
> > > >> line in my rendering script that makes a system call to 'net
> use'
> > > that
> > > >> tries
> > > >> to map the share to Q:, I get a warning that : is already
> mapped.
> > > >> No other errors or warnings are logged and the event viewer
> shows
> > > >> no entries
> > > that
> > > >> could be relevant. I've checked the number of sessions on
> machine
> > A
> > > and
> > > >> it's
> > > >> well within limits.
> > > >>
> > > >>
> > > >>
> > > >> This is undoubtedly a windows problem but it's not one I've
> > > encountered
> > > >> before. As far as I can see this should be working. Does anyone
> > > >> have
> > > any
> > > >> thoughts as to why the service can't see this drive?
> > > >>
> > > >>
> > > >>
> > > >> Thanks.
> > > >>
> > > >>
> > > >>
> > > >> www.kim-aldis.co.uk   |   kim(at)kim-aldis.co.uk
> > > >>
> > > >>
> > > > ---
> > > > Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text
> > in
> > > body:
> > > > unsubscribe xsi
> > > >
> > > >
> > >
> > > ---
> > > Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text
> in
> > > body:
> > > unsubscribe xsi
> >
> > ---
> > Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
> > body:
> > unsubscribe xsi
> 
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
> body:
> unsubscribe xsi
> 
> ---
> Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in
> body:
> unsubscribe xsi


---
Unsubscribe? Mail Majordomo(at)Softimage.COM with the following text in body:
unsubscribe xsi


Search the XSI List archives here or use the advanced search form to search across mailing lists. Searching help is available.
This site supposedly brought to you by Benjamin Grosser and the Imaging Technology Group.