[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [HTCondor-users] startd doesn't start
It's not too bad a challenge - if you have RPM, you can just shut down the service, then rpm --setuigids on all the condor* packages, and then chown -R condor:condor /var/log/condor /var/lib/condor/spool to cover the files created after the service started.
If you changed SPOOL, EXECUTE, or LOG, you'd need to manually update what the RPM doesn't hit.
> -----Original Message-----
> From: HTCondor-users [mailto:htcondor-users-bounces@xxxxxxxxxxx] On
> Behalf Of Dimitri Maziuk
> Sent: Monday, March 20, 2017 3:50 PM
> To: htcondor-users@xxxxxxxxxxx
> Subject: Re: [HTCondor-users] startd doesn't start
> On 03/20/2017 02:28 PM, Michael Pelletier wrote:
> > For what it's worth, CentOS / Red Hat has assigned uid/gid 64 to the
> "condor" user and group in /usr/share/doc/setup*/uidgid.
> I recently did another condor install and noticed that, but like Alessandra
> wasn't sure if that was just a coincidence. At BMRB our condor UID/GIDs will
> soon be old enough to drink... some day when I feel like I need a challenge I
> might run a find/chown on the entire pool. ;)
> Good to know about LDAP.
> Dimitri Maziuk
> BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu