OK, I clicked Reply-All :-)
I think that daemons running under nobody:distcc creates working files on the slaves, so I'm not sure what your point is here. The other more complex daemons I mentioned create files as well.
- should not create file, else they should not run under nobody
- shouldn't care if someone else see/delete/overwrite its files because it runs also under nobody.
I think that squid/apache/distcc shouldn't run under nobody if they write files. But if they do, then the problem is not that distcc runs under nobody but that *squid/apache* runs under nobody.
That was the discussion point: don't create a distcc user when running rpm installation.How about creating a "distcc" user if one does not already exist?
While?
- It's hard to remove
- You don't know which package created/use a certain user
So if distcc.rpm don't create a user, we have the 3 possibilities I described.
-jec
_______________________________________________
distcc mailing list http://distcc.samba.org/
To unsubscribe/change options: http://lists.samba.org/cgi-bin/mailman/listinfo/distcc
