topic Re: File sdlogs in Operating System - HP-UX

File sdlogs

Samuel Alfonzo — Mon, 04 Nov 2002 14:40:51 GMT

Hi,
I have a file in the directory / , It's called sdlogs and It has the folowing permissions:

lrwxrwxrwx 1 root root 20 Nov 1 12:07 sdlogs

I tried eliminate it, with : rm, rm -f, rm -Rf, unlink; but I don't have success, because It's returning me Device Busy.

Can you help me with this?????
Thanks

Re: File sdlogs

John Poff — Mon, 04 Nov 2002 14:39:23 GMT

Hi,

The 'l' in the first position indicates that you are looking at a symlink. Probably the file that it is symlinked to is held open by another process. Try 'fuser sdlogs' and you can see the processes that are holding it open, and then you can do 'ps -fp ' for them to see what they are.

What does a full 'ls -l sdlogs' look like? That should show you the symlink.

JP

Re: File sdlogs

Robin Wakefield — Mon, 04 Nov 2002 14:45:28 GMT

Hi,

I would guess this is a symlink someone/something has created to the Software Distributor log area. Can you show what the link is pointing to?

Rgds, Robin

Re: File sdlogs

Samuel Alfonzo — Mon, 04 Nov 2002 15:18:27 GMT

I tried to do 'fuser sdlogs' and It returned me
'sdlogs: stat: Permission denied
fuser: could not find or access file sdlogs'

It's very estrange, because the symbol link don't appear.

Regards

Re: File sdlogs

John Poff — Mon, 04 Nov 2002 15:25:32 GMT

Are you running the 'fuser' command as root?

JP

Re: File sdlogs

Samuel Alfonzo — Mon, 04 Nov 2002 15:49:58 GMT

yeah, all the command was executed with root.

Re: File sdlogs

John Poff — Mon, 04 Nov 2002 16:06:52 GMT

You could try an 'ls -li sdlogs' and get the inode number for that file. Then, try 'find / -xdev -inum ####' where the #### is the inode number from the 'ls -li' command. Since the stat command failed during the 'fuser' command, I suspect that the inode for this file may be hosed up.

It might be time for an 'fsck' on the / filesystem, which is pretty tough to do when the system is running. You could reboot the system and get the 'fsck' on / for free. Some of the other real wizards here might have a better idea for getting the filesystem checked. I hate doing reboots just to fix strange problems, but this might be one of those problems where it is justified.

JP