Hi Parv,
It looks like another directory structure has appeared
in the ftp directory that Lynx does not see and that
find . -inum inode -delete
does not delete. It does have a dot as the first character,
with some other non-printing characters, but no /. I
haven't yet tried to delete it
in message [EMAIL PROTECTED],
wrote Walter thusly...
It looks like another directory structure has appeared in the ftp
directory that Lynx does not see and that
find . -inum inode -delete
does not delete. It does have a dot as the first character, with
some other non-printing characters,
in message [EMAIL PROTECTED],
wrote Walter thusly...
I apologize for the late reply.
Parv wrote:
# find . \( -inum inode-1 -o -inum inode-2 \) -print0 \
# | xargs -0 rm -rfv
Thanks, but when I did:
ls -i
and then typed in the inode in the command (saved in an old List
e-mail):
On Mon, Mar 15, 2004 at 07:07:46PM -0800, Chris Pressey wrote:
That wouldn't explain why 'rm -i *' returned 'no match', though.
Just to eliminate the obvious: did these weird filenames begin with a
'.'? Shell globbing treats file names with a leading period
specially. You'ld have to do:
%
Chris Pressey wrote:
Walter, out of curiousity, what FTP server were you running, and (if you
remember) what was the exact output of ls -aB ?
I'm running, at the moment, the default ftpd in FBSD 4.6.2.
(Yeah, I know, it's way old.)
I don't remember the exact output, but contained mostly odd
Parv wrote:
in message [EMAIL PROTECTED],
wrote Parv thusly...
# find . \( -inum inode-1 -o -inum inode-2 \) -print0 \
# | xargs -0 rm -fv
Oh, don't forget the '-r', for recursion, option for rm(1) as i did.
Use this instead...
# find . \( -inum inode-1 -o -inum inode-2 \) -print0 \
#
Matthew Seaman wrote:
On Mon, Mar 15, 2004 at 07:07:46PM -0800, Chris Pressey wrote:
That wouldn't explain why 'rm -i *' returned 'no match', though.
Just to eliminate the obvious: did these weird filenames begin with a
'.'? Shell globbing treats file names with a leading period
specially.
I've tried lynx, but it did not display the files.
I tried emacs, but I was only able to rename two of the
directories to other names I could delete; the other two gave
me an error of illegal character. I tried 'rm -i -- ?*' but
it didn't find the files. I tried 'find . -inum 146
On Mon, Mar 15, 2004 at 03:51:37PM -0800, Derrick Ryalls wrote:
I've tried lynx, but it did not display the files.
I tried emacs, but I was only able to rename two of the
directories to other names I could delete; the other two gave
me an error of illegal character. I tried 'rm -i --
Erik Trulsson wrote:
On Mon, Mar 15, 2004 at 03:51:37PM -0800, Derrick Ryalls wrote:
I've tried lynx, but it did not display the files.
I tried emacs, but I was only able to rename two of the
directories to other names I could delete; the other two gave
me an error of illegal character. I
and delete normally? (Sigh.)
Original Message
Subject: Re: deleting directories with ??? in name
Erik Trulsson wrote:
On Mon, Mar 15, 2004 at 03:51:37PM -0800, Derrick Ryalls wrote:
I've tried lynx, but it did not display the files.
I tried emacs, but I was only able to rename
Walter wrote:
I managed to delete the files by recreating the directory.
Ah, you have the hacker nature, then. That is
probably a Good Thing(TM) ... I was going to
suggest
$cp * ../otherdir/
$cd .. rmdir thatdir
$mv otherdir thatdir
:-)
Not to seem ungrateful, but isn't it a Bad Thing that it
Walter [EMAIL PROTECTED] writes:
I managed to delete the files by recreating the directory.
Not to seem ungrateful, but isn't it a Bad Thing that it
is not straightforeward to delete any file on the system
(as root, and thwarted merely because of the characters in
the name of the
On 15 Mar 2004 20:26:12 -0500
Lowell Gilbert [EMAIL PROTECTED] wrote:
Walter [EMAIL PROTECTED] writes:
I managed to delete the files by recreating the directory.
Not to seem ungrateful, but isn't it a Bad Thing that it
is not straightforeward to delete any file on the system
(as
On Mon, Mar 15, 2004, Chris Pressey wrote:
On 15 Mar 2004 20:26:12 -0500
Lowell Gilbert [EMAIL PROTECTED] wrote:
...
That wouldn't explain why 'rm -i *' returned 'no match', though.
I think it's more likely that (for whatever reason) the FTP server is
allowing files to be created with extremely
in message [EMAIL PROTECTED],
wrote Walter thusly...
Erik Trulsson wrote:
ls(1) by default displays all unprintable characters as question
marks. To see what the filenames actually are use 'ls -aB'.
To delete files with strange names you can always do a 'rm -i *'
and answer 'y' only
in message [EMAIL PROTECTED],
wrote Parv thusly...
# find . \( -inum inode-1 -o -inum inode-2 \) -print0 \
# | xargs -0 rm -fv
Oh, don't forget the '-r', for recursion, option for rm(1) as i did.
Use this instead...
# find . \( -inum inode-1 -o -inum inode-2 \) -print0 \
# | xargs
17 matches
Mail list logo
