[Pulp-list] Does pulp tools have to be run as root?
jortel at redhat.com
Mon Jun 28 14:53:01 UTC 2010
On 06/28/2010 09:31 AM, Jason Dobies wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> Right now I have to run pulp tools as root because the log file writes
> to /var/log/pulp/pulptools.log, which only root has permission to.
> - - Is there another reason we'd *have* to run as root outside of this? If
> not, I'd like to find a workaround so I can run as any user. Seems like
> logging shouldn't be a reason to force us into running as root.
The user must be root because many of the CLI commands write to root protected (owned)
files and directories such as /etc/pulp/consumer and /etc/yum.repos.d/pulp.repo.
> - - This is causing a problem with the repo sync schedule implementation,
> which uses pulp tools to do the sync. It's crashing because the apache
> user can't write to the log file.
Repo sync is a server side thing. Wonder why this functionality is in pulptools. Can
this be moved?
> Assuming we can fix the first point, the second becomes a non-issue. I'm
> not sure of the cleanest solution (in nimbus tools, I write the log to
> /tmp if the user doesn't have access to /var/log), but someone else
> might have a more standard approach.
Interesting solution. I'm not opposed but seems odd that admins would have to look in two
places for the log when trying to debug.
> - --
> Jason Dobies
> RHCE# 805008743336126
> Freenode: jdob
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.14 (GNU/Linux)
> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/
> -----END PGP SIGNATURE-----
> Pulp-list mailing list
> Pulp-list at redhat.com
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 5126 bytes
Desc: S/MIME Cryptographic Signature
More information about the Pulp-list