Paul Slootman via rsync wrote:
> On Sun 02 Jun 2024, Chris Green via rsync wrote:
>
> > I have an rsync daemon running on a 64-bit (x86_64) system which I
> > successfully use for backups from several other 64-bit systems on my
> > LAN.
> >
> > I want to
On Sun 02 Jun 2024, Chris Green via rsync wrote:
> I have an rsync daemon running on a 64-bit (x86_64) system which I
> successfully use for backups from several other 64-bit systems on my
> LAN.
>
> I want to use it for backups from a BeagleBone Black (32-bit, armv7l)
> but i
I have an rsync daemon running on a 64-bit (x86_64) system which I
successfully use for backups from several other 64-bit systems on my
LAN.
I want to use it for backups from a BeagleBone Black (32-bit, armv7l)
but it fails as follows:-
root@bbb:~# rsync -a /etc chris@backup::bbb
On Sun, Sep 18, 2022 at 6:13 AM Paul Slootman wrote:
> IMHO rsync is correct in refusing to run with a missing rsyncd.conf.
>
Yeah, it's one of the ways that some installs prevent a superfluous daemon
from starting up -- if it's not configured, you don't want it.
..wayne..
--
Please use reply-a
On Sat 17 Sep 2022, Colton Lewis via rsync wrote:
> This is on a system where /etc/rsyncd.conf does not exist and goes away if
> /etc/rsyncd.conf is an empty file.
>
> Version: rsync version 3.2.5 protocol version 31
> Command: rsync --daemon
> What happens: The program
This is on a system where /etc/rsyncd.conf does not exist and goes away if
/etc/rsyncd.conf is an empty file.
Version: rsync version 3.2.5 protocol version 31
Command: rsync --daemon
What happens: The program outputs "Failed to parse config file:
/etc/rsyncd.conf"
What I expect: T
I wonder why there is no delay after a failed authentification attempt
(daemon mode).
Should be easy to write a brute-force attack script using RSYNC_PASSWORD...
Wouldn't a delay make attacks much more difficult ?
Regards,
Frank Schaefer
--
Please use reply-all for most replies to avoid omittin
https://bugzilla.samba.org/show_bug.cgi?id=12430
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On Sat, Jun 27, 2020 at 7:17 AM Chandrasekar Natarajan wrote:
> Kindly help me to resolve this.
>
One thing you can do is to change the initial command from "rsync" to
"/usr/bin/rsync" (if that is where the real command is installed in your
setup) in order to try to avoid any script & shell alias
Hi Wayne,
Thanks for your reply.
This is the command I am using now(a simple command) *rsync -vrcz --port
u...@x.x.x.xx::Module1 '/cygdrive/d/test 123/'*
This is the exception 'Unexpected remote arg: User@x.x.x.x::Module1
rsync error: syntax or usage error (code 1) at main.c(1361) [sender=3.
On Thu, Jun 25, 2020 at 3:02 PM Chandrasekar Natarajan wrote:
> Unexpected remote arg: user@x.x.x.x:port/module
>
This means that your non-option args starts with a local arg, contains a
remote arg somewhere in the middle, and ends with either a local or remote
arg. None of those are valid becau
Hi,
Even I tried the same syntax but failed. But push is working fine. rsync:
Unexpected remote arg: user@x.x.x.x::module.
> On 26-Jun-2020, at 5:22 AM, Kevin Korb wrote:
>
> user@x.x.x.x:port/ModuleName is not correct syntax. You may have
> something in your shell config translating that
user@x.x.x.x:port/ModuleName is not correct syntax. You may have
something in your shell config translating that for you. Correct syntax
is --port and user@host::module
On 6/25/20 6:01 PM, Chandrasekar Natarajan via rsync wrote:
> Hi,
>
> I am trying to pull folders from a windows remote m
Hi,
I am trying to pull folders from a windows remote machine using daemon
without SSH.
Below is the command that used:
rsync -vrtz --delete user@x.x.x.x:port/ModuleName '/cygdrive/d/backup/'
No issue running the same command in Command Prompt.While executing this
command via c#.net Process star
https://bugzilla.samba.org/show_bug.cgi?id=12430
Bug ID: 12430
Summary: rsync daemon chooses wrong place for pathes containing
space and the module name
Product: rsync
Version: 3.1.1
Hardware: All
OS: Linux
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You can do that with rsync over ssh but not rsyncd.
On 09/21/2015 10:57 AM, Simon Wong (Staff) wrote:
> Dear all,
>
> Can someone let me know if it is possible to setup an Rsync server
> with domain authenticated users e.g. Active Directory users rat
Dear all,
Can someone let me know if it is possible to setup an Rsync server with domain
authenticated users e.g. Active Directory users rather than having
username:passwords in plain text?
Thanks,
Simon
The University of Dundee is a registered Scottish Charity, No: SC015096
--
Please use r
https://bugzilla.samba.org/show_bug.cgi?id=10668
--- Comment #4 from Barry Sanford 2014-06-22 17:45:57 UTC
---
Ahhh!!! The fault, then, is in my own understanding, or lack thereof. I was
under the false assumption that the pre-exec ran only when files were being
copied. But now my understandi
https://bugzilla.samba.org/show_bug.cgi?id=10668
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=10668
--- Comment #2 from Barry Sanford 2014-06-22 14:46:51 UTC
---
Btw, the HardLink file is created by the pre-exec script as a symbolic link to
the previous day's backup folder. For example, if the current backup folder is
201406022, then the pre-ex
https://bugzilla.samba.org/show_bug.cgi?id=10668
--- Comment #1 from Barry Sanford 2014-06-22 14:38:18 UTC
---
I have a server on my LAN that's hosting an rsync daemon. When I backup to the
'Backups' module on this server I have a 'pre-exec' script that creates a
'
https://bugzilla.samba.org/show_bug.cgi?id=10668
Summary: Remote rsync daemon still showing deleted file
Product: rsync
Version: 3.1.1
Platform: x86
OS/Version: Mac OS X
Status: NEW
Severity: normal
Priority: P5
Kevin Korb (k...@sanitarium.net) wrote on 17 February 2014 21:13:
>OK, I just did a quickie test. When I 'ssh user@host rsync --daemon
>- --server .' an I don't have an rsyncd.conf file in my home dir I get
>no output like you do (an error message here would be nice).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
OK, I just did a quickie test. When I 'ssh user@host rsync --daemon
- --server .' an I don't have an rsyncd.conf file in my home dir I get
no output like you do (an error message here would be nice). If I do
have a proper rsyncd.
Kevin Korb (k...@sanitarium.net) wrote on 14 February 2014 12:51:
>Try running that ssh command line yourself and see what it says.
Doesn't say anything. But rsync is indeed run. I changed it to this
script:
#!/bin/bash
echo "run!"
echo "run!"
and
ural# rsync -avv -e "ssh -l root" ./orig/ ma
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Try running that ssh command line yourself and see what it says.
On 02/14/2014 06:34 AM, Carlos Carvalho wrote:
> Kevin Korb (k...@sanitarium.net) wrote on 13 February 2014 21:47:
>> modules are defined in an rsyncd.conf file. That file needs to
>> b
On 14.02.2014 13:17, Paul Slootman wrote:
> On Fri 14 Feb 2014, Matthias Schniedermeyer wrote:
> >
> > You mixed the options from "remote shell" with "rsync daemon".
> > Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode.
>
On Fri 14 Feb 2014, Matthias Schniedermeyer wrote:
>
> You mixed the options from "remote shell" with "rsync daemon".
> Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode.
Matthias,
Ik recommend you check out the "USING RSYNC-D
Matthias Schniedermeyer (m...@citd.de) wrote on 14 February 2014 13:06:
>You mixed the options from "remote shell" with "rsync daemon".
>Rsync is used either as 'rsync over SSH'(/remote shell) OR daemon-mode.
No, there's a third method. Search for
"
t see server greeting
> rsync error: error starting client-server protocol (code 5) at main.c(1635)
> [sender=3.1.1pre1]
>
> Am I doing something wrong?
You could say that.
You mixed the options from "remote shell" with "rsync daemon".
Rsync is used eith
Kevin Korb (k...@sanitarium.net) wrote on 13 February 2014 21:47:
>modules are defined in an rsyncd.conf file. That file needs to be in
>the home dir of the user.
You mean the config file must be called "rsyncd.conf" instead of "module"?
That'd be easy to solve but unfortunately it didn't work.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
modules are defined in an rsyncd.conf file. That file needs to be in
the home dir of the user.
On 02/13/2014 08:38 PM, Carlos Carvalho wrote:
> I'm trying to transfer something to another machine launching a
> once-only "daemon" through ssh with thi
I'm trying to transfer something to another machine launching a
once-only "daemon" through ssh with this command:
rsync -avv -e "ssh -l user" ./orig/ machine::module/
where "module" is the name of a file in the home dir of user with the
following:
path = /path/to/home/transfer
The ssh connecti
||FIXED
Summary|rsyncd resolves hosts |rsync daemon should do
|stupidly|forward lookups of allowed
||hostnames
--- Comment #1 from Wayne Davison 2013-10-27 17:20:53 UTC ---
[Are
https://bugzilla.samba.org/show_bug.cgi?id=8838
Wayne Davison changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=9660
Wayne Davison changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #2 from Wayne Davison
https://bugzilla.samba.org/show_bug.cgi?id=8838
Wayne Davison changed:
What|Removed |Added
Status|NEW |ASSIGNED
--- Comment #7 from Wayne Davison
https://bugzilla.samba.org/show_bug.cgi?id=8838
--- Comment #6 from Chris Dunlop 2013-05-13 07:00:07 UTC
---
Apologies, my previous comment was a bit misleading. I meant that I would also
have expected --protect-args to fix the problem you've identified, however, if
the intention is to not affec
https://bugzilla.samba.org/show_bug.cgi?id=8838
--- Comment #5 from mlus...@redhat.com 2013-05-10 09:50:58 UTC ---
Created attachment 8876
--> https://bugzilla.samba.org/attachment.cgi?id=8876
New version of patch preserving historical usage
Attached patch enables transmission of files into dir
https://bugzilla.samba.org/show_bug.cgi?id=8838
--- Comment #4 from Chris Dunlop 2013-05-06 03:54:58 UTC
---
(In reply to comment #3)
> Thank you Chris. I have not been aware about this rsync feature. I am getting
> the same result when I try to transmit mentioned file with --protect-args.
> Sho
https://bugzilla.samba.org/show_bug.cgi?id=8838
--- Comment #3 from mlus...@redhat.com 2013-05-03 14:01:08 UTC ---
Thank you Chris. I have not been aware about this rsync feature. I am getting
the same result when I try to transmit mentioned file with --protect-args.
Shouldn't this be working with
https://bugzilla.samba.org/show_bug.cgi?id=8838
--- Comment #2 from Chris Dunlop 2013-04-15 02:08:20 UTC
---
It looks like the proposed fix may break this usage (from the
'ADVANCED USAGE' section of the man page):
Older versions of rsync required using quoted spaces in the SRC, like
these e
https://bugzilla.samba.org/show_bug.cgi?id=8838
--- Comment #1 from mlus...@redhat.com 2013-04-12 15:40:18 UTC ---
Hi,
is there any problem with reproduction or inclusion into upstream?
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail b
https://bugzilla.samba.org/show_bug.cgi?id=9660
--- Comment #1 from m...@gmx.net 2013-03-29 10:28:30 UTC ---
It looks like the function is not implemented for the --deamon mode. Can
somebody confirm this?
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are re
https://bugzilla.samba.org/show_bug.cgi?id=9660
Summary: rsync --daemon --bwlimit does not work on server side
Product: rsync
Version: 3.0.9
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
https://bugzilla.samba.org/show_bug.cgi?id=8979
Wayne Davison changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|
https://bugzilla.samba.org/show_bug.cgi?id=8979
--- Comment #1 from Simon Klinkert 2012-06-14
06:47:45 UTC ---
After some more investigation with gdb it seems like something is wrong in
function flist_for_ndx().
check_prior() calls flist_for_ndx() with ndx=759. The problem is he returns
every t
https://bugzilla.samba.org/show_bug.cgi?id=8979
Summary: rsync daemon: High load while skipping hardlinks
Product: rsync
Version: 3.0.5
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P5
https://bugzilla.samba.org/show_bug.cgi?id=8838
Summary: rsync daemon chooses wrong destination place if space
and the module name is part of it
Product: rsync
Version: 3.1.0
Platform: All
OS/Version: Linux
Status
> On Tue, Nov 2, 2010 at 9:29 AM, Norbert van Bolhuis
> wrote:
>
>> Is there a way to make the rsync daemon use sync or whatsoever to make
>> sure
>> the rsync command returns only if all transferred data is written to
>> physical media[?]
>>
>
> Yo
On Tue, Nov 2, 2010 at 9:29 AM, Norbert van Bolhuis
wrote:
> Is there a way to make the rsync daemon use sync or whatsoever to make sure
> the rsync command returns only if all transferred data is written to
> physical media[?]
>
You can't delay the return, but you can ask th
Dear rsync-guru's,
here's a user question:
I want to make sure the files transferred to
rsync daemon (running on a linux kernel) are written to media
I assume if rsync command returns (with 0) all data has been
tranferred to rsync daemon, but it depends on the
rsync daemon priority
On 31-10-2010 18:41, edac...@gmail.com wrote:
On 10/31/2010 07:26 PM, Vahsen Beheer wrote:
On 31-10-2010 18:07, edac...@gmail.com wrote:
"-n" means "dry-run", no real action will be performed :).
Hope found one-line solution:
rsync -ndivv -f 'R /daily.20101030-0155/**' -f '-!r
/daily.20101030
On 31-10-2010 18:07, edac...@gmail.com wrote:
On 10/31/2010 06:52 PM, Vahsen Beheer wrote:
Hi again Edvinas, and thanks a lot!!!
I finally managed to delete a remote empty directory now! I
simplified my request a bit though, and need to delete a
subdirectory
On 10/31/2010 06:52 PM, Vahsen Beheer wrote:
> On 31-10-2010 17:23, Edvinas Valatka wrote:
>> Hi Vansen :) The 'p' in '-!pr' only needed, if directory
>> remote-host::Backups/daily.20101030-0155 is not empty.
>>
>> Workaround: rsync -d --del /tmp/empty-dir/
>> remote-host::Backups/daily.20101030
On 31-10-2010 17:23, Edvinas Valatka wrote:
Hi Vansen :)
The 'p' in '-!pr' only needed, if directory
remote-host::Backups/daily.20101030-0155 is not empty.
Workaround:
rsync -d --del /tmp/empty-dir/ remote-host::Backups/daily.20101030-0155/
rsync -ndv -f '-!r /daily.20101030-0155' --del /tmp/emp
On Sun, 31 Oct 2010 16:52:05 +0100
Vahsen Beheer wrote:
>
> On 31-10-2010 16:39, Edvinas Valatka wrote:On Sun, 31 Oct 2010
> 03:15:37 +0100 Vahsen Beheer wrote:
>
> Hi!
>
> I am backing up (using --link-dest, hard links) to a NAS which has
> an 'rsync'
On 31-10-2010 16:39, Edvinas Valatka wrote:
On Sun, 31 Oct 2010 03:15:37 +0100
Vahsen Beheer wrote:
Hi!
I am backing up (using --link-dest, hard links) to a NAS which has
an 'rsync' daemon running. I do not have ssh access to this
Stor
On Sun, 2010-10-31 at 17:39 +0200, Edvinas Valatka wrote:
> On Sun, 31 Oct 2010 03:15:37 +0100
> Vahsen Beheer wrote:
> > I am backing up (using --link-dest, hard links) to a NAS which has
> > an 'rsync' daemon running. I do not have ssh access to this
> > Stora
On Sun, 31 Oct 2010 03:15:37 +0100
Vahsen Beheer wrote:
> Hi!
>
> I am backing up (using --link-dest, hard links) to a NAS which has
> an 'rsync' daemon running. I do not have ssh access to this
> Storage-device. Part of my script needs to delete whole remote
>
On Sun, 31 Oct 2010 03:15:37 +0100
Vahsen Beheer wrote:
> Hi!
>
> I am backing up (using --link-dest, hard links) to a NAS which has
> an 'rsync' daemon running. I do not have ssh access to this
> Storage-device. Part of my script needs to delete whole remote
>
On Sun, 31 Oct 2010 03:15:37 +0100
Vahsen Beheer wrote:
> Hi!
>
> I am backing up (using --link-dest, hard links) to a NAS which has
> an 'rsync' daemon running. I do not have ssh access to this
> Storage-device. Part of my script needs to delete whole remote
>
Hi!
I am backing up (using --link-dest, hard links) to a NAS which has
an 'rsync' daemon running.
I do not have ssh access to this Storage-device. Part of my script
needs to delete whole remote
directory trees. This seems difficult with rsync.
Paul Slootman wrote:
> On Sat 06 Mar 2010, Wayne Davison wrote:
> > On Thu, Feb 25, 2010 at 5:20 PM, Tom Dickson wrote:
> >
> > > Is it possible to get a "pool" of waiting daemons, similar to how apache
> > > runs?
> >
> > No, there is no support for that in rsync at the moment. I don't think i
On Sat 06 Mar 2010, Wayne Davison wrote:
> On Thu, Feb 25, 2010 at 5:20 PM, Tom Dickson wrote:
>
> > Is it possible to get a "pool" of waiting daemons, similar to how apache
> > runs?
>
> No, there is no support for that in rsync at the moment. I don't think it
> would be simple to add, but if
On Thu, Feb 25, 2010 at 5:20 PM, Tom Dickson wrote:
> Is it possible to get a "pool" of waiting daemons, similar to how apache
> runs?
No, there is no support for that in rsync at the moment. I don't think it
would be simple to add, but if someone wants to work on patch, I'd consider
adding it
Hello,
We have multiple clients that are connecting to our rsync daemon, sending a
small file, and then disconnecting. This works well, but rsync forks each
time there is a connection.
Is it possible to get a "pool" of waiting daemons, similar to how apache
runs?
-tom
--
Please use
Hi,
I have followed https://help.ubuntu.com/community/rsync and
successfully configured it and works fine without any issue.
The question is how can i call the rsync client from the remote hosts
automatically to ping the rsync daemon and fetch only the new files
which is available on rsync
On Tue, Jun 9, 2009 at 12:41 AM, Daniel.Li wrote:
> b) Moniter CPU and mem usage during backup;
Yes, you are right. CPU% as given by ps aux seems always very low. Only a few %.
> I think you can test the system to find out what is the bottleneck.
Trying that now.
> I run a daemon on my Nasbox
On Mon, 2009-06-08 at 22:39 -0500, Rahul Nabar wrote:
> > If you're not using different partitions on different disks, then
> doing
> > anything in parallel is probably going to slow it down
> (reading/writing
> > all over the disk, means more seektime, which means waiting).
>
> No, its just a sin
On Mon, Jun 8, 2009 at 2:55 PM, Leen Besselink wrote:
> I think Daniel was trying to say, cpu might not be the bottleneck, it could
> be network or something else (I doubt it's memory rsync 3 pretty much solved
> that for most) and if you ask me it's probably disk.
Ah! I see. Thanks for the clarif
Rahul Nabar wrote:
> On Thu, Jun 4, 2009 at 12:09 AM, Daniel.Li wrote:
>
>> I think multi-client can improve performance, but limit is the same as
>> above.
>
> I don't think I understand! Can I start more than one "rsync --daemon"
> instances then?
On Thu, Jun 4, 2009 at 12:09 AM, Daniel.Li wrote:
> I think multi-client can improve performance, but limit is the same as
> above.
I don't think I understand! Can I start more than one "rsync --daemon"
instances then?
> What kind of performance you are concerning, n
On Wed, 2009-06-03 at 20:57 -0500, Rahul Nabar wrote:
> Is there a way to speed up rsync by opening more than one daemon in
> parallel.
daemon will create a process when a connection is established. So the
limit is hardware.
> I use rsync --daemon to start rsync. I was wondering if
Is there a way to speed up rsync by opening more than one daemon in
parallel. I use rsync --daemon to start rsync. I was wondering if
opening more than one instance is recommended or feasible? I know that
for services like nfs for example I have had opening many instances
improve performance.
I
n output information to console. But it seems no effect
> with "rsync --daemon".
>
> So, how can I output verbose information to console when running with
> command "rsync --daemon"
>
> I also tried log file. Seems didn't work.
>
> Or is there any o
Dear List,
option "-v" can output information to console. But it seems no effect
with "rsync --daemon".
So, how can I output verbose information to console when running with
command "rsync --daemon"
I also tried log file. Seems didn't work.
Or is there any
; > Currently the daemon runs root to get the 873 port opened.
> > > And when transfers then run, they run as nobody.
> > >
> > > I would like the rsync daemon to connect to 873 (as root)
> > > then possibly do a chroot and then run always as something else
>
of port 873. You should either
enable the xinetd service with chkconfig or start the daemon manually
with "rsync --daemon", but not both. If that isn't the problem, run
"netstat -a --inet --program" as root to see what process is listening
on the port.
Matt
--
P
On Fri, 2008-10-10 at 13:42 +0100, michael wrote:
> On Thu, 2008-10-09 at 17:08 -0700, Wayne Davison wrote:
> > On Thu, Oct 09, 2008 at 03:29:04PM +0100, michael wrote:
> > > and this is when I've tried both of
> > > a) /usr/bin/rsync --daemon -v
> &
On Thu, 2008-10-09 at 17:08 -0700, Wayne Davison wrote:
> On Thu, Oct 09, 2008 at 03:29:04PM +0100, michael wrote:
> > and this is when I've tried both of
> > a) /usr/bin/rsync --daemon -v
> > b) sudo /sbin/chkconfig rsync on
>
> Fedora supplies an /etc/xinetd.d
Wayne wrote:
> Fedora supplies an /etc/xinetd.d/rsync file that defaults to off. Using
> your b command should turn it on and sighup xinetd. If you go the
> xinetd route, that means that there won't be a dedicated rsync daemon
> running. You could elect to leave the xinetd con
On Thu, Oct 09, 2008 at 03:29:04PM +0100, michael wrote:
> and this is when I've tried both of
> a) /usr/bin/rsync --daemon -v
> b) sudo /sbin/chkconfig rsync on
Fedora supplies an /etc/xinetd.d/rsync file that defaults to off. Using
your b command should turn it on and sighup xine
;ve tried both of
> a) /usr/bin/rsync --daemon -v
> b) sudo /sbin/chkconfig rsync on
Fedora does not provide an initscript for rsync, so you should be using
command (a). You need to write an /etc/rsyncd.conf file if you haven't
already; see the rsyncd.conf(5) man page for details. If t
Maybe the daemon is running but I don't think so:
[EMAIL PROTECTED]:/var/log$ ps -elf|grep rsync
0 S mkb 24869 21866 0 80 0 - 17433 pipe_w 15:26 pts/4
00:00:00 grep rsync
and this is when I've tried both of
a) /usr/bin/rsync --daemon -v
b) sudo /sbin/chkconfig rsync on
I also
nsfers then run, they run as nobody.
> >
> > I would like the rsync daemon to connect to 873 (as root)
> > then possibly do a chroot and then run always as something else
> > than root (maybe nobody).
> >
> > It this advisable? Is it possible?
>
> The
On Sat, 2008-08-30 at 18:23 +0200, Keld Jørn Simonsen wrote:
> I run a mirror service where for gentoo I run rsync as a daemon.
> Currently the daemon runs root to get the 873 port opened.
> And when transfers then run, they run as nobody.
>
> I would like the rsync daemon to con
Hi
I run a mirror service where for gentoo I run rsync as a daemon.
Currently the daemon runs root to get the 873 port opened.
And when transfers then run, they run as nobody.
I would like the rsync daemon to connect to 873 (as root)
then possibly do a chroot and then run always as something
On Mon, 2008-08-11 at 13:44 -0700, Tamara Temple wrote:
> Ok, but what should be *in* the rsyncd.conf file. the man page isn't
> at all clear what should be included.
See the rsyncd.conf(5) man page for details and examples:
http://rsync.samba.org/ftp/rsync/rsyncd.conf.html
> I just want to do
sender=2.6.9]
paladin:~ tamara$
there is no rsyncd.conf file.
That would be the problem. An rsync daemon needs a configuration
file;
it will look for the file at /etc/rsyncd.conf unless you specify a
different path with a --config option in the command inetd is running.
In general, you sh
ctures/
> rsync: connection unexpectedly closed (0 bytes received so far) [sender]
> rsync error: error in rsync protocol data stream (code 12) at /
> SourceCache/rsync/rsync-35.2/rsync/io.c(452) [sender=2.6.9]
> paladin:~ tamara$
> there is no rsyncd.conf file.
That would be the pro
This is a newbie question. I've looked through the archives and
haven't found an answer to this.
I set up rsync in inetd.conf to respond on request. When I give a
remote request to the machine, I get the following error:
paladin:~ tamara$ rsync -avr /Volumes/Music/Pictures/ rsync://
[EMAIL
https://bugzilla.samba.org/show_bug.cgi?id=5633
--- Comment #4 from [EMAIL PROTECTED] 2008-07-28 03:59 CST ---
Thanks, backport patch works well for me.
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
You
https://bugzilla.samba.org/show_bug.cgi?id=5633
--- Comment #3 from [EMAIL PROTECTED] 2008-07-28 03:27 CST ---
Created an attachment (id=3425)
--> (https://bugzilla.samba.org/attachment.cgi?id=3425&action=view)
The --dparam (-M) daemon option for 3.0.4.
The 3.0.x branch is only gett
https://bugzilla.samba.org/show_bug.cgi?id=5633
--- Comment #2 from [EMAIL PROTECTED] 2008-07-28 02:10 CST ---
Could this be backported to 3.0.x (3.0.4) ?
--
Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email
--- You are receiving this mail because: ---
Y
you specify
the pidfile like this:
rsync --daemon --dparam pidfile=/tmp/other.pid
or
rsync --daemon -M pidfile=/tmp/other.pid
You can adjust any global or default value using that option, and it will
supersede a global/default value in the config file (but will not supersede an
explicitly
https://bugzilla.samba.org/show_bug.cgi?id=5633
Summary: --pidfile option for rsync daemon
Product: rsync
Version: 3.0.3
Platform: Other
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P3
Matt McCutchen escribió:
On Fri, 2008-06-06 at 10:02 -0300, Alejandro Celery wrote:
I have a problem: I was running rsync --daemon on a Ubuntu 6.10 linux
without problems. I used it to sync our company intranet from a Windows
host through deltacopy. Then I migrated my system to new hardware
On Fri, 2008-06-06 at 10:02 -0300, Alejandro Celery wrote:
> I have a problem: I was running rsync --daemon on a Ubuntu 6.10 linux
> without problems. I used it to sync our company intranet from a Windows
> host through deltacopy. Then I migrated my system to new hardware and
> inst
Hi everyone.
I have a problem: I was running rsync --daemon on a Ubuntu 6.10 linux
without problems. I used it to sync our company intranet from a Windows
host through deltacopy. Then I migrated my system to new hardware and
installed Ubuntu 7.10 on it. I run rsync --daemon with the same
1 - 100 of 220 matches
Mail list logo
