The /tmp-symlink problem made me switch from symlinking to another way of doing
the same configuration: mount the real location at /tmp/ with --bind. A line
like this in fstab does this:
/var/TMP /tmp auto auto,bind 0 0

The /tmp-symlink problem made me switch from symlinking to another way of doing
the same configuration: mount the real location at /tmp/ with --bind. A line
like this in fstab does this:
/var/TMP /tmp auto auto,bind 0 0

Thanks, it\'s overall cleaner (but won\'t work on Linux 2.2 which is in wide
use).
Probably worth adding if not to the email sent along with this
\&quot;problem\&quot; then to documentation?
edited on: 13-12 18:14

Thanks, it\'s overall cleaner (but won\'t work on Linux 2.2 which is in wide
use).
Probably worth adding if not to the email sent along with this
\&quot;problem\&quot; then to documentation?
edited on: 13-12 18:14

1: ok (but then add the --bind recipe to doc?
OTOH: if /tmp itself is a symlink then either we\'ve got bigger problems or it\'s _normal_.
2: complains regarding \&quot;inappropriate data type\&quot; or smth along that, can\'t quote the message as it\'s (sleepily) deleted. The file in question was 7G sized but that should be *perfectly* ok.
edited on: 15-12 19:46

1: ok (but then add the --bind recipe to doc?
OTOH: if /tmp itself is a symlink then either we\'ve got bigger problems or it\'s _normal_.
2: complains regarding \&quot;inappropriate data type\&quot; or smth along that, can\'t quote the message as it\'s (sleepily) deleted. The file in question was 7G sized but that should be *perfectly* ok.
edited on: 15-12 19:46