I just installed v 18.1 and noticed that since 17.9a
POPFile has ceased to ignore the WM_ENDSESSION message (or
CTRL_LOGOFF_EVENT) on the Windows platform.
I had 17.9a installed as a service using srvany
and it worked great. 18.1 however, dies any time
a user (any user) logs out.
Can anyone suggest a fix?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm, this doesn't sound good. I'm about to upgrade from v17.9a myself, and I'm currently running it as an NT service. After reading this, however, I'm reluctant to install just yet.
I hope we can find an answer to this one -- thanks for posting it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'd suggest running it as a per-user logon program for the time-being. Either that, or use one of those service wrappers, which really should swallow any messages that services shouldn't see or care about.
I'll have to find out whether we can set a configuration option for ignoring these messages, though.
Ignoring the WM_ENDSESSION messages in all cases before was also pretty badly broken, IMO. Anyone who started POPFile for a single user would still have it running for all other users. Woops.
Regards,
Sam
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2003-03-29
I think this might actually be a function of Perl. I noticed that with the newer version of POPFile a new version of
Perl is required. Perhaps the new version of perl is no
longer handling these events in the same fashion???
I thought about simply downgrading perl, but noticed
that there was some multi-threading functionality that
the newer version of POPFile needs -- I guess for the
time being I will switch back to 17.9a and give up
those nice new GUI features to which I've recently become accustomed... :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Data point: I'm running 0.18.1 Cross-Platform as a service under Cygwin on Windows XP Home, and it stays up across user switches and logouts with no problems. I'm the only user who ever downloads mail on that box, though, which makes things a little less complex.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is off-topic but I have to ask to satisfy my curiousity.
When you run under Cygwin, am I correct that the perl you are using is a non-windows perl that installs under Cygwin? So if you were to test for the OS from within perl, what would it show?
Scott
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I just installed v 18.1 and noticed that since 17.9a
POPFile has ceased to ignore the WM_ENDSESSION message (or
CTRL_LOGOFF_EVENT) on the Windows platform.
I had 17.9a installed as a service using srvany
and it worked great. 18.1 however, dies any time
a user (any user) logs out.
Can anyone suggest a fix?
Hmm, this doesn't sound good. I'm about to upgrade from v17.9a myself, and I'm currently running it as an NT service. After reading this, however, I'm reluctant to install just yet.
I hope we can find an answer to this one -- thanks for posting it.
I'd suggest running it as a per-user logon program for the time-being. Either that, or use one of those service wrappers, which really should swallow any messages that services shouldn't see or care about.
I'll have to find out whether we can set a configuration option for ignoring these messages, though.
Ignoring the WM_ENDSESSION messages in all cases before was also pretty badly broken, IMO. Anyone who started POPFile for a single user would still have it running for all other users. Woops.
Regards,
Sam
I think this might actually be a function of Perl. I noticed that with the newer version of POPFile a new version of
Perl is required. Perhaps the new version of perl is no
longer handling these events in the same fashion???
I thought about simply downgrading perl, but noticed
that there was some multi-threading functionality that
the newer version of POPFile needs -- I guess for the
time being I will switch back to 17.9a and give up
those nice new GUI features to which I've recently become accustomed... :)
Data point: I'm running 0.18.1 Cross-Platform as a service under Cygwin on Windows XP Home, and it stays up across user switches and logouts with no problems. I'm the only user who ever downloads mail on that box, though, which makes things a little less complex.
This is off-topic but I have to ask to satisfy my curiousity.
When you run under Cygwin, am I correct that the perl you are using is a non-windows perl that installs under Cygwin? So if you were to test for the OS from within perl, what would it show?
Scott
% perl -e 'print $^O'
cygwin
Dennis, did you ever get this one straightened out?