cosign-discuss at umich.edu
general discussion of cosign development and deployment
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: CosignIIS problems
Agreed. All filter loading issues I've experienced (IIS5 and IIS6 across
nearly a dozen systems) have been resolvable through configuration changes
followed by an IIS service restart - rebooting the server has not been
[mailto:jarod@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx] On Behalf Of jarod@xxxxxxxxx
Sent: Thursday, July 15, 2004 4:39 PM
To: Phil Pishioneri; 'Cosign Discussion'
Subject: Re: CosignIIS problems
With both IIS 5 and 6, restarting IIS will reload the filter as well as
pick up any config.dll.config file changes. In IIS 5.0 stopping and
restarting the web site usually unloads then reloads the IISCosign filter,
too. In IIS 6.0, stopping the web site does not unload the filter... at
least right away. (It seems after a certain amount of inactivity that it
will, eventually, unload.) This means the filter still has exclusive write
control over the log file keeping it in a 'busy' state.
Has anyone had a situation where IISCosign wouldn't load until they
restarted their server? Here at U of M there was always another issue
preventing the filter from loading. That is, resetting web servers has not
been shown to fix a 'IICosign filter will not load' problem. Not yet
anyway and it'd probably be best if we keep it that way. :)
--University of Michigan
--On Thursday, July 15, 2004 11:09 AM -0400 Phil Pishioneri <pgp@xxxxxxx>
> While we're talking about the IIS filter...
> Anyone ever notice that, even after stopping the web server, the
> Cosign.log file is busy? I.e., Wordpad can't open it (though Edit from a
> cmd window can still get to it). Would seem to imply that a task didn't
> really quit (which then makes me wonder if restarting the web server will
> really pick up a config change, or if I have to reboot the system).