16024 2008-06-14 17:58:06 +0400 chroot should clear TMPDIR environment variable 2021-05-13 12:24:28 +0300 1 1 4 Development Sisyphus coreutils unstable all Linux CLOSED FIXED https://bugzilla.altlinux.org/show_bug.cgi?id=40041 P2 normal --- 1 mike placeholder glebfm ldv placeholder vt qa-sisyphus oldest_to_newest 72352 0 mike 2008-06-14 17:58:06 +0400 While performing rescue jobs in a chroot (changing rootfs type): # mkinitrd --help /sbin/mkinitrd: line 1557: cannot create temp file for here document: No such file or directory # set | grep T.*MP TMP=/tmp/.private/root TMPDIR=/tmp/.private/root # ls /tmp/.private/root ls: cannot access /tmp/.private/root: No such file or directory Indeed. 72354 1 ldv 2008-06-14 18:07:42 +0400 (In reply to comment #0) > While performing rescue jobs in a chroot (changing rootfs type): This is not a regular operation, right? > # mkinitrd --help > /sbin/mkinitrd: line 1557: cannot create temp file for here document: No such file or directory > > # set | grep T.*MP > TMP=/tmp/.private/root > TMPDIR=/tmp/.private/root > # ls /tmp/.private/root > ls: cannot access /tmp/.private/root: No such file or directory > > Indeed. There are many ways to fool yourself. Try "env TMPDIR= chroot" next time. 72370 2 mike 2008-06-14 22:33:20 +0400 (In reply to comment #1) > > While performing rescue jobs in a chroot (changing rootfs type): > This is not a regular operation, right? It is one of operations when: - the stress is usually above usual; - weird diagnostics don't really help. > > # mkinitrd --help > > /sbin/mkinitrd: line 1557: cannot create temp file for here document: No such file or directory > > ls: cannot access /tmp/.private/root: No such file or directory > There are many ways to fool yourself. > Try "env TMPDIR= chroot" next time. I'll sure forget it 'till next time. Rather wanted to draw your attention to the fact that corner cases like this do matter; is it unreasonable to request that directory existence[/writability] check be performed before setting TMP/TMPDIR? 72375 3 ldv 2008-06-14 23:36:11 +0400 Lets handle this issue in chroot(1). 72382 4 mike 2008-06-15 12:05:21 +0400 Thanks in advance! 76626 5 ldv 2008-08-30 03:26:54 +0400 6.11-alt1-2-gc4aa447 76735 6 mike 2008-09-01 01:02:56 +0400 Your advance has arrived :-)