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.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_- Eskimo North Linux Friendly Internet Access, Shell Accounts, and Hosting. Knowledgeable human assistance, not telephone trees or script readers. See our web site: http://www.eskimo.com/ (206) 812-0051 or (800) 246-6874. On Wed, 24 Jan 2018, Mihai Moldovan wrote:
Date: Wed, 24 Jan 2018 07:36:24 +0100 From: Mihai Moldovan <[email protected]> To: Andrew Munn <[email protected]> Cc: [email protected] 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/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/ and the general file system hierarchy, /usr/lib is not a good place to make changes. Thankfully you should be able to move this into /etc/tmpfiles.d/x2go.conf and have that setting persist between system updates.Do you think there should be some automated process to append that line during installation on a CentOS/RHEL system?Yes, I should add this file to the general packaging! It's impressive how many workarounds are necessary for systemd in order for it not to break everything... Mihai
_______________________________________________ x2go-user mailing list [email protected] https://lists.x2go.org/listinfo/x2go-user
