On Thu, Mar 7, 2013 at 6:07 PM, Gergely Nagy <[email protected]> wrote: > Kay Sievers <[email protected]> writes: > >> On Thu, Mar 7, 2013 at 5:38 PM, Gergely Nagy <[email protected]> wrote: >> >>> Apart from the case I outlined above, all other reasons I'd have boil >>> down to convenience. Similarly how the 'tty' group's ID is configurable, >>> the journal group being similarly configurable would make it much easier >>> downstream to adapt the journal to an existing environment. >> >> "tty" is also not configurable, only it's numeric number, which we do >> not need for the journal. >> >> So it is already very similar. :) > > No, because tty's gid (the only thing that is used, the tty group itself > is never referenced, AFAICS) is configurable, while the journal group > isn't. > > They *are* very similar in that the tty gid can vary between systems, > and the group to access logs can too, and I'd like to keep using the > existing group that I already have. (Which most often happens to be adm > on most of my systems, so the former hardcoded value did not affect > me. :P) > > Mind you, if the journal is changed to use a GID rather than a symbolic > name, and make the gid configurable - that would be perfectly good for > me too.
"tty" is used all over udev, so it cannot be made configurable like you say. Kay _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
