Re: Script running OK, re-loaded with no changes, then won't run uintil -w switch added.

To elaborate slightly on Podmaster's explanation: it wouldn't run without the "-w", because there was an extra character after "perl" -- a carriage return -- and the server does not have an executable file named "/usr/bin/perl\r" (or whatever path you're using.

Once you add the " -w" and upload again (using a method of file transfer that either adds or retains "\r" before every "\n"), "/usr/bin/perl" is now followed by a space, which is fine. (And once perl starts, it probably does the right thing with "-w\r".)

Comment on Re: Script running OK, re-loaded with no changes, then won't run uintil -w switch added.

Replies are listed 'Best First'.
Re^2: Script running OK, re-loaded with no changes, then won't run uintil -w switch added. by tinita (Parson) on Oct 17, 2005 at 22:08 UTC
and the server does not have an executable file named "/usr/bin/perl\r" years ago i thought about the idea if it wouldn't be the best for providers to just have a file "/usr/bin/perl\r" on the system that links to the correct binary. as far as i have tested scripts will run fine. not being serious, though =)	[reply]
Re^3: Script running OK, re-loaded with no changes, then won't run uintil -w switch added. by graff (Chancellor) on Oct 18, 2005 at 00:37 UTC
hehe... yes, that would be so clever. And when a sysadmin or anyone else does "ls /usr/bin" (and, just by coincidence, "perl\r" does not occur in the right-most column), they'll wonder why that one line of the listing is shorter than expected and has things out of order, and some programs that should be there are not showing up. Think of the fun everyone would have!	[reply]