Re: Selecting encrypted files list

[Gary H. <gar...@gm...>]

Hi Shachar,

Thanks for the reply. I actually did a work around bu writing to
/usr/local/bin rather than cygdrive/c, this worked fine. When I tried
to write to cygdrive I couldnt get it to encrypt or create the folder
structures due to the permission error.

I am running cygwin as there doesnt seem to be a windows version of
rsync i.e. I run rsycrypto first then rsync these files.

Cheers

Gary



On 7/3/05, Shachar Shemesh <rsy...@sh...> wrote:
> Gary Holzer wrote:
>=20
> >Dear List,
> >
> >
> >
> Hi Gary,
>=20
> Sorry for taking so long to answer. I have totally missed your email.
>=20
> >In a previous part of the script I sucessfully create the $FILELIST
> >and set up the other variables. The $CRYPT_DIR is on the same box that
> >is running cygwin i.e. the script and rsyncrypto. For some reason when
> >I run the script I get the following errors in the $TEMPFILE for each
> >file I try to encrypt in $FILELIST
> >
> >e.g.
> >
> >Error in encryption of /cygdrive/c/Work/Jo/Uni/Proposal - professional
> >comm.doc: mkdir failed(/cygdrive/c): Permission denied
> >
> >
> Did the actual encryption succeed?
>=20
> The problem is that rsyncrypto, in order to make sure the entire
> directory path exists, creates each individual subdirectory. As such, it
> also tries to create /cygdrive and /cygdrive/c. It is programmed to
> ignore "file exists" errors as irrelevant.
>=20
> The problem is that /cygdrive and /cygdrive/c are not regular
> directories. They are made up by cygwin for the purpose of emulating the
> Windows forset view over the cygwin tree view. As such, cygwin returns
> "permission denited" for them, rather than the more conventional "file
> exists". I actually think this is a bug in cygwin, btw.
>=20
> I have a question, though. Why are you using the cygwin version when you
> can use the native Windows version?
>=20
>        Shachar
>=20
> --
> Shachar Shemesh
> Lingnu Open Systems Consulting
> http://www.lingnu.com/
>=20
>