I guess you are creating the Net::FTP object before the fork ?
which means after the fork both parent and child have the object
and connection. This is an issue.
As a workaround you could try close($ftp) in the process
that does not want/need the ftp object.
Graham.
On Tue, Aug 01, 2000 at 10:34:53AM -0400, Anthony R. J. Ball wrote:
>
> I have a project which uses Net::FTP to allow ftp
> through a cgi. I want to fork off my session handler
> for individual downloads so people can still browse
> and even download more than one file at a time but
> forking really seems to screw with my FTP handle. I
> don't mind making a second FTP handle for a download,
> but how do I prevent the original one from exploding
> when I fork?
>
> --
> ___ __ __ __ _ _ ____ _ _ ____ ____
> / __)( )( ) /__\( \/ )( ___) ( \( )( ___)(_ _)
> \__ \ )(__)( /(__)\\ / )__) ) ( )__) )(
> (___/(______)(__)(__)\/ (____)()(_)\_)(____) (__)
> There were computers in Biblical times. Eve had an Apple.
>
>
