Steve Grazzini wrote: > > And besides, open() is not particularly easy to > override. You'd have to account for all of: > > open FH, $path; > open FH, "> $path"; > open FH, ">", $path; > open FH, ">", \$sstream; > open FH, "command |"; > open FH, "| command";
i don't recommand people do all of the above. if the need arise to access the open() function that came with Perl, CORE::open() is good enought. > > And six corresponding versions where FH is an > undefined scalar, not a glob reference. > > And there's this oddball: > > open $path; # morphs $path into a filehandle > > But *never* this: > > my $fh = open($path); > > Anyway most people end up using filesystem permissions > for sandboxing, or chroot(), but you can try this: true. chroot() is powerful. many daemon calls chroot() to isolate itself from the rest of the filesystem. it's safer than to mask Perl build in function. david -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
