I would like to request that rsync -n to an rsync server target that is read only be supported rather than generating the following error, ERROR: module is read only The motivation is to allow the generation of a list of files against an rsync target that will be used by another application. Since dry-run mode does not require write access it would be convenient if the “module is read only” error message was only thrown if/when a write attempt is made and not assume write access is needed. Thanks. -- Stuart Anderson anderson at ligo.caltech.edu http://www.ligo.caltech.edu/~anderson
On Fri 01 Jul 2016, Stuart Anderson wrote:> I would like to request that rsync -n to an rsync server target that is read only be supported rather than generating the following error, > ERROR: module is read only > > The motivation is to allow the generation of a list of files against an rsync target that will be used by another application. Since dry-run mode does not require write access it would be convenient if the “module is read only” error message was only thrown if/when a write attempt is made and not assume write access is needed.Of course, one could argue that the point of the -n option is to test if it will work when the -n option is removed. That would not be the case here. Paul
Paul Slootman <paul+rsync at wurtel.net> wrote:> On Fri 01 Jul 2016, Stuart Anderson wrote: > > I would like to request that rsync -n to an rsync server target that > > is read only be supported rather than generating the following error, > > ERROR: module is read only > > ... > Of course, one could argue that the point of the -n option is to test if > it will work when the -n option is removed. That would not be the case > here.This could be covered by emitting a warning (rather than an error) if the target of --dry-run is read-only.