[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] write and execute from different computer in grid
- Date: Fri, 18 Mar 2016 16:39:07 +0100
- From: Labounek RenÃ <xlabou01@xxxxxxxxxxxxxxxxxx>
- Subject: Re: [HTCondor-users] write and execute from different computer in grid
thanks for advice and instructions. I will save them. Because Ben's
advice helped without doing it, I hope I wil not need to do it.
Cituji Michael V Pelletier <Michael.V.Pelletier@xxxxxxxxxxxx>:
From: RenÃ Labounek <xlabou01@xxxxxxxxxxxxxxxxxx>
Date: 03/17/2016 09:25 AM
I think I have found a problem. Based on chapter 2.5.3 in next URL, UIDs
and GIDs must agree between computers. and they are not. Even not for
the condor user. Can I manually rewrite uid and gid for condor user on
one computer without breaking the HTcondor installation?
Changing the condor uid/gid is not as hard as you might think.
You'll want to shut down the service first, of course. Next, update the
user and group ID numbers to your desired value.
And the RPM package handily gives you a list of files and directories
that need to be owned by the condor user and group. For 8.2:
rpm -qlv condor | grep '[0-9] condor'
(That'll need to include all the other packages in the 8.4 release,
such as condor-procd, )
You've got /var/lib/condor and its subdirectories, /var/lock/condor,
/var/log/condor, and /var/run/condor in 8.2. Then you just do
a chown -R condor:condor on those directories, which will use the
new UID and GID values you updated in /etc/passwd and /etc/group,
and then restart the service.
You might also have a /tmp/hsperfdata_condor directory, depending
on your system, but you can just remove it rather than chowning it.
If you want to be really sure, you can use find on your local
filesystems on a given machine:
find / -fstype ext4 -uid <olduid> -print
If you find anything outside of the RPM's purview, add it to the
chown list or remove it. Since it's a privilege separation account,
though, you really shouldn't find anything outside the RPM's
And then you just fire up the service again, and away you go.