Skip to content
Snippets Groups Projects
Commit ae9bec1a authored by Gerardo Ganis's avatar Gerardo Ganis
Browse files

Update following recent changes/additions

git-svn-id: http://root.cern.ch/svn/root/trunk@24721 27541ba8-7e3a-0410-8455-c3a389f83636
parent 4dc5602c
No related branches found
No related tags found
No related merge requests found
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html> <html>
<head> <head>
<title>PROOF release notes</title>
<title>PROOF release notes</title>
</head> </head>
<body> <body>
<br> <br>
<hr> <hr>
<a name="proof"></a> <a name="proof"></a>
<h3>PROOF</h3> <h3>PROOF</h3>
<ul> <ul>
<li>New functionality</li> <li>New functionality</li>
<ul> <ul>
<li>XrdProofd plug-in</li>
<ul>
</ul>
<li>Possibility to define the list worker directly in the
xrootd config file (new directive xpd.worker, see Wiki reference pages)</li>
<li>Improvements:</li> <li>Support for automatic reconnections in the case xrootd
is restarted</li>
<li>Dedicated admin area (under <span style="font-style: italic;">xrd.admin</span>/.xproof.<span style="font-style: italic;">port</span>) to
keep information about active and terminated sessions, and active
clients. This is used to reguraly check the client and session
activity, to cleanup orphalin sessions and to shutdown inactive client
connections.&nbsp;</li>
<li>domain + level control of printout message</li>
</ul>
</ul>
<ul> <ul>
</ul>
<li> <li>Improvements:</li>
Log retrieval:</li>
<ul>
<li>XrdProofd plug-in</li>
<ul> <ul>
<li>Overall refactorization&nbsp;for easier
maintainance and improved solidity</li>
<li> <li>Improved format of printout messages: all information
for 'grep' operations, use the system 'grep' command via 'popen' messages contain now the tag 'xpd-I' and all error messages the
instead of a handmade filtering; this implies that the full grep functionality is now available</li> tag&nbsp;'xpd-E', so that they can easily be grepped out from the
log file.
</li>
</ul>
<li>Log sending</li>
<ul>
<li> <li>
set the default number of displayed lines to 100 instead of 10</li> Implement selective sending of logs from workers to master to avoid duplicating
too many text lines on the master log. Logs are now sent only after Exec, Print
requests and in case an error (level &gt;= kError) occured. Of course, the full
logs can always be retrieved via TProofMgr::GetSessionLogs
</li>
</ul>
<li>Log retrieval:</li>
<ul>
<li>for 'grep' operations, use the system 'grep' command
via 'popen'
instead of a handmade filtering; this implies that the full grep
functionality is now available</li>
<li>set the default number of displayed lines to 100
instead of 10</li>
</ul> </ul>
<li>Improve diagnostic in case of worker death: clients will now
<li>Improve diagnostic in case of worker death: clients will
now
receive a message containing the low level reason for the failure and a receive a message containing the low level reason for the failure and a
hint for getting more information</li> hint for getting more information</li>
</ul>
</ul>
<ul> <ul>
</ul> </ul>
<li>Fixes</li> <li>Fixes</li>
<ul> <ul>
<li>Invalidate the TProofMgr when the physical connection is
closed; avoids
crashing when trying to get the logs after a failure. </li>
<li> <li>Fix a memory leak in log retrieval (the TProofLog object
Invalidate the TProofMgr when the physical connection is closed; avoids was never
crashing when trying to get the logs after a failure.
</li>
<li>
Fix a memory leak in log retrieval (the TProofLog object was never
deleted)</li> deleted)</li>
<li>Add protections for the cases the manager cannot be
initialized</li>
<li> <li>Fix a race condition possibly affecting the handling of
Add protections for the cases the manager cannot be initialized</li> workers death</li>
<li>Fix a race condition possibly affecting the handling of workers death</li>
<li>Avoid duplicating worker logs in the master log file unless <li>Avoid duplicating worker logs in the master log file
unless
when explicitely needed by the request (Exec(...), Print(...)) or when when explicitely needed by the request (Exec(...), Print(...)) or when
an error occured</li> an error occured</li>
</ul> </ul>
</ul> </ul>
</body> </body>
</html> </html>
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment