set -x

[brian_31]

I have put set -x in my script to find why it fails via cron and i get this
crontab: error on previous line; unexpected character found in line.
crontab: errors detected in input, no crontab file generated.

when i do vi i do not see any unexpected characters. how do i see it? why does set -x complain that way. i have set -x as the first line.

Thanks

Brian

[Ralph Grothe]

In vi try

Esc:set list

or try

cat -v /suspicious/file

or

od -c /suspicious/file

[Oviwan]

Hey

in the first line of the script you have to set
#!/usr/bin/ksh or #!/usr/bin/sh or whatever and then set -x

Regards

[Steve Steel]

Hi


Indeed

#!/bin/ksh
set -x


Steve Steel

[Steven E. Protter]

Shalom Brian,

I think set -x should be in the script, not the crontab file.

SEP

[Sandman!]

you might have invisible or non-printing characters in your file. Do "cat -vt filename" to see if that's the case.