rsync - Jan 2004 - chroot and pwd.db file not found ...

This has been asked before, but my question is somewhat different.

On FreeBSD, the message:
rsyncd[520]: /etc/pwd.db: No such file or directory

is obviously caused by a chrooted rsyncd being unable to access /etc/pwd.db to
get at the password database to convert UIDs to names and back.

Workorounds of putting /etc/pwd.db in the chrooted directory have been offered,
and that's one solution.

However, my questions are these:
1) Does it hurt anything for rsyncd to not be able to resolve uids?  It
doesn't
    seem to affect the function of the system.
2) If it's not hurting anything, is there a way to stop these messages?

Thanks in advance for any suggestions.

-- 
Bill Moran
Potential Technologies
http://www.potentialtech.com

On Thu, Jan 08, 2004 at 01:11:43PM -0500, Bill Moran
wrote:
> This has been asked before, but my question is somewhat different.
> 
> On FreeBSD, the message:
> rsyncd[520]: /etc/pwd.db: No such file or directory
> 
> is obviously caused by a chrooted rsyncd being unable to access /etc/pwd.db
> to
> get at the password database to convert UIDs to names and back.
> 
> Workorounds of putting /etc/pwd.db in the chrooted directory have been 
> offered,
> and that's one solution.
> 
> However, my questions are these:
> 1) Does it hurt anything for rsyncd to not be able to resolve uids?  It 
> doesn't
>    seem to affect the function of the system.
> 2) If it's not hurting anything, is there a way to stop these messages?
> 
> Thanks in advance for any suggestions.
The messages are being generated by the library, not rsync.

I'd start by trying the --numeric-ids option.


-- 
________________________________________________________________
	J.W. Schultz            Pegasystems Technologies
	email address:		jw@pegasys.ws

		Remember Cernan and Schmitt