| Ah, shoot, another thing that would be useful:
- What OS? What version? - Do you use automount on the system?
I wouldn't expect the contents of the bind-mount to be visible to the HTCondor daemons unless you are hitting another bug.
Brian Hi Michael,
Can you give a few more of the lines around the one you reference?
In particular, I'm curious about which part of the job lifetime this is triggered on.
Brian Hi,
is it possible to use condor to run jobs that require root permissions to run (completely). I have the case where I need a special user to run some adminstrative functionality that requires root permissions on exec hosts. The jobs execute these pieces via sudo. The machines are configured to accept a specific set of sudo command's from that users. In general this works fine. However sometimes such jobs get suspend -- and I don't know why.
In such cases the startlog would say something like this
03/18/13 16:38:08 Directory::setOwnerPriv(): NOT changing priv state to owner of /var/lib/condor/execute/dir_29073/buildbase/29106/proc/2568/task/2580/fdinfo" (0.0), that's root!
which refers to a bind-mount /proc inside a chroot.
Is there a way to make this work reliably?
Thanks,
Michael
--
HTCondor-users mailing list
To unsubscribe, send a message to htcondor-users-request@xxxxxxxxxxx with a
subject: Unsubscribe
You can also unsubscribe by visiting
https://lists.cs.wisc.edu/mailman/listinfo/htcondor-users
The archives can be found at:
https://lists.cs.wisc.edu/archive/htcondor-users/
|
![[Computer Systems Lab]](http://www.cs.wisc.edu/pics/csl_logo.gif){kind=logo}