Hello fellow Puppeteers and thanks in advance for any assistance you may be able to offer.
We have a rather non-standard requirement on our Puppet-managed Linux systems, and I'm trying to figure out if/how Puppet can satisfy it. We use some of our servers to run Oracle database software. If you are familiar with Oracle DBs and Grid Infrastructure, then you know that if the user and/or groups are unknown when a server boots that the Oracle stack will not start properly. As such, even though we use WINBIND to join our servers to our M$ Active Directory domain, we want to have the oracle user be local...kind of...so that it's known at boot time even if there is an issue with the AD/WINBIND connection. The solution up to now was to use the same UID as generated by WINBIND to add an entry to /etc/passwd. However, we don't want the encrypted stored password to exist on every server, so we instead leave out the entry for /etc/shadow, and WINBIND is smart enough to authenticate the user to AD for us (and at boot time, the local presence of the oracle entry in /etc/passwd is sufficient to allow the oracle stack to start properly). With that in mind, is there any way to get an "oracle" entry added to /etc/passwd, create HOME directory and profiles, etc. without also ending up with an /etc/shadow entry? Thanks again, Bill -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/01db3245-9b87-460d-b301-e60ce91ee82d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
