On mer, 2014-08-27 at 08:49 +0000, Zaman, Imran wrote: > Hei! > > gumd and pwdutils scripts are unreleated to each other. gumd does not use any > of those scripts. > login.defs is not used in gumd instead gumd has its own configuration file > /etc/gumd/gumd.conf.
the current Tizen's package is installing gumd.conf in /etc not /etc/gumd as you can see. # rpm -ql gumd /etc/dbus-1 /etc/dbus-1/system.d /etc/dbus-1/system.d/gumd-dbus.conf /etc/gumd.conf /usr/bin/gumd /usr/share/dbus-1/system-services /usr/share/dbus-1/system-services/org.tizen.SecurityAccounts.gUserManagement.service /usr/share/doc/packages/gumd /usr/share/doc/packages/gumd/AUTHORS /usr/share/doc/packages/gumd/COPYING.LIB /usr/share/doc/packages/gumd/INSTALL /usr/share/doc/packages/gumd/NEWS /usr/share/doc/packages/gumd/README /usr/share/gumd.manifest Is it an error? what other files may go in the directory /etc/gumd/? Best regards José > BR > imran > ________________________________________ > From: José Bollo [[email protected]] > Sent: 27 August 2014 10:30 > To: [email protected] > Cc: Zaman, Imran; [email protected]; Laako, Jussi > Subject: Re: [Dev] [Mulituser] user creation/removal notification > > On mar, 2014-08-26 at 18:00 +0200, Krzysztof Sasiak wrote: > > Hi, > > > > Thanks for the links and information! > > > > About the native notification API: I've asked around and it seems > > that dbus is good enough for us. > > > > One more question: Do You think it would be a good idea to include > > gumd in the standard ks file for images building? > > Hi all, > > It is planned to be included or is already included. > > But we are still having question about that. So I'm jumping into the > opportunity of this mail thread to ask it here. It would avoid browsing > sources if someone will help. > > First, is there a relationship between gumd and the usual scripts > provided by pwdutils: useradd/del/mod, groupadd/del/mod or are they > unrelated one to other? The case of the tuning scripts useradd.local, > userdel-post.local, userdel-pre.local, groupadd.local is also important. > Will gumd use it? And what about the configuration file /etc/login.defs, > is it used? > > Second (but linked to the previous), we might not have DBUS in during > MIC's image creation process (frankly, I should check that, so if > someone has the answer...). Thus relying on gumd features during image > creation is still hypothetical for me. It would imply that %pre and % > post sections of .spec files shouldn't rely on gumd 8( > > Feedbacks are very welcome > > Best regards > José > > > > > > Best regards, > > > > Krzysztof Sasiak > > > > On 26.08.2014 14:01, Zaman, Imran wrote: > > > > > Urls in my last email may not open as it may need login to gerrit but the > > > one below should not need login to gerrit... > > > > > > dbus notifications url: > > > https://review.tizen.org/git/?p=platform/upstream/gumd.git;a=blob;f=src/daemon/dbus/gumd-dbus-user-service-adapter.c;h=6cd37b9dcd94908349574b049fb386123c0f3d88;hb=refs/heads/upstream#l150 > > > > > > scripts commit url: > > > https://review.tizen.org/git/?p=platform/upstream/gumd.git;a=commit;h=9406e2c5eade7e8798771b5ecf1164a005bd5315 > > > > > > BR > > > imran > > > ________________________________________ > > > From: Dev [[email protected]] on behalf of Zaman, Imran > > > [[email protected]] > > > Sent: 26 August 2014 14:41 > > > To: [email protected]; José Bollo > > > Cc: [email protected]; Laako, Jussi > > > Subject: Re: [Dev] [Mulituser] user creation/removal notification > > > > > > Hi > > > > > > Jose is correct. DBus notifications for user add/remove already exists. > > > More precisely, dbus notification is at this place: > > > https://review.tizen.org/gerrit/gitweb?p=platform/upstream/gumd.git;a=blob;f=src/daemon/dbus/gumd-dbus-user-service-adapter.c;h=6cd37b9dcd94908349574b049fb386123c0f3d88;hb=refs/heads/upstream#l150 > > > > > > Krzysztof! one question from you: > > > - We can add user/group add/remove notifications in library libgum which > > > provides (GObject/C) interface to gumd dbus interface provided your > > > components (Buxton, Cynara) can link to the library directly and makes > > > your life easier. So would such solution can help you more or dbus > > > notifications are enough? > > > > > > Btw we have recently added support for adding scripts in gumd which will > > > be run: > > > a- after a user is added > > > b- before a user is about to be deleted > > > c- after a group is added > > > d- before a group is about to be deleted. > > > > > > So the (required) components can add their shell script under e.g. > > > /etc/gumd/useradd.d/ and /etc/gumd/userdel.d/ folders and it will be run > > > (in sorted order) > > > Here is the commit > > > https://review.tizen.org/gerrit/gitweb?p=platform/upstream/gumd.git;a=commit;h=9406e2c5eade7e8798771b5ecf1164a005bd5315 > > > > > > Please don't hesitate to ask if you have more questions. > > > > > > BR > > > imran > > > ________________________________________ > > > From: Dev [[email protected]] on behalf of Krzysztof Sasiak > > > [[email protected]] > > > Sent: 25 August 2014 17:57 > > > To: José Bollo > > > Cc: [email protected] > > > Subject: Re: [Dev] [Mulituser] user creation/removal notification > > > > > > Thank You for pointing this out. > > > > > > On 25.08.2014 15:58, José Bollo wrote: > > > > > > On lun, 2014-08-25 at 15:36 +0200, Krzysztof Sasiak wrote: > > > > > > > > > Hello, > > > > > > I'd like to propose a new feature for gumd - user added/removed > > > notifications. > > > > > > > > > > > > This functionnalities are already upstream in GUMD: see > > > src/daemon/gumd-daemon.c function gumd_daemon_class_init. > > > > > > > > > > > > After analysis of the architecture of the current service daemons > > > running on Tizen, a conclusion has been reached that it would be > > > beneficiary to have notifications whenever a user is added or removed. > > > As gumd already uses dbus for communication between service and > > > client, I propose to use it also for notification about the above > > > mentioned events. Clients could register signal handlers and then a > > > predefined callback function would be run. > > > > > > Example usecases: > > > 1. Buxton: Whenever a user is removed, all per user entries would also > > > be removed > > > 2. Cynara: User privilege entries are removed, as soon as user is > > > removed > > > > > > Correct me if I'm wrong - I've already checked gumd for this > > > feature, but didn't find anything. > > > > > > Please state Your opinion. > > > -- > > > > > > > > > Samsung_Logo_for_Mail_Signature > > > > > > > > > > > > Krzysztof Sasiak > > > > > > Samsung R&D Institute Poland > > > > > > Samsung Electronics > > > > > > [email protected]<mailto:[email protected]> > > > > > > > > > _______________________________________________ > > > Dev mailing list > > > [email protected]<mailto:[email protected]> > > > https://lists.tizen.org/listinfo/dev > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > [Samsung_Logo_for_Mail_Signature] > > > > > > Krzysztof Sasiak > > > Samsung R&D Institute Poland > > > Samsung Electronics > > > [email protected]<mailto:[email protected]> > > > --------------------------------------------------------------------- > > > Intel Finland Oy > > > Registered Address: PL 281, 00181 Helsinki > > > Business Identity Code: 0357606 - 4 > > > Domiciled in Helsinki > > > > > > This e-mail and any attachments may contain confidential material for > > > the sole use of the intended recipient(s). Any review or distribution > > > by others is strictly prohibited. If you are not the intended > > > recipient, please contact the sender and delete all copies. > > > --------------------------------------------------------------------- > > > Intel Finland Oy > > > Registered Address: PL 281, 00181 Helsinki > > > Business Identity Code: 0357606 - 4 > > > Domiciled in Helsinki > > > > > > This e-mail and any attachments may contain confidential material for > > > the sole use of the intended recipient(s). Any review or distribution > > > by others is strictly prohibited. If you are not the intended > > > recipient, please contact the sender and delete all copies. > > > > > > > > > > > --------------------------------------------------------------------- > Intel Finland Oy > Registered Address: PL 281, 00181 Helsinki > Business Identity Code: 0357606 - 4 > Domiciled in Helsinki > > This e-mail and any attachments may contain confidential material for > the sole use of the intended recipient(s). Any review or distribution > by others is strictly prohibited. If you are not the intended > recipient, please contact the sender and delete all copies. > _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
