Le jeudi 27 novembre 2014 à 10:23 +0100, Patrick Ohly a écrit : > Hello! > > It hasn't become clear to me in the gumd and image creation discussions > whether .rpm postin/un scripts can still depend on useradd and userdel > to create users for system services (example: avahi daemon runs as user > "avahi") dynamically. > > If so, what are the right runtime dependencies (if any) to ensure that > the commands are really available? > > If not, then I guess we maintain a static configuration of such daemons > and never modify it during package install/uninstall? Again, avahi is a > good example, because that's what's currently done for the "avahi" user > (see > https://review.tizen.org/gerrit/#/admin/projects/platform/upstream/setup). >
Hi Patrick, That is a real problem. I advocated on this list to have gumd providing a legacy scripts: useradd.... We will switch to gumd very soon (see https://review.tizen.org/gerrit/#/c/30885/ ). IMHO, the preferred way of adding user is dynamic not static. Then there is a problem of tools and of guideline. The good old useradd/userdel ... is widely used currently in installation phase of spec files in %pre or in %post (at least 20 times in platform/...). When switching to gumd, we should either replace any of this invocation by the correct gum-utils call or provide a wrapping script inside gumd packaging that will emulate the legacy useradd (in further steps it could emit first a warning and second an error what would allow a slight transition). This clarification is needed for the creation of HOMEs of users. I would also like to know what will be the groups. I suggested in a recent mail to create one group per user (and also per service). Best regards José _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
