<p>Ditto on oracle. System accounts get handled by the local machine. <br>
That said, putting oracle accounts in ldap is a good thing for large environments.<br>
For distros like rhel, apache install creates local system accounts. Since all system accounts will, by default, have uid <500 , using ldap for all ordinary, non-system accounts is pretty straight forward.<br>
There is also a non standard patch that stores ssh pub keys in ldap for no password ssh access.</p>
<p><blockquote type="cite">On Mar 23, 2010 8:45 PM, "adam" <<a href="mailto:prozaconstilts@gmail.com">prozaconstilts@gmail.com</a>> wrote:<br><br><p><font color="#500050"><a href="mailto:brian@polibyte.com">brian@polibyte.com</a> wrote:<br>
> Hi,<br>> <br>> I'm curious how people administering services on linux in envir...</font></p>I keep systems accounts on local systems.<br>
<br>
Oracle (of course), likes to do it differently. I build an oracle user<br>
and group in ldap, but since I install oracle from their vanilla<br>
distributions, and not via a package system, that means I get to define<br>
the users and groups during installation that oracle will be assigned to<br>
use, and not have a package manager decide what to do.<br>
<br>
If, for some reason, you have a packaged oracle that you have to use,<br>
I'd then stick to local system accounts. It'll make patching and<br>
updating later a lot less painful.<br>
<font color="#888888"><br>
Adam<br>
</font><p><font color="#500050"><br>_______________________________________________<br>Ale mailing list<br><a href="mailto:Ale@ale.org">Ale@ale.org</a><br><a href="http://mail.ale.org/ma.">http://mail.ale.org/ma.</a>..</font></p>
</blockquote></p>