/tmp file to delete?

[Betty Simonds]

The server is an rp3410 running Unix 11.11.
The /tmp folder is nearly full. I've cleared out what I know can be deleted, but have a file called hp11e134.SD that is dated Aug 20, 2004 that consumes much of the space. I researched and believe this was used to install Jet Direct, and can be deleted, but would like confirmation of that before deleting it. The other large file is called wd_action.dbg. This file is current. I would like to know what it's related to , if you know. It is quite large - can it be cleared out in some way? Or is it one of those files that can be deleted and will recreate itself? I've attached a text file with the first few lines of the file. The rest of the file repeats the last three lines in the attachment.

[Patrick Wallek · Accepted solution]

The hp11e134.SD can almost surely be deleted. The SD is indicative of a software depot file which is used for installation. Once software has been installed, you no longer need the SD file.

I don't know about the wd_action.dbg. It sounds as if some process is writing debug messages to this file. Do an 'fuser -u /tmp/wd_action.dbg' and see what user name and process id are returned, if anything. You can then do a 'ps -ef' and grep for the PID returned to see what process is using that file.

Good luck.

[Sandman!]

You can run lsof on this file to see which if any processes are using it. If none then you can safely delete it.

# lsof

cheers!

[Devender Khatana]

Hi,

It is not advised to delete the second file as it is current. As posted above through fuser and lsof you can find the process using this file. Restarting the process if possible will clear the file for you.

If the process can not be restarted then you can look forward for a reboot which inturn could also do that.

HTH,
Devender

[Andy Torres]

I recognize hp11e134.SD as the name of the JetDirect (hpnpd) product software depot. You can still download it from various sources and could move or delete it. I'd save it somewhere in case it's difficult to find.

After some crafty Google searches, the best I can come up with on the wd_action.dbg file is some sort of debug or log file from (possiby) a watchdog-type utility - maybe a montor of some sort, as described in the text file you uploaded. fuser or lsof are going to help you investigate the source process for that file.

If it's going to casue /tmp to fill up and possibly cause a larger problem for the system then I might take a chance and cat /dev/null to it. It's in /tmp, which is almost universally understood to be a TEMPORARY area, right? Err on the side of caution if you feel you have time, of course.

[Gavin Clarke]

This reply is probably a bit late now, I'm sorry I didn't see your post sooner.

As the others have said hp11e134.SD can go you can easily download it again if need be.

wd_action.dbg we've got that file too, it is a rather dull looking ascii file which has text in it like:

--->rw():reread: action = <0>
--->rw() : New action = <0>

I guess it might be better left alone, I think there must be a reason that it is there.