RE: Listener files/sockets in /tmp/.oracle
- From: "Matthew Zito" <mzito@xxxxxxxxxxx>
- To: "Allen, Brandon" <Brandon.Allen@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Thu, 12 Nov 2009 16:47:12 -0500
Ah, yes, that is a Silly Sysadmin command par excellence. A far better command
is:
find /tmp -atime +90 -exec rm -f {} \;
That will only blow away files that haven't been accessed in 90 days, which is
a far better metric, imho, than simply being 90 days old.
Thanks,
Matt
-----Original Message-----
From: Allen, Brandon [mailto:Brandon.Allen@xxxxxxxxxxx]
Sent: Thu 11/12/2009 4:46 PM
To: Matthew Zito; oracle-l@xxxxxxxxxxxxx
Subject: RE: Listener files/sockets in /tmp/.oracle
Thanks Matt for the good ideas - I'll look into them further. Yes, I'm
guessing she ran something like "find /tmp -mtime +90 | xargs rm" because she
mentioned that she only deleted files older than 90 days (which includes when
our listener was last started). I'm not sure off the top of my head if find
searches in hidden directories by default, but I'm guessing it does - either
that, or maybe she gave it a flag to force it to.
Also, just to clarify - removing the sockets didn't really "crash" my listener
as I said earlier - the listener was still up and responding to TCP requests,
it just stopped responding to IPC, which turned out to not be a big deal since
none of our applications connect through IPC anyway.
Thanks,
Brandon
________________________________
Privileged/Confidential Information may be contained in this message or
attachments hereto. Please advise immediately if you or your employer do not
consent to Internet email for messages of this kind. Opinions, conclusions and
other information in this message that do not relate to the official business
of this company shall be understood as neither given nor endorsed by it.
Other related posts:
