> /path IN_CLOSE_WRITE /bin/sh -c '/bin/myscript "$@/@#"'



No, that won't work for all file names, especially file names containing

unusual features such as consecutive blanks, quotes, backslashes, or

newlines e.g.:



    Mom's  "Good"  Recipies 

      are fun \ to \\ eat.



In fact, consecutive blanks in a file name will produce empty arguments

to the called script, single backslashes in the name will disappear, and

multiple backslashes in the name will compress down to a single backslash.



We can work around everything except the lost backslashes.  File names

containing backslashes are impossible to handle correctly in incron since

incron throws away some of the backslashes before it calls the script.



A work-around that works for file names that do *not* contain backslashes

is to delimit the arguments with characters that can't appear in file

names, e.g.



  /path IN_CLOSE_WRITE /bin/myscript ///$@///@#///



and then recombine the multiple arguments into one and split them apart

again based on the "///" delimiters.  The script fragment below will do

that for file names that don't contain backslashes or newlines:



    #!/bin/sh -u

    args=$*

    arg1=$( echo "$args" | sed -e 's:^///::' -e 's:[/]//.*::' )

    arg2=$( echo "$args" | sed -e 's:[/]//$::' -e 's:.*///::' )

    logger -t "$0" "The actual argument is '$arg1/$arg2'"



The above work-around will handle all pathnames that do *not* contain

backslashes or newlines.  Blanks and quotes and all other special characters

are fine.  Using Perl or something smarter than sed to do the parsing,

we could also handle newlines correctly.  Pathnames containing backslashes

cannot be handled, since incron throws away some of the backslashes.



Edit: I had to change /// to [/]// in the above expressions to stop this

comment system from mangling the expressions into hyperlinks.  Please find

a better comment system that preserves blanks and doesn't mangle what I enter.