:: You're probably storing it in a global so it never gets cleaned
:: up. Don't
:: do that.
No, it's not a global Perrin - I've learnt that lesson! :-)
Ged Haywood wrote:
>
> Hi there,
>
> On Tue, 11 Dec 2001, Jonathan M. Hollin wrote:
>
> > When using Mail::Sender only the first email is sent on my mod_perl server.
> > When I investigated, I realised that the socket to the SMTP server was
> > staying open after the completion of that first em
should one not unlink() after the close?
> > When using Mail::Sender only the first email is sent on my mod_perl
> server.
> > When I investigated, I realised that the socket to the SMTP server was
> > staying open after the completion of that first email (presumably mod_perl
> > is responsible f
> When using Mail::Sender only the first email is sent on my mod_perl
server.
> When I investigated, I realised that the socket to the SMTP server was
> staying open after the completion of that first email (presumably mod_perl
> is responsible for this persistence).
>
> Is there any way to defeat
--On mardi 11 décembre 2001 12:25 + "Jonathan M. Hollin"
<[EMAIL PROTECTED]> wrote:
> Hey Gang,
>
> When using Mail::Sender only the first email is sent on my mod_perl
> server. When I investigated, I realised that the socket to the SMTP
> server was staying open after the completion of that
Hi there,
On Tue, 11 Dec 2001, Jonathan M. Hollin wrote:
> When using Mail::Sender only the first email is sent on my mod_perl server.
> When I investigated, I realised that the socket to the SMTP server was
> staying open after the completion of that first email (presumably mod_perl
> is respon
Hey Gang,
When using Mail::Sender only the first email is sent on my mod_perl server.
When I investigated, I realised that the socket to the SMTP server was
staying open after the completion of that first email (presumably mod_perl
is responsible for this persistence).
Is there any way to defeat
