in reply to Cleaning up after CTRL-C when using Net::DNS::Nameserver on Windows?

Hi,

Without modifying Net::DNS::Nameserver, you could perform a fork (works ok with 5.8 and 2k+), where the child process becomes your dns server and the parent will be the controlling process. That way, you can safely keep both signal handlers. :-)

Jason L. Froebe

Team Sybase member

No one has seen what you have seen, and until that happens, we're all going to think that you're nuts. - Jack O'Neil, Stargate SG-1

  • Comment on Re: Cleaning up after CTRL-C when using Net::DNS::Nameserver on Windows?

Replies are listed 'Best First'.
Re^2: Cleaning up after CTRL-C when using Net::DNS::Nameserver on Windows?
by elwarren (Priest) on Jan 04, 2005 at 20:12 UTC
    I would rather not fork on windows. I'm trying to keep this code light on memory, and I've had problems with fork and reading from sockets on windows in the past.

    Setting this forking discussion aside, this still does't tell me why my END block doesn't run as I expect/want.

    It is windows, so I'm thinking about just calling my perl script from a batch file and reseting the interface with a second script that runs after the first one exits. Not as clean of a solution as I'd like, but eventually I expect this to run as a service, so the CTRL-C portion will be moot at that point...
[reply]

In Section Seekers of Perl Wisdom