![]() |
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| UNIX for Dummies Questions & Answers If you're not sure where to post a UNIX or Linux question, post it here. All UNIX and Linux newbies welcome !! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Passing a file descriptor | robotball | Shell Programming and Scripting | 6 | 06-08-2008 11:41 PM |
| File descriptor constant | vino | High Level Programming | 4 | 05-18-2005 02:18 AM |
| Problems with file descriptor | teo | High Level Programming | 11 | 05-09-2005 12:47 PM |
| File Descriptor Help | rahulrathod | UNIX for Dummies Questions & Answers | 3 | 10-14-2004 06:08 AM |
| file activity (open/closed) file descriptor info using KORN shell scripting | Gary Dunn | UNIX for Dummies Questions & Answers | 3 | 06-07-2004 02:54 PM |
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
||||
|
bad file descriptor?
Ok, I'm sure this is a total newbie question, but I think I'm in the right place, no?
I'm trying to call a perl module from a cgi script - Mail::Sendmail - and my web host installed the module in a directory that doesn't seem to be accessible, at least not the way I'm trying. But I thought you could call a module just about anywhere as long as you include a 'use lib' statement so perl can find it... Anyway, I guess my question is this: does 'bad file descriptor' indicate that a file pathname I've written is bunk? That basically the pathname is not correct? Thanks in advance for any light shed for a Unix rookie... Chris |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|