Re: [gentoo-user] running mldonkey with umask 0002

[Holly Bostick]

Robert Persson schreef:
> I would like to run mldonkey with umask 0002.  However I cannot work
>  out how to do this.  The Gentoo version of /etc/init.d/mldonkey
> calls start-stop-daemon, but start-stop-daemon doesn't have a umask
> option.
>
>
> As mldonkey is the only program that runs as user p2p, I would be
> happy if I could get all programs launched by p2p to run with umask
> 0002, but I can't work out how to do that either.
>
> Can anyone help me with this?
>
> Many thanks Robert

Frankly, I avoided the entire 'user p2p' issue by editing
/etc/conf.d/mldonkey:

# owner of mlnet process (don't change, must be existing)
USER="me"

# home dir of owner (don't change, must be existing)
BASEDIR="/home/me"

Whoever wrote the 'don't change' note can bite me-- with the original
settings, I wound up with a new user's $HOME directory, solely to
contain ~/.mldonkey. This seriously cheesed me off, because I was simply
trying out the daemon after I had logged into a new WM, while in my past
login I had been trying out Sancho (which is pretty nice), and because I
didn't know so much about how it was organized, I had run mlnet
standalone. I therefore had files in progress in my own ~/.mldonkey folder.
These of course were not picked up by user p2p (unless I wanted to go
around symlinking, which I didn't, since I didn't even want some rogue
user $HOME directory in the first place).

But I'm not running the mldonkey service from another PC, so I
can do that. Of course, since I'm not running the server (or the
service) from another PC than the client, I don't actually (seeem to)
need the service running (on a permanent basis via rc-update) anyway.
But if I change my mind and decide to use it despite that, at least it
should now pick up my currently-running transfers and settings instead
of making a whole new clean setup. I was pretty annoyed by that (hence
the 'bite me').

I found that "(don't change, must be existing)" comment confusing and
alarming, especially since the user p2p was (naturally) *not* existing
before I ran the daemon the first time (I saw it being created in the
output), so 'must be existing' wasn't even true, and 'don't change'
contradicts 'must be existing' anyway (why must the user be existing if
you aren't changing the user to a different pre-existing user)?

I hope this helps, but I am by no means an mldonkey expert, so I could
be wrong, or wrong for your setup.

Holly
-- 
gentoo-user@g.o mailing list