stmpclean-0.1-alt2 would not handle at least two cases properly: - /tmp being a symlink to /var/tmp (quite common situation); - large (>2Gb) files (int32 is a bottleneck). It is annoying :-) --- --- alt2..alt3 changelog: * Wed Oct 30 2002 Dmitry V. Levin <<a href="mailto:ldv@altlinux.org>" target="_new">ldv@altlinux.org></a>; 0.1-alt3 - Rebuilt in new environment. Hence the above should hold true too.
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 \"problem\" then to documentation? edited on: 13-12 18:14
1. stmpclean won\'t follow symlinks, it\'s design feature. If you replaced /tmp directory with symlink, you also have to edit /etc/cron.daily/stmpclean. 2. What\'s wrong with large files? edited on: 15-12 00:33
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 \"inappropriate data type\" 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
LFS support fixed in stmpclean-0.1-alt4.
