[naviserver-devel] Nsssl - small logging glitch

2013-06-04 Thread David Osborne
Hi,

Thanks for 4.99.5. It's been working well for us so far.

I've noticed a small glitch in the logging of nsssl shutdowns (not sure if
it's new to 4.99.5 or not)

When NsWaitDriversShutdown logs the stopped message for nsssl the driver
name seems to gain an extra unprintable character.
[9715.7f556c6f2700][-main-] Notice: [driver:nsssl#]: stopped
where # is an unprintable character (possibly 007F)

I think it could be an issue relating to how NsWaitDriversShutdown in
particular accesses the driver name, rather than a more global encoding
problem, since NsStopDrivers logs the stopping message for nsssl without
any similar problems on the same installation.

Could this be a local configuration problem?
This is using the encoding defaults from conf/sample-config.tcl

Regards,
David Osborne
--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j___
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel


Re: [naviserver-devel] Nsssl - small logging glitch

2013-06-04 Thread Gustaf Neumann

Hi David,

no, this is not a configuration problem, but a problem with the shutdown 
order.


This issue should be fixed by the following change:
https://bitbucket.org/naviserver/naviserver/commits/d812197ba4853bd50d003f14555cf538e69da33b?at=default

Naviserver has still a small problem, that a shutdown of the server 
might crash during the shutdown of the threads (it looks like a problem 
with Tcl's thread local storage being freed to early), but this seems to 
depend on the timings and is not easy to debug, since tcl shutdown 
contains still some moving magic. However, this happens so late that it 
is in practice not a problem.


Please try the change...

-gustaf neumann

Am 04.06.13 13:09, schrieb David Osborne:

Hi,

Thanks for 4.99.5. It's been working well for us so far.

I've noticed a small glitch in the logging of nsssl shutdowns (not 
sure if it's new to 4.99.5 or not)


When NsWaitDriversShutdown logs the stopped message for nsssl the 
driver name seems to gain an extra unprintable character.

[9715.7f556c6f2700][-main-] Notice: [driver:nsssl#]: stopped
where # is an unprintable character (possibly 007F)

I think it could be an issue relating to how NsWaitDriversShutdown in 
particular accesses the driver name, rather than a more global 
encoding problem, since NsStopDrivers logs the stopping message for 
nsssl without any similar problems on the same installation.


Could this be a local configuration problem?
This is using the encoding defaults from conf/sample-config.tcl

Regards,
David Osborne


--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j


___
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel



--
Univ.Prof. Dr. Gustaf Neumann
Institute of Information Systems and New Media
WU Vienna
Augasse 2-6, A-1090 Vienna, AUSTRIA

--
How ServiceNow helps IT people transform IT departments:
1. A cloud service to automate IT design, transition and operations
2. Dashboards that offer high-level views of enterprise services
3. A single system of record for all IT processes
http://p.sf.net/sfu/servicenow-d2d-j___
naviserver-devel mailing list
naviserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/naviserver-devel