Kirk, Thanks for that. IBM also recommends using skulker. If I were more adept in writing scripts, I'd take the current skulker script and modify it to include a few of the useful commands you noted in your item #3. For example, skulker only looks at last access date, but not whether or not a process is still using the file, and will delete the entry anyway(I realize the process still has the inode allocated until it goes away). But why not include logic to do a "fuser -u file"? Even then many processes write .pid file that may be needed later.
In my case, for /tmp, I am going to continue to use a TFS, because it does start fresh and empty with every IPL, and at our shop that’s about once every 6 months. For the couple of my DB2 users that had trouble with space in /tmp using IDAA tool, I have created a .profile in their home directory, and added TMPDIR= specification that should redirect their /tmp usage to a different location. And lastly I am going to up the size of my /tmp from 256M to 512M. At this time skulker just adds way too many issues to work around for the limited benefit at my shop. If I hadn't implemented the automatic offload facility of SYSLOGD, I'd have used skulker to cleanup historical data from it in /var/logs as that data I *know* is typical log data, and once a new day starts, the prior is no longer allocated or in use. Dave _________________________________________________________________ Dave Jousma Assistant Vice President, Mainframe Engineering [email protected] 1830 East Paris, Grand Rapids, MI 49546 MD RSCB2H p 616.653.8429 f 616.653.2717 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Kirk Wolf Sent: Monday, December 21, 2015 4:42 PM To: [email protected] Subject: Re: managing /tmp Here are some notes in the appendix of our quick-guide for setting up IBM Ported Tools OpenSSH that mention "Best practices" for managing /tmp space. Any ideas or suggestions for improvement are appreciated. http://dovetail.com/docs/pt-quick-inst/pto-inst-tmp.html Kirk Wolf Dovetailed Technologies http://dovetail.com On Mon, Dec 21, 2015 at 10:15 AM, Shmuel Metz (Seymour J.) < [email protected]> wrote: > In > < > 4ee2851a2279b94cb70cd69b174106090149665...@s1flokydce2kx01.dm0001.info > 53.com > >, > on 12/21/2015 > at 01:09 PM, "Jousma, David" <[email protected]> said: > > >Seems as though that tool wants to use /tmp space between copying > >data from DB2 filesystem to IDAA hardware. > > In what directory? > > >they claim there is no way to override what to use for temp space. > > Mount? > > -- > Shmuel (Seymour J.) Metz, SysProg and JOAT > ISO position; see <http://patriot.net/~shmuel/resume/brief.html> > We don't care. We don't have to care, we're Congress. > (S877: The Shut up and Eat Your spam act of 2003) > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send > email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN This e-mail transmission contains information that is confidential and may be privileged. It is intended only for the addressee(s) named above. If you receive this e-mail in error, please do not read, copy or disseminate it in any manner. If you are not the intended recipient, any disclosure, copying, distribution or use of the contents of this information is prohibited. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please erase it from your computer system. Your assistance in correcting this error is appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
