I was terribly amused, when doing some research on one of our servers, to see the following line in the command history:
Of course, that didn't work, and apparently successive attempts failed until eventually, the following was used:
perl -e'symlink($_ => "$_\r") for @ARGV'
/usr/bin/perl /usr/bin/python /usr/bin/ruby
This was done because these are dedicated servers and customers sometime FTP programs written on a Windows box to their Linux box and the symlink was considered easier than writing a custom FTP server or running a cron job to find the errant files
Can anyone think of a better solution which doesn't require manual intervention after setting up a dedicated server for a customer who doesn't know about line endings?