similar to: chroot and pwd.db file not found ...

I have rsync-2.5.5 humming along on FreeBSD 4.7-STABLE with no apparent problems. However, I notice when some clients connect to sync, I get this in /var/log/messages rsyncd[42843]: /etc/pwd.db: No such file or directory rsync is running as root with this basic rsync.conf: use chroot = yes read only = yes timeout = 600 Well of course /etc/pwd.db exists and could be readable, but more

Almost forgot - diff need ot be appied only on FreeBSD 5 version of 550.ipfwlimit, but resulting file can be used on both 4 and 5 releases. On Wed, Feb 23, 2005 at 03:59:51PM +0100, Alexander Leidinger wrote: Better version then previos, it will not break order of rules. awk version, it will work on all 4 and 5 releases, at least those, where IPFW enabled ;-) Also i removed check for

the protocols in. Trying to stifle the Small Businesses from using Home Edition on their networks trying reduce their costs I bet. Personally I figure Smart Co's are going to say bite me and move to Linux. Using http://www.ximian.org software my users can do whatever their WinDoze counterparts can with Word Excel printing and it just keeps getting simpler to install and use Linux for the end

Are there any other wireless IP phones out there other then the Cisco 7920?? -- James Moran <jmoran@potentialtech.com> Potential Technologies

I'm finding this a little strange. I'm putting together a mail server that will (someday, hopefully) serve a lot of email addresses for a lot of domains. To make life easy, each account name is the full mail name ... i.e "joe at domain.com" instead of just "joe" Mail is stored in Maildirs, and the user account information is all in MySQL. Delivery is handled by

Subject says it all. (I'm almost positive this is a FAQ, or that the information is online _somewhere_, but I just spent 20 minutes without finding it ... sorry if I didn't search hard enough) -- Bill Moran Potential Technologies http://www.potentialtech.com

http://us3.samba.org I get nothing but empty HTML pages when I try to access this particular mirror. Is something wrong with the mirror or is it something on my end? Anyone else who sees blank pages? Other mirrors seem to be working fine. -- Bill Moran Potential Technology http://www.potentialtech.com

Is anyone signed up with Vonage and using an asterisks box?? Also what VOIP providers would anyone recommend? -- James Moran Potential Technologies http://www.potentialtech.com

I'm looking for suggestions and pros/cons on how to implement this. We've got a WAN setup with 3 Samba servers, each on it's own leg of the WAN. The 3 sites are connected by a wireless link that is only capable of about 200k/sec. Currently we have 3 samba servers, each the PDC of it's own domain. The security is distributed via NIS so that all 3 servers have the same passwd/group

Hi, I am not sure it this still is a point, but I just discovered that a chrooted rsync version 2.6.3pre1 is forgetting the time zone underways: Jan 12 07:00:01 ftp4 rsyncd[11091]: rsync on dobes/ from dobes@edoc1.gwdg.de (134.76.28.251) Jan 12 06:00:39 ftp4 rsyncd[11091]: wrote 732542 bytes read 182 bytes total size 553909487945 Logging is done with syslog. Time zone is GMT+1, the system

I'm getting a Got SIP response "400 Bad request" from 172.16.0.105 (which is a Zyxtel 2000w). It also will not register. Any suggestions?? -- James Moran <jmoran@potentialtech.com> Potential Technologies

It took me a little while to figure out what was going on here ... We're trying to migrate a site from non-encrypted to encrypted passwords using the "update encrypted" option. Apparently, this causes problems when "username level" is set greater than zero (it's set to 15 in our implementation) We've been having a lot of problems when we turn on encrypted

Hi all, Tripped over a documentation bug. I'm guessing the behavior I've found isn't a bug in itself as it's kind of implied by chroot (unless the /etc/passwd db is read *before* you do the chroot call), so I'm calling it a documentation bug. The Setup: System A: running rsync --daemon from xinetd, configured with a read-only share. System B: syncing a local directory

Hello, Anyone out there running a production network supporting PC and Macintosh clients using samba and netatalk. we are currently using NT 4.0 with AppleTalk-IP software. Sharing the same files with the Macs and the pc is a must. I read someplace that samba 2.2.2 supports Appletalk. Is this true? Thanks, Joe

550.ipfwlimit check in /etc/periodic/security takes into account only global/default verbosity limit and does not account for a specific logging limit set for a particular rule e.g.: $ ipfw -a l | fgrep log 65000 *521* 41764 deny log logamount *1000* ip from any to any $ sysctl -n net.inet.ip.fw.verbose_limit *100* >From security run output: ipfw log limit reached: 65000 519

https://bugzilla.samba.org/show_bug.cgi?id=11013 Bug ID: 11013 Summary: [patch] Mention that privileges are dropped, when "use chroot" is enabled in rsyncd.conf manpage Product: rsync Version: 3.1.1 Hardware: All OS: All Status: NEW Severity: trivial Priority: P5

https://bugzilla.samba.org/show_bug.cgi?id=12817 Bug ID: 12817 Summary: [PATCH] Allow daemon itself to chroot Product: rsync Version: 3.1.2 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: core Assignee: wayned at samba.org Reporter:

Hello, I am trying to run rsync under my own userid on a high-numbered port. The problem is that, when I use the --daemon option, I get an error saying that a chroot() call failed. My config file does *not* have any chroot call in it. How can I avoid a chroot() invocation when running as a normal non-root user? Thanks in advance for any advice! -- Daniel Ortmann, LSI Logic, 3425 40th Av NW,

Why would I be getting this on a box? I have the same permissions on many other directories. Using verbose mode shows nothing more then the error in the Subject line. Any help is appreciated. -- Jason G Helfman Network Administrator BizRate.com 310.754.1264 desk

https://bugzilla.samba.org/show_bug.cgi?id=8198 Summary: rsync does not set TZ variable after chroot(), which confuses logging timestamps Product: rsync Version: 3.1.0 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P5 Component: core AssignedTo: wayned at