Thanks Fred, but as I said, rm doesn't work - even with the -f switch and escaping the forward slash(es).
I don't think the C code will work - isn't that just what rm tries to do?


If I do a rm -f "/dev/log" it just ignores me.
If I do a rm -f -d "/dev/log" it ignores me.
If I go one level higher, and do the same on the directory holding the offending "files":
rm -f -d setiold it tells me it can't delete setiold as it's a directory. Yes I know it's a directory, that's why I said -d but it still ignores me.


I've tried rmdir, but that won't work either - it tells me the directory isn't empty. If I use the --ignore-fail-on-non-empty switch it ignores me.

The interesting part is that I've been able to mv the directory with the offending files all over the place, I just can't delete it or its contents.

HELP, please, someone - I can't start my domain's mail server until I get a clean boot!

julian.
============================
At 05:59 AM 6/29/03, you wrote:
On Sun, Jun 29, 2003 at 01:55:37AM -0500, Julian Opificius wrote:
> Help, please,
>
> As a result of an unclean shutdown, I have some rogue files on my 7.2
> installation, which are preventing a complete boot up.
>
> Somehow I have files called "/dev/log" and "/var/loc" in a director in
> /var/log.
> Yes, the files have the forward slashes in them, and the OS is all
> confused, thinking they're directories when they're really not. I can't
> delete them or rename them using rm, or rmdir. I've tried chattr, but that
> won't touch them either.
You should be able to do something like:
        rm -f "/var/log/dev\/log"
or even write a short C program similar to this (untested) code:
---------------- foo.c --------------
#include <stdio.h>
#include <unistd.h>
main (int argc, char ** argv)
        {
        if (argc == 2)
                {
                unlink (argv[1]);
                }
        return 0;
        }
-----------------------
compile it:
        cc -o foo foo.c
run it:
        ./foo "/var/log/dev\/log"
>
> During the boot process, the OS sees the unclean state, which causes fsck
> to run. Fsck fails to solve the problem, which causes the boot process to
> fail, dumping me into a diagnostic shell.
>
> I'm also getting Input/Output errors on a couple of pid files.
>
> Is there a utility I can use to clean this up?
>
> Many thanks.
>
> Julian.
>


--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list

Reply via email to