On 29 May 2003, Andrew Klein [EMAIL PROTECTED] wrote:
The getpassphrase() call is identical to getpass() except it returns 256
chars maximum. Of course you would have to mess with autoconf but I
don't think that should be too hard. Based on the autoconf stuff in the
latest rsync release,
The getpassphrase() call is identical to getpass() except it returns 256
chars maximum. Of course you would have to mess with autoconf but I
don't think that should be too hard. Based on the autoconf stuff in the
latest rsync release, the compile check would be something along these
lines:
I have run across an interesting issue when running rsync from Solaris
to an rsync daemon on Linux. It works properly when I specify the
password on the command line:
RSYNC_PASSWORD=the_Password rsync -r /tmp/test [EMAIL PROTECTED]::test_user/topdir/subdir
However, if I do not specify the
On Wed, May 28, 2003 at 10:27:44AM -0400, Andrew Klein wrote:
I have run across an interesting issue when running rsync from Solaris
to an rsync daemon on Linux. It works properly when I specify the
password on the command line:
RSYNC_PASSWORD=the_Password rsync -r /tmp/test
[EMAIL
I believe J.W. Schultz replied to this but I lost it since
I was not yet fully subscribed to the list. He rightly suggested
that the a portable getpass() would be non-trivial. An alternate
suggestion though: Solaris has a getpassphrase() call that
returns up to 256 chars. The configure
--On Wednesday, May 28, 2003 13:26:17 -0400 Andrew Klein
[EMAIL PROTECTED] wrote:
I believe J.W. Schultz replied to this but I lost it since I was not yet
fully subscribed to the list. He rightly suggested that the a portable
getpass() would be non-trivial. An alternate suggestion though:
On Wed, May 28, 2003 at 04:14:54PM -0400, Carson Gaspar wrote:
--On Wednesday, May 28, 2003 13:26:17 -0400 Andrew Klein
[EMAIL PROTECTED] wrote:
I believe J.W. Schultz replied to this but I lost it since I was not yet
fully subscribed to the list. He rightly suggested that the a
