Dominig, I agree with you , but if the db is created at the first time then we need to store local db into /home/*** directories not elsewhere. Indeed, adding user is one thing, delete user account is an other one.
Store them into /home/*** directories permits to manage user account removal. Baptiste 2014/1/10 Dominig ar Foll (Intel OTC) <[email protected]> > > > If you’re going to have multiple user accounts you are going to need a > mechanism for creating new user accounts, possibly a derivative of either > adduser or useradd. This mechanism (useradduser? J) could create these > databases and files just as it would have to create other user profile > information. > > I see a few issues in that proposition : > > - adduser run with privilege, it"s simpler to let the App create it's own > user DB at the first run (generic model for most Linux App) if those do not > exist. Access Right will then setup correctly be default. > - time to add a user will get longer and longer when App are added on the > system even if the new user do not need these App. Feedback in progress is > not easy to provide > - if a one App init script fails, it not simple/reliable to recover and > process other App init script > - if the user DB is lost or currupted for any raison, you need to > reinstall the App to trigger the yser DB creation. > - adduser feature quality become depend of App init script quality on > which we have no control. > > For all these issues, I strongly think that we should let the App create > it's own DB on first run and not push that service in the adduser facility. > > Dominig > > _______________________________________________ > Dev mailing list > [email protected] > https://lists.tizen.org/listinfo/dev > > -- Baptiste DURAND Eurogiciel Vannes/FR
_______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
