17 Oct
2004
17 Oct
'04
19:24
On Sunday, 17 October 2004 21.10, C Hamel wrote:
Another possibility (having read the others, first) is that you are experiencing what happened to me: for whatever reason, the tab delimitation got frelled and since I could see no garbage I put the cursor on the 'r' of root and backspaced to the previous parameter, than did one TAB; ditto on the actual command. That cured the problem, at least in my case.
This is what I meant about non-printable garbage characters. cron can handle any number and mixture of spaces and tabs (must be at least one) between the entries, so if that procedure worked there had to be at least one character in there that wasn't space or tab but that still wasn't visible on screen.