<HTML><BODY>
<div><SPAN contentEditable=false style="DISPLAY: inline-block"></SPAN>
<div>Memory footprint might be <SPAN class=correction id="">improved</SPAN>.</div>
<div> </div>
<div> For me with version 0.6.0, I have an <SPAN class=correction id="">nxagent</SPAN> that runs for quite a long time. It now takes 14MB of shared memory 88MB of residential memory and 168MB of virtual memory (with <SPAN class=correction id="">htop</SPAN> (<SPAN class=correction id="">SHR</SPAN>;RES;<SPAN class=correction id="">VIRT</SPAN>)). For one user sure it is <SPAN class=correction id="">ok</SPAN>, but if a system have (4GB/88M=) 45 users the memory requirement of the <SPAN class=correction id="">nxagents</SPAN> may consume all of the existing memory.<SPAN style="DISPLAY: inline-block"></SPAN></div>
</div>
<div> </div>
<br>
-----Original Message-----<br>
From: FabianFranz@gmx.de<br>
To: freenx-knx@kde.org<br>
Sent: Mon, 2 Apr 2007 5:42 PM<br>
Subject: [FreeNX-kNX] Its release time again ... Any open issues?<br>
<br>
<STYLE>
.AOLPlainTextBody {
margin: 0px;
font-family: Tahoma, Verdana, Arial, Sans-Serif;
font-size: 12px;
color: #000;
background-color: #fff;
}
.AOLPlainTextBody pre {
font-size: 9pt;
}
.AOLInlineAttachment {
margin: 10px;
}
.AOLAttachmentHeader {
font: 11px arial;
border: 1px solid #7DA8D4;
background: #F9F9F9;
}
.AOLAttachmentHeader .Title {
font: 11px arial;
background: #B5DDFA;
padding: 3px 3px 3px 3px;
}
.AOLAttachmentHeader .FieldLabel {
font: 11px arial;
color: #000000;
padding: 1px 10px 1px 9px;
background: #F9F9F9;
}
.AOLAttachmentHeader .FieldValue {
font: 11px arial;
color: #000000;
background: #F9F9F9;
}
.AOLAttachmentHeader a, .AOLImage a {
color: #2864B4;
text-decoration: none;
}
.AOLAttachmentHeader a:hover, .AOLImage a:hover {
color: #2864B4;
text-decoration: underline;
}
.AOLWebSuiteCompose .AOLPicturesFullSizeLink,
.AOLWebSuite .AOLPicturesFullSizeLink {
height: 1px;
width: 1px;
overflow: hidden;
}
body {
background-color: white;
font-family: "Verdana";
font-size: 10pt;
border: 0px;
}
.AOLWebSuiteCompose p {
margin: 0px;
padding: 0px;
}
img.managedImg {
width: 0px;
height: 0px;
}
img.placeholder {
width: 275px;
height: 206px;
background: #F4F4F4 center center no-repeat;
border: 1px solid #DADAD6 !important;
}
</STYLE>
<div class=AOLPlainTextBody id=AOLMsgPart_0_856baae4-4de5-4259-99b3-059c05dcab09><PRE><TT>Spring: Flowers start blooming, the weather is nicer and a new release of FreeNX
stands "in front of the door". (german saying)
The reason for the release is that bugs keep popping up that are already fixed
in SVN, which is bad for time reasons ...
Before we go "gold" with 0.6.1 though, I would like to ask if there are any
other open issues besides MAC keyboard support?
Also if any of you are a bit adventurous, please try SVN _now_. Because that
will be the new release soon.
cu
Fabian
________________________________________________________________
Were you helped on this list with your FreeNX problem?
Then please write up the solution in the FreeNX Wiki/FAQ:
<A href="http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ" target=_blank>http://openfacts.berlios.de/index-en.phtml?title=FreeNX_FAQ</A>
Don't forget to check the NX Knowledge Base:
<A href="http://www.nomachine.com/kb/" target=_blank>http://www.nomachine.com/kb/</A>
________________________________________________________________
FreeNX-kNX mailing list --- <A href='javascript:parent.ComposeTo("FreeNX-kNX%40kde.org", "");'>FreeNX-kNX@kde.org</A>
<A href="https://mail.kde.org/mailman/listinfo/freenx-knx" target=_blank>https://mail.kde.org/mailman/listinfo/freenx-knx</A>
________________________________________________________________
</TT></PRE></div>
<!-- end of AOLMsgPart_0_856baae4-4de5-4259-99b3-059c05dcab09 -->
<div class="AOLPromoFooter">
<hr style="margin-top:10px;" />
<a href="http://pr.atwola.com/promoclk/100122638x1081283466x1074645346/aol?redir=http%3A%2F%2Fwww%2Eaim%2Ecom%2Ffun%2Fmail%2F" target="_blank"><b>Check Out the new free AIM(R) Mail</b></a> -- 2 GB of storage and industry-leading spam and email virus protection.<br />
</div>
</BODY></HTML>