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 <[email protected]> schrieb am Sa., 1. Sep. 2018,
11:08:

> On Sat, 1 Sep 2018 10:03:06 +0200
> Ulrich Sibiller <[email protected]> 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/
>
_______________________________________________
x2go-user mailing list
[email protected]
https://lists.x2go.org/listinfo/x2go-user

Reply via email to