in reply to perl -e problem

I figured out the problem!!!!!!
My permissions on /devices/pseudo/mm@0:null were too restrictive and ownership was not correct. Changed owner to root:sys and permissions to 666 and all is right with the world.
Found it out by doing a man on perl and getting an error of /dev/null: can not create

Thank you all for your help, I wouldn't have found it without your suggestions. :)

Replies are listed 'Best First'.
Re^2: perl -e problem
by merzy (Scribe) on May 21, 2005 at 03:00 UTC
    Glad you found your solution!

    Next time, try a 
        truss -f -topen perl ...
    That'll give you a good idea of what files your process is trying to open and will likely point directly at the permissions issue.
[reply]

      For others' edification, truss : Solaris :: strace : Linux. See: Monitoring and Tracing Unix Processes

      An strace command to do the same thing as the above truss command would be (sorry if flags aren't portable; strace version 4.5.9): strace -f -e trace=open perl ...

      Thanks for the extremely helpful tip merzy.

[reply]
[d/l]

In Section Seekers of Perl Wisdom