[Bug 221906] Review Request: gmediaserver - UPnP compatible media server for the GNU system

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug report.

Summary: Review Request: gmediaserver - UPnP compatible media server for the GNU system
Alias: gmediaserver

https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=221906





------- Additional Comments From bjohnson at symetrix.com  2007-04-06 17:29 EST -------
(In reply to comment #15)
> In the absence of option 3 (static UID/GID), I think option 2 (not removing the
> user/group) is much better. It may be "messy" in terms of leaving accounts on
> systems but IMHO this is not as "messy" as leaving unowned files on those
> systems (which would happen if the user/group were deleted).

> There is actually a pseudo-static UID/GID mechanism available in Fedora
> (http://fedoraproject.org/wiki/PackageUserCreation) but use of it is contentious

I agree with Paul here.  This is messy, but ATM there is not a good way to
handle this except with fedora-usermgmt as noted above.  However, I would not
recommend fedora-usermgmt (although I use it on my packages) until the
controversy regarding it's use is ironed out.

So for now, let's go with the persistent user/group.

(In reply to comment #14)
> Well...IMO there are some ways resolve this problem:
> 1. Do not change it, the owner of /srv/gmediaserver will be changing all time
> when the package user will be having other uid/gid and the files are often 644,
> so the program can read it. I think it is safe, because if the directory will
> not be deleted unless it is empty.

But there will be potentially unowned files depending on how the media server is
used.  You're lucky in the regard that the media server doesn't actually have to
manage the files, only read them - otherwise it would be more sticky.


-- 
Configure bugmail: https://bugzilla.redhat.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.