>
> REX0634E: Error 40.900: SysFileTree() argument 1 must be less than 255
> characters in length
I don't believe this restriction makes sense - please open a request for
enhancement (a bug report won't do, since we explicitly documented this
behavior)
Thanks!
---
Hello Erich thanks for checking. Here is the exact error message for both cases
(one at the time, the program breaks at this statement)
For dirs
*-* Compiled routine "SYSFILETREE".
7 *-* res = SysFileTree(SourceDir || slash || "*","dir","DO")
REX0040E: Error 40 running /Users/po/Data
>
> got the error message that the path was to long, and that it can only be
> 255 characters long on Unix
>
Hi P.O.
what's the exact error message?
what commands are you using to back "up downwards" (shell? Rexx?)
the maximum path length on Unix typically is not 255, rather much longer
"say .Rexx
I have a related question that someone might have the answer to,
While backing up everything from the root directory downwards on the Mac I
quickly got the error message that the path was to long, and that it can only
be 255 characters long on Unix like systems (like the Mac). This is a serious
Dear all,
Please close this item, I can answer my own question now. Sorry for wasting
bandwidth.
While working on the Mac I realized that the system volume is not indeed a
volume but just a symbolic link to the root directory (/), hence the
explanation that SysFileTree() behaves differently on
Dear Developers,In addition to what I wrote below I realized that the behavior is different depending on if the volume is a system volume (as in the case below) or another volume (separate disk or mounted volume on a NAS on the network). In the first case the behavior is as below, in the second cas
