Hard to get rid of two files
in [Shell]
|
Prev: Find error
Next: Drop '$' with sed
From: John W. Krahn on 23 Jun 2008 15:16 Doug Freyburger wrote: > comph...(a)toddh.net (Todd H.) wrote: >> "John W. Krahn" <some...(a)example.com> writes: >> >>> I've got a couple of files in lost+found that were left there after an >>> fsck operation: >>> -rwS--s-wT 1 1418 36752 92966795 1972-12-11 16:06 #48581751 >>> --wSr--rw- 1 1418 34988 92965031 1972-12-11 15:37 #48582225 >> What the heck is the T file mode in this context? > > And note the setuid bit on both and the setgid bit on one. > >> I assume it's something to do with a sticky bit, but its impact I'm >> not sure? > > So they are both compiled binary programs. It's an important > hint I think. The sticky bit hasn't meant much for programs > for a long time (keep the pages of PIC code in swap space then > jump to it and page it in the next time it's used) but it's yet > another clue that they are programs. > >> Root should be able to wack these. Otherwise, you can create userid >> that have those UID's and use that user to try to delete them with >> those users. But root should be able to wack anything...shouldn't it? > > The times I've gotten "operation not permitted" was when I > tried to delete programs currently running in backgroup. > Consider the HPUX method of moving the image to a new > name and write a post-script to deelte them. > >> What file system is in use by the external drive? > > My questions is - What programs are running in background > off of a USB stick? Why was fsck run on a stick with > running programs? It's not a "stick", it's an external 400 GB hard drive. John -- Perl isn't a toolbox, but a small machine shop where you can special-order certain sorts of tools at low cost and in short order. -- Larry Wall
From: Marcel Bruinsma on 24 Jun 2008 04:56 In article <FKQ7k.851$yg7.269(a)edtnps82>, John W. Krahn wrote: > I've got a couple of files in lost+found that were left there after an > fsck operation: > > -rwS--s-wT 1 1418 36752 92966795 1972-12-11 16:06 #48581751 > --wSr--rw- 1 1418 34988 92965031 1972-12-11 15:37 #48582225 > > I've tried "rm -f" and chmod but I keep getting an "Operation not > permitted" message. Perhaps those files have the 'immutable' attribute set? If so, use chflags or chattr (or whatever the appropriate utility is named on your system) to clear that, and possibly any other special attributes, first. Most likely, you need to change to single-user mode (e.g. runlevel S) before you are allowed to clear the immutable attribute. Regards, Marcel
From: Joachim Schmitz on 24 Jun 2008 05:37 Todd H. wrote: > "John W. Krahn" <someone(a)example.com> writes: > >> I've got a couple of files in lost+found that were left there after >> an fsck operation: >> >> -rwS--s-wT 1 1418 36752 92966795 1972-12-11 16:06 #48581751 >> --wSr--rw- 1 1418 34988 92965031 1972-12-11 15:37 #48582225 > > What the heck is the T file mode in this context? > > I assume it's something to do with a sticky bit, but its impact I'm > not sure? sticky (AKA 'save text' bit set, exeute but unset -> uppercase S in ls-output The equiv is true for SUID/SGIN and uppercase S As far as I'm aware the sticky bit doesn't have any special meaning for anything other than a directory Bye, Jojo
From: John W. Krahn on 24 Jun 2008 09:58
Marcel Bruinsma wrote: > In article <FKQ7k.851$yg7.269(a)edtnps82>, > John W. Krahn wrote: > >> I've got a couple of files in lost+found that were left there after an >> fsck operation: >> >> -rwS--s-wT 1 1418 36752 92966795 1972-12-11 16:06 #48581751 >> --wSr--rw- 1 1418 34988 92965031 1972-12-11 15:37 #48582225 >> >> I've tried "rm -f" and chmod but I keep getting an "Operation not >> permitted" message. > > Perhaps those files have the 'immutable' attribute set? > > If so, use chflags or chattr (or whatever the appropriate utility is > named on your system) to clear that, and possibly any other > special attributes, first. Most likely, you need to change to > single-user mode (e.g. runlevel S) before you are allowed to > clear the immutable attribute. Yes, thanks for the reply but Stéphane already pointed that out yesterday. :-) John -- Perl isn't a toolbox, but a small machine shop where you can special-order certain sorts of tools at low cost and in short order. -- Larry Wall |