* On 01/24/2018 08:36 AM, Robert Dinse wrote:
> Yes, you gotta love systemd. There is an upside though, it's about
> two seconds between the time my BIOS fires off the boot block and I've got a
> desktop login screen, under the old start up system it was more like 30
> seconds.
... unless
site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874.
On Wed, 24 Jan 2018, Stefan Baur wrote:
Date: Wed, 24 Jan 2018 08:43:20 +0100
From: Stefan Baur <x2go-m...@baur-itcs.de>
To: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] can't connect to session
*ahem*
I am one of the list-
an <io...@ionic.de>
>> To: Andrew Munn <and...@nmedia.net>
>> Cc: x2go-user@lists.x2go.org
>> Subject: Re: [X2Go-User] can't connect to session
>>
>> * On 01/22/2018 10:28 PM, Andrew Munn wrote:
>>> Thanks!
>>> I've added the following lin
, 24 Jan 2018 07:36:24 +0100
From: Mihai Moldovan <io...@ionic.de>
To: Andrew Munn <and...@nmedia.net>
Cc: x2go-user@lists.x2go.org
Subject: Re: [X2Go-User] can't connect to session
* On 01/22/2018 10:28 PM, Andrew Munn wrote:
Thanks!
I've added the following line to /usr/lib/tmpfiles.d
* On 01/22/2018 10:28 PM, Andrew Munn wrote:
> Thanks!
> I've added the following line to /usr/lib/tmpfiles.d/tmp.conf
>
> x /tmp/.x2go-*
>
> Hopefully that fixes it.
Then again, according to
https://developers.redhat.com/blog/2016/09/20/managing-temporary-files-with-systemd-tmpfiles-on-rhel7/
Thanks!
I've added the following line to /usr/lib/tmpfiles.d/tmp.conf
x /tmp/.x2go-*
Hopefully that fixes it. Do you think there should be some automated
process to append that line during installation on a CentOS/RHEL system?
Andrew
On Mon, 22 Jan 2018, Mihai Moldovan wrote:
> * On
* On 01/16/2018 02:32 AM, Andrew Munn wrote:
> I get reasonable output from x2golistsessions_root. I also see a matching
> directory in /tmp/.x2go-$user/ containing 3 files:
>
> [root@hercules C-andrew-51-1513021653_stDMATE_dp24]# ls
> total 12
> -rw-rw-r-- 1 andrew andrew 1 Jan 10 08:56
Am 16.01.2018 um 02:32 schrieb Andrew Munn:
> I can delete the session files and then create a new one. Or I can click
> "new" instead of double-clicking on the session. Clicking "new" will
> create an additional session and when I disconnect/reconnect I now see 2
> sessions. One is status
I get reasonable output from x2golistsessions_root. I also see a matching
directory in /tmp/.x2go-$user/ containing 3 files:
[root@hercules C-andrew-51-1513021653_stDMATE_dp24]# ls
total 12
-rw-rw-r-- 1 andrew andrew 1 Jan 10 08:56 options
-rw-rw-r-- 1 andrew andrew 12 Jan 10 08:56 sshd.pid
* On 01/10/2018 04:13 PM, Andrew Munn wrote:
> I'm seeing this situation again. I can see the session in the client as
> usual by when I click on it nothing happens. I think someone in another
> thread mentioned running out of available ports as a possible cause. Is
> that right? What's the
I'm seeing this situation again. I can see the session in the client as
usual by when I click on it nothing happens. I think someone in another
thread mentioned running out of available ports as a possible cause. Is
that right? What's the solution here? I want to reconnect to the session
On Sun, 19 Nov 2017, Mihai Moldovan wrote:
> * On 11/19/2017 11:21 AM, Andrew Munn wrote:
> > Yes deleting /tmp/.x2go-$USER did fix it. It happens rarely. I'm not
> > sure how long the session runs before this occurs. A fix for this issue
> > would be great. Thanks for the suggestion!
>
>
* On 11/19/2017 11:21 AM, Andrew Munn wrote:
> Yes deleting /tmp/.x2go-$USER did fix it. It happens rarely. I'm not
> sure how long the session runs before this occurs. A fix for this issue
> would be great. Thanks for the suggestion!
Uh, no, my suggestion was *not* to delete this data, it
Yes deleting /tmp/.x2go-$USER did fix it. It happens rarely. I'm not
sure how long the session runs before this occurs. A fix for this issue
would be great. Thanks for the suggestion!
On Sat, 18 Nov 2017, Mihai Moldovan wrote:
> * On 11/18/2017 09:32 AM, Andrew Munn wrote:
> > Sometimes
* On 11/18/2017 09:32 AM, Andrew Munn wrote:
> Sometimes x2go works fine. Other times I can't get the session back and
> logs look like this. server version 4.0.1.20. Same results occur when
> connecting from my Windows or Linux client.
Might that be the same problem as described by the
Sometimes x2go works fine. Other times I can't get the session back and
logs look like this. server version 4.0.1.20. Same results occur when
connecting from my Windows or Linux client.
$ uname -a
Linux hercules 3.10.0-514.26.2.el7.x86_64 #1 SMP Tue Jul 4 15:04:05 UTC
2017 x86_64 x86_64
16 matches
Mail list logo
