Well, from MPOV you do not need a shutdown. Just update the nx packages. The next new connection will use the new nxagent.
Let me now when you want to compile an own version, so that I can provide some instructions for sanitizer integration. (I need to figure that out again since I mainly use valgrind). Uli On Fri, Jan 24, 2020 at 8:35 AM Johannes Töger <johannes.to...@med.lu.se> wrote: > > Yeah, I could absolutely compile my own version. I think it might be better > to try with the .deb packages you linked first though. > > I need to ask my users for a window where I can shut down everything first, > so might take a few days before I can organize this. > > — > Johannes Töger > > Associate Senior Lecturer > Cardiac MR Group > Department of Clinical Sciences Lund, Clinical Physiology > Lund University, Sweden > > -----Original Message----- > From: Ulrich Sibiller <ul...@gmx.de> > Sent: Thursday, January 23, 2020 19:43 > To: Johannes Töger <johannes.to...@med.lu.se> > Cc: Bernd Schubert <bs_li...@aakef.fastmail.fm>; x2go-user@lists.x2go.org > Subject: Re: [X2Go-User] Long-running x2goagent, high memory usage > > On Thu, Jan 23, 2020 at 7:35 PM Johannes Töger <johannes.to...@med.lu.se> > wrote: > > > > Thanks to you both for getting involved in this. > > > > I've been swamped with other things, so not much to report. I did manage to > > plot the x2goagent memory use over time though. Maybe this can help. > > > > Link to plot: > > https://imgur.com/a/lDqZ2zd > > > > As you see, several users have a constant memory use. However, 3 of them > > have a constantly increasing memory use. So not isolated incidents that > > leak, but rather a continuous drip. > > OK, well, do you think you could compile an own version of x2go? > > Uli _______________________________________________ x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
