Question regarding exclude and invalid arg messages

[John Van Essen]

On Wed, 02 Jul 2003, Morten Primdahl <morten at kikobu.com> wrote:
>
>I still get some garbage on stderr:
>
>.qsJ4iC failed: Invalid argumentsp_ind/Emails ind/.Icon
>.klS8j3 failed: Invalid argumentsp_ud/Emails ud/.Icon

This is an error message with an embedded carriage return after the ".Icon"
that causes the last part of the message to overwrite the first part on a
terminal display.

There seems to be an embedded CR (Carriage Return) character in these names.
If the names (with the first part overwritten by the error message) were:

        <..some missing parts..>sp_ind/Emails ind/.Icon<CR>.qsJ4iC
        <..some missing parts..>sp_ud/Emails ud/.Icon<CR>.klS8j3

Then the error message would be:

mkstemp <..some missing parts..>sp_ind/Emails ind/.Icon<CR>.qsJ4iC failed: Invalid argument
mkstemp <..some missing parts..>sp_ud/Emails ud/.Icon<CR>.klS8j3 failed: Invalid argument

So it appears that the <CR> character (ASCII 13 decimal) is an invalid
character for mkstemp on the target filesystem.

>The garbage lines only come for the .Icon folder.

Makes sense if that's the only filename with an embedded <CR>.

>But also more valid messages like (still on stderr):
>
>mkstemp 2001_12_Villa_OpNed/01_Korrespondance ind/01 Bygherre/Emails/.Villa "up and go".1.N0LkFe failed: Invalid argument
>mkstemp 2001_12_Villa_OpNed/01_Korrespondance ind/01 Bygherre/Emails/.nyt på tegnefronten?.1.8ZzfZ6 failed: Invalid argument

Since these files are being created on your "FAT32 external HD", something
in these filenames is not allowed on that filesystem.  Perhaps the
double-quote and question mark characters are not valid in a filename?
This wold certainly be the case for a Windows system.  Thus mkstemp fails
(as it does for the embedded <CR>).
-- 
        John Van Essen <vanes002 at umn.edu>