On Fri, 2006-06-16 at 08:42 -0500, Grant Goodyear wrote: > Mike Kelly wrote: [Thu Jun 15 2006, 08:36:25PM CDT] > > As part of my original plans for my GLEP27 implementation, I was > > going to have my scripts automatically add the users requested by a > > package (for example, the cron user), to all the passwd backends > > listsed in /etc/nsswitch.conf. However, in consultation with some > > folks, it seems that what may be more desirable is to just add > > users/groups to the local files/compat backends instead, and not make > > any changes to the remote databases. > > > > Does anyone have any strong notion of any cases where it would be > > excessively bad for the package manager to try adding to, say, the > > nss_nis backend in addition to the nss_files backend, or cases where > > that would be a strongly desired behavior? > > I think it's unlikely that one would want to add an account to both > files and nis/ldap, but there's no good reason that I can think of not > to let the user choose. That said, I'm not exactly an uber-sysadmin. > One thing that I might think would be common, though, would be to have > system accounts pre-defined in ldap/nis, with the expectation that your > scripts would look up the remote values and then create local accounts > with those values. Anybody who actually has a clue want to chime in?
Most things *should* not to *anything* if the account exists in mysql/ldap/nis/etc as the account is already present. It's just the case of it *not* existing that causes the real problem. > > Oh, it might be a good idea to ask in [EMAIL PROTECTED], too. > > -g2boojum- -- Chris Gianelloni Release Engineering - Strategic Lead x86 Architecture Team Games - Developer Gentoo Linux
signature.asc
Description: This is a digitally signed message part
