Path: ...!weretis.net!feeder8.news.weretis.net!eternal-september.org!feeder3.eternal-september.org!news.eternal-september.org!.POSTED!not-for-mail From: Lawrence D'Oliveiro Newsgroups: comp.os.linux.advocacy Subject: Re: Building Linux in /dev/shm Date: Mon, 22 Apr 2024 07:38:16 -0000 (UTC) Organization: A noiseless patient Spider Lines: 17 Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Injection-Date: Mon, 22 Apr 2024 09:38:16 +0200 (CEST) Injection-Info: dont-email.me; posting-host="a50b2468e31bf3266ea857d988e1469f"; logging-data="888963"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX19mEUOyXLfsaBvaxY5Hg9fv" User-Agent: Pan/0.155 (Kherson; fc5a80b8) Cancel-Lock: sha1:6EBqwQx0P6vWTe2FlbApCRYPZH0= Bytes: 1828 On Mon, 22 Apr 2024 02:03:57 -0000 (UTC), vallor wrote: > ssh-agent's socket lives in a subdirectory in /tmp. Really should live > in /run somewhere. Looks like it can be steered by changing the TMPDIR > environment variable... The logical place for per-user stuff would be /run/user/«userid», as per systemd conventions. > On our companies user-access shell server, each user has their own /tmp > in their own chroot. I once had to set up a file-access server for a client that had to support both old-style insecure FTP and also SFTP (with the ultimate aim, of course, of transitioning all their customers from the former to the latter). Setting up a per-user chroot that would work with both was ... quite a challenge ...