[NTLUG:Discuss] Getting rid of a core with a link

[Russ]

On 9/10/05, Kevin Brannen <kbrannen at pwhome.com> wrote:
> Russ wrote:
> 
> >I'm seeking assistance with a situation that I don't understand.
> >
> >I've got a core file that was created when a power outage (no UPS)
> >occurred during an update of my Linux system.  Pardon my description
> >if it isn't clear.  I'd like to get rid of it because it's a 2.7 mB
> >file on a 8 mB hard drive.  It's owned by root and exists as link to
> >/proc/kcore.
> >
> >This the status of the core:
> >
> >lrwxrwxrwx 1 root root    11 2005-09-09 09:30 core -> /proc/kcore
> >
> >If the core was a discrete file I could get rid of it.  It was a
> >common problem on a Unix system we used at work.  For me the problem
> >is that it's a link.  I don't know the consequences of doing a removal
> >as I would for a file without a link and I'd rather not go through the
> >whole install/update of the distro if I don't have to.
> >
> >The Linux manuals I have don't tell me how to dispose of this,
> >including the books that are associated with the distro (Suse 9.1).  I
> >find instructions in my Unix books but I'm reticent to try those
> >procedures.
> >
> >Advice would be welcome.  Thanks in advance.
> >
> >
> 
> It's just a symlink.  As you can see, it only takes up 11 bytes (and 1
> inode if that means anything to you).  So my advice is not to worry
> about it.

Thanks for the reply.  You're correct in guessing.  The relevance of
11 didn't mean anything to me.  It will however.  I'll check it out
along with "symlink" and other terms.  This whole thing is a learning
experience.

> 
> That being said, you could remove it.  As root, do "rm ./core" when
> you're sitting in its dir.  HOWEVER, it may be a *bad* thing to remove
> that symlink!  You don't tell us where the file is, i.e. what dir it is
> in.  If it's /dev/core or /proc/core, leave it alone.  If it's /core,
> remove it.  

The properties of the file listed it as "memory crash dump".  However
it was in the /dev directory and linked to /proc/kcore.  A friend who
knows only a bit more than me told me that doing an unlink would be a
good first step.  All my attempts to find the core file have failed. 
I am unable to find it.  That worried me because it meant that either
it was virtual or it had hidden in some way.  I was searching in root
so I didn't thing that it was likely to be hidden.

>This is a case where context is everything. :-)  If you
> aren't sure, reply back to the list with the full path name to the
> symlink.  But I'd say you're safe just to ignore it.

So far I haven't detected anything malfunctioning.  Of course, I
haven't been back on the box for more than an hour.

I wonder what's involved in trying to get back to where it was.  By
that, I mean trying to create the link again.

> 
> BTW, do *not* attempt to remove /proc/kcore.  In fact, don't ever
> attempt to modify anything in /proc; look with "cat", but don't modify.

Thanks.  I appreciate the warning.

> 
> Kevin
> 
> _______________________________________________
> https://ntlug.org/mailman/listinfo/discuss
> 


-- 
Russ