Hello list,
x2go-server writes each 2 seconds AFAICS four tmp files to /tmp/
-rw------- 1 root root 0 Sep 1 09:22 d_If2A_6JI -rw------- 1 root root 0 Sep 1 09:22 b21fnyFKys -rw------- 1 root root 0 Sep 1 09:22 FQVURek_gX -rw------- 1 root root 0 Sep 1 09:22 DMIsk9sy8n
Is it possible to move these tmp files to /tmp/whatever/ ?
The reason is that I use a tmpfs on /tmp/ but the stats of /tmp directorie are updated on an SSD disk which causes writes to the SSD.
R.
-- richard lucassen http://contact.xaq.nl/
On Sat, 1 Sep 2018 09:30:02 +0200 richard lucassen <mailinglists@lucassen.org> wrote:
The reason is that I use a tmpfs on /tmp/ but the stats of /tmp directorie are updated on an SSD disk which causes writes to the SSD.
s/writes/unnecessary writes/
-- richard lucassen http://contact.xaq.nl/
I don't think that there's any sense in writing 0 byte files regularly. Are you sure x2go causes them? Have you tried with a simple session that only runs an xterm?
Uli
richard lucassen <mailinglists@lucassen.org> schrieb am Sa., 1. Sep. 2018, 09:53:
On Sat, 1 Sep 2018 09:30:02 +0200 richard lucassen <mailinglists@lucassen.org> wrote:
The reason is that I use a tmpfs on /tmp/ but the stats of /tmp directorie are updated on an SSD disk which causes writes to the SSD.
s/writes/unnecessary writes/
-- richard lucassen http://contact.xaq.nl/
x2go-user mailing list x2go-user@lists.x2go.org https://lists.x2go.org/listinfo/x2go-user
On Sat, 1 Sep 2018 10:03:06 +0200 Ulrich Sibiller <ulrich.sibiller@gmail.com> wrote:
I don't think that there's any sense in writing 0 byte files regularly. Are you sure x2go causes them? Have you tried with a simple session that only runs an xterm?
This happens when x2goserver is running (no client connections):
root@x2go ~>stat /tmp/ File: /tmp/ Size: 580 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:02:57.435297157 +0200 Change: 2018-09-01 11:02:57.435297157 +0200 Birth: - root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:02:59.767272229 +0200 Change: 2018-09-01 11:02:59.767272229 +0200 Birth: - root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:03:02.095247355 +0200 Change: 2018-09-01 11:03:02.095247355 +0200 Birth: -
Then I stop x2goserver:
root@x2go ~>service x2goserver stop
root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:03:50.934725699 +0200 Change: 2018-09-01 11:03:50.934725699 +0200 Birth: - root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:03:50.934725699 +0200 Change: 2018-09-01 11:03:50.934725699 +0200 Birth: - root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:03:50.934725699 +0200 Change: 2018-09-01 11:03:50.934725699 +0200 Birth: -
It is definitely x2goserver...
R.
-- richard lucassen http://contact.xaq.nl/
Ok, interesting. Unfortunately I don't have an idea what might be causing that. Can you check with lsof who is touching the files?
@Mihai Can you say something about those files?
Uli
richard lucassen <mailinglists@lucassen.org> schrieb am Sa., 1. Sep. 2018, 11:08:
On Sat, 1 Sep 2018 10:03:06 +0200 Ulrich Sibiller <ulrich.sibiller@gmail.com> wrote:
I don't think that there's any sense in writing 0 byte files regularly. Are you sure x2go causes them? Have you tried with a simple session that only runs an xterm?
This happens when x2goserver is running (no client connections):
root@x2go ~>stat /tmp/ File: /tmp/ Size: 580 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:02:57.435297157 +0200 Change: 2018-09-01 11:02:57.435297157 +0200 Birth: - root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:02:59.767272229 +0200 Change: 2018-09-01 11:02:59.767272229 +0200 Birth: - root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:03:02.095247355 +0200 Change: 2018-09-01 11:03:02.095247355 +0200 Birth: -
Then I stop x2goserver:
root@x2go ~>service x2goserver stop
root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:03:50.934725699 +0200 Change: 2018-09-01 11:03:50.934725699 +0200 Birth: - root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:03:50.934725699 +0200 Change: 2018-09-01 11:03:50.934725699 +0200 Birth: - root@x2go ~>stat /tmp/ File: /tmp/ Size: 540 Blocks: 0 IO Block: 4096 directory Device: 1ah/26d Inode: 11133 Links: 12 Access: (1777/drwxrwxrwt) Uid: ( 0/ root) Gid: ( 0/ root) Access: 2018-09-01 09:22:41.174939529 +0200 Modify: 2018-09-01 11:03:50.934725699 +0200 Change: 2018-09-01 11:03:50.934725699 +0200 Birth: -
It is definitely x2goserver...
R.
-- richard lucassen http://contact.xaq.nl/
On Sat, 1 Sep 2018 11:13:01 +0200 Ulrich Sibiller <uli42@gmx.de> wrote:
Ok, interesting. Unfortunately I don't have an idea what might be causing that. Can you check with lsof who is touching the files?
These files only live a very short time. I noticed it when I wanted to send an attachment which was located in /tmp/ with the email client "Sylpheed". The popup in which the attachment directory is shown was constantly refreshing, showing these files (4 as far as I can see). Otherwise I wouldn't have noticed it.
R.
-- richard lucassen http://contact.xaq.nl/
On Sat, 1 Sep 2018 11:29:28 +0200 richard lucassen <mailinglists@lucassen.org> wrote:
Ok, interesting. Unfortunately I don't have an idea what might be causing that. Can you check with lsof who is touching the files?
These files only live a very short time. I noticed it when I wanted to send an attachment which was located in /tmp/ with the email client "Sylpheed". The popup in which the attachment directory is shown was constantly refreshing, showing these files (4 as far as I can see). Otherwise I wouldn't have noticed it.
I'm not sure, but I'd say this is something of the later versions of x2goserver. I've never seen it before until a week ago. I run Debian testing with x2goserver 4.1.0.2-2. But once again: I'm not sure, I might have sent attachments from other diretories than /tmp/
-- richard lucassen http://contact.xaq.nl/
On Sat, 1 Sep 2018 11:13:01 +0200 Ulrich Sibiller <uli42@gmx.de> wrote:
Ok, interesting. Unfortunately I don't have an idea what might be causing that. Can you check with lsof who is touching the files?
Run an strace on the pid of "/usr/bin/perl /usr/sbin/x2gocleansessions" and you'll see the tmp files creation.
-- richard lucassen http://contact.xaq.nl/
On Sat, 1 Sep 2018 17:26:36 +0200 richard lucassen <mailinglists@lucassen.org> wrote:
Ok, interesting. Unfortunately I don't have an idea what might be causing that. Can you check with lsof who is touching the files?
Run an strace on the pid of "/usr/bin/perl /usr/sbin/x2gocleansessions" and you'll see the tmp files creation.
Ok, I just simply killed the beast and the server still runs. I have no idea what exactly it is doing, but it makes quite a lot of noise IMHO, run "top" and you will see it regularly see it on top of the list.
If it's only made to look for stale sessions, maybe it can be run from cron once in a while?
-- richard lucassen http://contact.xaq.nl/
-
richard lucassen -
Ulrich Sibiller -
Ulrich Sibiller