All the Perl that's Practical to Extract and Report
use Perl Log In
Ovid (2709)
(email not shown publicly)
http://publius-ovidius.livejournal.com/
AOL IM: ovidperl (Add Buddy, Send Message)
Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.
Hilarious Unix Commands
I was terribly amused, when doing some research on one of our servers, to see the following line in the command history:
ln -s
/usr/bin/perl /usr/bin/perl\r
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?
I pour myself a cup of strong coffee. :-)
-- Jarkko Hietaniemi
Log surfing (Score:1)
shell quoting of special chars (Score:1)
ln -s foo foo^M
lrwxrwxrwx 1 uri staff 3 Nov 30 12:53 foo? -> foo
but your perl solution is fine too.
uri
some of ftp daemon support upload filter (Score:1)
No -s (Score:1)
I'd consider using a hard link 'better' than using a symlink - it requires less file system access to get to the binary. It also uses marginally less disk space - and less inodes.
But I don't think you were looking for this kind of 'better'.
Re: (Score:2)