Re: [PLUG] Two passwd files?

[Paul <paul@dpagin.net>]

That idea may work.  Either post-processing or pre-processing the passwd 
file.

I had a similar idea for the hosts file.  (Oh, I just realized how 
important it will be to modify the hosts file before distributing it!) 
I thought of getting a list of hosts from the hosts file, which 
requires removing comments and local host information, that the rsync 
script can use to automactically target its updates.  On the client 
side, local host information will need to be preseved.

I'm starting to wonder if going back to NIS would be easier.


Jeff Abrahamson wrote:

> On Wed, Apr 16, 2003 at 10:57:23PM -0400, Paul wrote:
>  
>
> >  [13 lines, 85 words, 706 characters]  Top characters: _tsinelo
> >
> > I want to use rsync and ssh to push the passwd file (and others) as an 
> > alternative to NIS.  The question is, is it possible to have a "local" 
> > passwd file as an extension to the pushed passwd file?  For example, to 
> > have a local root account which is only valid on a particular machine?
> >
> > The config that I will be using is a variation of the approach detailed 
> > at http://www.ussg.iu.edu/security/rsync.html
> >    
>
> You could post-process locally with sed to change the root line:
>
> On local host:
>
>    ssh $central:/etc/passwd /etc/passwd.template
>    sed < /etc/passwd.template > /etc/passwd.root script
>    mv /etc/passwd.root /etc/passwd
>
> Assuming your constitution can take all this moving about without
> excessive adrenaline or high blood pressure.  Needless to say, you
> want to make sure an error at one step of the chain can't leave you
> without a passwd file.
>
>  

_________________________________________________________________________
Philadelphia Linux Users Group        --       http://www.phillylinux.org
Announcements - http://lists.netisland.net/mailman/listinfo/plug-announce
General Discussion  --   http://lists.netisland.net/mailman/listinfo/plug