From mikedep333@gmail.com Wed Aug 19 05:25:54 2015 Received: (at 923) by bugs.x2go.org; 19 Aug 2015 03:25:57 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=5.0 tests=BAYES_50,FREEMAIL_FROM, HTML_MESSAGE,T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2 Received: from mail-yk0-f172.google.com (mail-yk0-f172.google.com [209.85.160.172]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 50D135DA86 for <923@bugs.x2go.org>; Wed, 19 Aug 2015 05:25:54 +0200 (CEST) Received: by ykll84 with SMTP id l84so115613225ykl.0 for <923@bugs.x2go.org>; Tue, 18 Aug 2015 20:25:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=xvToU5+gPc/KvgwNoVDUiWX0bBsoHF4dZNPD0zs623M=; b=Oejf1ylp4+ekKy+nCpEB//SOqTL//GqIZcrg0M/+UASCy/wmXNz4aNJlWpUyIMCK0d 6t0CeCHhuR0NQe6rwbb9+t6PL7vzma4hk+g02sI7erUywvBIHf99dOhAEriMxVnGH7yx hKWdBt6i+E+WAmwsA4AcUKIQ/FUJk9nDbaufZSmoyhj4PAiiSRNidiBkEHgdfAx9eQ7m 0J0Rx+fElSrdolt9tZuc6kqIt2pozmljHqtPm7ckaNRCvHYj1LVh7wRvAQZMM46nSj5z sFBCrkfQoqwlTXUbOSbepBRIAixARNAUmcfU+DviSLSLSffzCMGouN91azywwPreJRUM PPLw== MIME-Version: 1.0 X-Received: by 10.129.45.194 with SMTP id t185mr11591021ywt.52.1439954753021; Tue, 18 Aug 2015 20:25:53 -0700 (PDT) Received: by 10.37.223.22 with HTTP; Tue, 18 Aug 2015 20:25:52 -0700 (PDT) In-Reply-To: <55D3533C.2090101@cora.nwra.com> References: <55D3533C.2090101@cora.nwra.com> Date: Tue, 18 Aug 2015 23:25:52 -0400 Message-ID: Subject: Re: [X2Go-Dev] Bug#923: .xsession-x2go-errors improvements From: Mike DePaulo To: 923@bugs.x2go.org Content-Type: multipart/alternative; boundary=001a114145368bed55051da197cb --001a114145368bed55051da197cb Content-Type: text/plain; charset=UTF-8 On Tue, Aug 18, 2015 at 11:46 AM, Orion Poplawski wrote: > Package: x2goserver > Version: 4.0.1.19 > > First issue is that ~/.xsession-x2go-errors is always appended to so it > grows > forever. It should at least get rotated to .old file. > I wholeheartedly agree. Plus there are weird instances where a command will make it grow to GB in size quickly. In general, I believe in following what the local X.org server sessions do. However, since I am often debugging issues with why apps are not working properly with X2Go, I would rather rotate than delete. > Second is with shared NFS home directories, multiple X2Go sessions get > logged > to the same file which is confusing. I would suggest putting the host name > into the log file name. I wholeheartedly agree. Gluster (for HA home dirs) is affected too. -Mike --001a114145368bed55051da197cb Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On T= ue, Aug 18, 2015 at 11:46 AM, Orion Poplawski <orion@cora.nwra.com&g= t; wrote:
Package: x2goserver
Version: 4.0.1.19

First issue is that ~/.xsession-x2go-errors is always appended to so it gro= ws
forever.=C2=A0 It should at least get rotated to .old file.

I wholeheartedly agree. Plus there are weird instances= where a command will make it grow to GB in size quickly.

In general, I believe in following what the local X.org server sess= ions do. However, since I am often debugging issues with why apps are not w= orking properly with X2Go, I would rather rotate than delete.

Second is with shared NFS home directories, multiple X2Go sessions get logg= ed
to the same file which is confusing.=C2=A0 I would suggest putting the host= name
into the log file name.

I wholeheartedly ag= ree. Gluster (for HA home dirs) is affected too.

-= Mike
--001a114145368bed55051da197cb--