[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] GID process tracking
- Date: Sun, 2 Dec 2007 20:56:38 -0800
- From: Stuart Anderson <anderson@xxxxxxxxxxxxxxxx>
- Subject: Re: [Condor-users] GID process tracking
Fare enough. However, I am confused as to whether I have this working or not.
Here is an example of a condor spawned user process on an FC4 execute machine
running version 6.9.5:
[root@node1 condor]# grep -i gid /proc/19302/status
Gid: 4093 4093 4093 4093
[root@node1 condor]# grep -i gid ~condor/condor_config
## The user/group ID <uid>.<gid> of the "Condor" user.
USE_GID_PROCESS_TRACKING = True
MIN_TRACKING_GID = 900
MAX_TRACKING_GID = 903
I was expecting to see one of [900, 903] in /proc/pid/status. Is there
somewhere else I should look?
On Fri, Nov 30, 2007 at 09:08:41AM -0600, Greg Quinn wrote:
> The current behavior is for the initial N active slots to use up the GID
> space, as expected. Any jobs that later fail to get allocated a GID
> because none are available will actually fail. This behavior was chosen
> because (a) it's a misconfiguration and should be reconciled anyways,
> and (b) presumably if you want to use GID-based tracking you're serious
> about making sure Condor tracks your jobs' processes properly.
> Greg Quinn
> Condor Team
> On Thu, 2007-11-29 at 21:15 -0800, Stuart Anderson wrote:
> > With the new GID process tracking,
> > http://www.cs.wisc.edu/condor/manual/v6.9.5/3_12Setting_Up.html#sec:GroupTracking
> > if I later on increase the number of slots but forget to increase the GID
> > tracking range is the specified GID address space first consumed by active
> > slots, leaving additional new slots to fall back to the previous pid tracking
> > algorithm(s)?
> > Thanks.
> Condor-users mailing list
> To unsubscribe, send a message to condor-users-request@xxxxxxxxxxx with a
> subject: Unsubscribe
> You can also unsubscribe by visiting
> The archives can be found at:
Stuart Anderson anderson@xxxxxxxxxxxxxxxx