Yep I tried those two options, and nothing... Even if the pre-user conf files have a log file in the same directory, which I touch before trying, messages keep going to syslog... I tried with 666 permissions on rsyncd.log too just to make sure... The following is one of the user's conf file, hope theres a clue. Thanks! log file = /home/pluto/rsyncd.log <<< This is the problem!! this rsync.conf is in the same dir. log format = [From: %a] [To: %m] %o %f %u [Size: %b] use chroot = false transfer logging = true [module1] path = modules/module1 hosts allow = 192.168.99.45 read only = false uid = pluto gid = users incoming chmod = g-rwx,o-rwx auth users = pluto secrets file = svsec strict modes = true list = false [syncvlt] path = modules/syncvlt #hosts allow read only = true uid = pluto gid = users list = false> I bet your per-user rsyncd.conf files specify /var/log/rsyncd.conf but > the individual users don't have permission to write to this log file. > Thus the individual rsyncs get EACCES and fall back to syslog. To fix > this, you can either grant everyone permission to write > to /var/log/rsyncd.log (might not be a good idea because one user could > maliciously alter the other user's log messages) or create per-user log > files and specify their locations in the per-user rsyncd.confs. > > -- > Matt McCutchen > hashproduct@verizon.net > http://hashproduct.metaesthetics.net/ > >-------------- next part -------------- HTML attachment scrubbed and removed
On Fri, 2006-03-31 at 18:50 +0200, Julian Pace Ross wrote:> Yep I tried those two options, and nothing... > Even if the pre-user conf files have a log file in the same directory, > which I touch before trying, messages keep going to syslog... I tried > with 666 permissions on rsyncd.log too just to make sure...I can reproduce this bad behavior! I have the following rsyncd.conf in my home directory: log file = /home/matt/rsync/test-daemon/rsyncd.log log format = [From: %a] [To: %m] %o %f %u [Size: %b] use chroot = false transfer logging = true [module1] path = modules/module1 hosts allow = 127.0.0.1 read only = false uid = matt gid = matt incoming chmod = g-rwx,o-rwx list = false And I have modules/module1 with a test file in it. The following happens: [matt@mattlaptop ~]$ rsync -vv -e ssh rsync://localhost/module1/ opening connection using ssh localhost rsync --server --daemon . opening connection using --server --sender -vv --list-only . module1/ drwx------ 72 2006/03/31 12:08:32 . -rw------- 0 2006/03/31 12:08:32 testfile delta-transmission enabled sent 82 bytes received 78 bytes 106.67 bytes/sec total size is 0 speedup is 0.00 And I get nothing in rsyncd.log but the following in syslog: Mar 31 12:20:44 mattlaptop rsyncd[9157]: connect from mattlaptop (127.0.0.1) Mar 31 12:20:44 mattlaptop rsyncd[9157]: rsync allowed access on module module1 from mattlaptop (127.0.0.1) Mar 31 12:20:44 mattlaptop rsyncd[9157]: rsync on module1/ from mattlaptop (127.0.0.1) Mar 31 12:20:44 mattlaptop rsyncd[9157]: sent 78 bytes received 82 bytes total size 0 -- Matt McCutchen hashproduct@verizon.net http://hashproduct.metaesthetics.net/
Possibly Parallel Threads
- [LLVMdev] Linking modules across contexts crashes
- is "unintended library loading" actually possible?
- rsync server complaining about vanishing files while they are not.
- The rsync daemon as a gateway service?
- [LLVMdev] inline callsites whose function definitions are in different file?