chattr: Operation not supported while reading flags on /tmp/.private/jeroen/ksocket-jeroen/klauncherT20158.slave-socket chattr: Operation not supported while reading flags on /tmp/.private/jeroen/keyring-bzRynb/socket.pkcs11 chattr: Operation not supported while reading flags on /tmp/.private/jeroen/keyring-bzRynb/ssh chattr: Operation not supported while reading flags on /tmp/.private/jeroen/keyring-bzRynb/socket chattr: Operation not supported while reading flags on /tmp/.private/jeroen/keyring-edAHWf/socket chattr: Operation not supported while reading flags on /tmp/.private/jeroen/demobrowser chattr: Operation not supported while reading flags on /tmp/.private/jeroen/Arora_1000_100 chattr: Operation not supported while reading flags on /tmp/.private/jeroen/druby8958.0 chattr: Operation not supported while reading flags on /tmp/.private/jer/seahorse-Lg4llt/S.gpg-agent chattr: Operation not supported while reading flags on /tmp/.private/jer/seahorse-BfJOHo/S.gpg-agent chattr: Operation not supported while reading flags on /tmp/.private/jer/seahorse-olqTFh/S.gpg-agent chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-19c4-0-32d5d60d222b6 chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-53ad-0-6e96a118cf50c chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-1f01-0-d4dab91839fd chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-3a1-0-42052b47cb1a chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-1f31-0-17521ab69534b chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-486b-0-b4dbc544e94c chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-5391-0-5ff6454dec270 chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-2d82-0-16eed3b45ab67 chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-64b2-0-4887b032ec530 chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-1f4a-0-477c1e4677294 chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-19e3-0-6d3df2469ad12 chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-4c39-0-6f1d97f8345d3 chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-1f3e-0-fd919cd8af2 chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-34c-0-292c30b1b91ea chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-6414-0-1180156ae0ca4 chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-198b-0-c546e4a9562c chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-53bc-0-32f193dff0c8a chattr: Operation not supported while reading flags on /tmp/.private/jer/orbit-jer/linc-53a6-0-5c1b71c677942 Maybe it's a good idea to send all that information to /dev/null, just in case some system doesn't support it? --- /etc/init.d/bootmisc.old 2010-11-22 12:56:02.000000000 +0100 +++ /etc/init.d/bootmisc 2010-11-24 15:42:56.000000000 +0100 @@ -39,7 +39,7 @@ # each user gets a private directory with immutable # bit set; remove the immutable bit before trying to # remove it. - [ -d /tmp/.private ] && chattr -R -a /tmp/.private + [ -d /tmp/.private ] && chattr -R -a /tmp/.private &>/dev/null find $startopts ! -name . \ ! -path "./lost+found" \
All, is it safe to redirect the output from chattr to /dev/null, or is there a better way to handle this? The chattr was introduced by commit 09bed967bf610ee9e52a7eab772fa6f9c7b3e00b, so should I revert this if there isn't a better way to handle the output? Thanks, William
Damn, I didn't consider the case where /tmp wouldn't have a working chattr. Feel free to 2>/dev/null, there should be nothing there worth looking at anyway.
Do you know if chattr also works on bsd systems, or should we test to make sure we are running on a linux system? Thanks, William
This is fixed in 0.6.6. Thanks for the report. William
