search for: mygid

...d_header = yes smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache smtpd_tls_session_cache_timeout = 3600s smtpd_use_tls = yes strict_rfc821_envelopes = yes tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 virtual_gid_maps = proxy:mysql:/etc/postfix/mygid.cf virtual_mailbox_base = / virtual_mailbox_maps = proxy:mysql:/etc/postfix/myvirtual.cf virtual_minimum_uid = 1000 virtual_transport = dovecot virtual_uid_maps = static:33 # POSTFIX master.cnf # # Postfix master process configuration file. For details on the format # of the file, see the master...

...ose set of statistics on the file transfer RSYNC_FLAGS="$RSYNC_FLAGS --human-readable -h" # output numbers in a human-readable format I have an rsyncd (root:root) with the following setup: comment = data area for rsync path = something log file = /var/log/rsyncd.log uid=root gid=mygid read only=false write only=false use chroot=true rsync works as expected (at least does what I expect). when I comment out uid=root in rsyncd.conf the owner will not be transferred any more, it will remain nobody. The precedence of --perms on the client side (including -o, -g) and the uid= guid=...