[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] Request: Run hook scripts in the context of the user who will execute the job on Windows
- Date: Thu, 3 Sep 2009 13:50:31 -0400
- From: Ian Chesal <ICHESAL@xxxxxxxxxx>
- Subject: Re: [Condor-users] Request: Run hook scripts in the context of the user who will execute the job on Windows
> > >> Another idea: if you are using a "Professional" version of
> > >> Windows, aka
> > >> XP Professional and _not_ XP Home etc, and you are using
> > >> dedicated job
> > >> run accounts with Condor, perhaps you could use the "runas
> > /savecred"
> > >> option and then do a runas from inside your hook.
> > > We're toying with this now. It's been unreliable in the
> > past to stash
> > > credentials this way. It'll work for a period of time and
> then it'll
> > > start asking for the password again. We'll see how the
> > tests go with this one.
> > just use psexec instead :)
> > http://technet.microsoft.com/en-gb/sysinternals/bb897553.aspx
> Yes! That's the ticket. I forget about the PS-tools. Handy they are.
Todd, Matt -- an update. These solutions are a no-go. Psexec insists on
outputting stuff to stdout when you run it, which confuses Condor. I
tried rolling my own "ianexec" command but what I found was anything
output by the sub-process in another user space was invisible to the
calling process. So writing to stdout in the hook script being run as a
domain user isn't visible to Condor.
I'm faced with writing to a file, and having my calling script echo to
stdout. Or I can always return a job to Condor to and that job is my
hook script -- which screws up stats (machines always look busy) but
gets me hook scripts running as domain users.
So yea, a way to fire hooks as domain users would be nice.
This message may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient, you are hereby notified that any use, disclosure, dissemination, distribution, or copying of this message, or any attachments, is strictly prohibited. If you have received this message in error, please advise the sender by reply e-mail, and delete the message and any attachments. Thank you.