<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Temportay file deletion in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053138#M600477</link>
    <description>Does your question translate to,&lt;BR /&gt;is anything necessary to be recovered that used to be in a lost /tmp filesystem?&lt;BR /&gt;Maybe this will answer it a little.&lt;BR /&gt;On Solaris boxes the /tmp filesystem is merely part of swap,&lt;BR /&gt;which means that you get an autoclaen of its content whenever you reboot.&lt;BR /&gt;</description>
    <pubDate>Fri, 10 Aug 2007 06:48:29 GMT</pubDate>
    <dc:creator>Ralph Grothe</dc:creator>
    <dc:date>2007-08-10T06:48:29Z</dc:date>
    <item>
      <title>Temportay file deletion</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053136#M600475</link>
      <description>what type of file can we delete if the /tmp get breached.</description>
      <pubDate>Fri, 10 Aug 2007 06:41:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053136#M600475</guid>
      <dc:creator>Pintu Bhagat</dc:creator>
      <dc:date>2007-08-10T06:41:17Z</dc:date>
    </item>
    <item>
      <title>Re: Temportay file deletion</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053137#M600476</link>
      <description>The nature of the tmp directory is (or should be)that the files are temporary. In this instance, I always start by deleting anything over a week old:&lt;BR /&gt;&lt;BR /&gt;cd /tmp&lt;BR /&gt;find . -mtime +7 -exec rm {}\;&lt;BR /&gt;&lt;BR /&gt;If there's still a problem I look at the largest files:&lt;BR /&gt;&lt;BR /&gt;ll|sort -k5,5nr|pg&lt;BR /&gt;&lt;BR /&gt;Unless the file at the top is very new I would be inclined to get rid of it.&lt;BR /&gt;&lt;BR /&gt;Mark Syder (like the drink but spelt different)</description>
      <pubDate>Fri, 10 Aug 2007 06:46:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053137#M600476</guid>
      <dc:creator>MarkSyder</dc:creator>
      <dc:date>2007-08-10T06:46:07Z</dc:date>
    </item>
    <item>
      <title>Re: Temportay file deletion</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053138#M600477</link>
      <description>Does your question translate to,&lt;BR /&gt;is anything necessary to be recovered that used to be in a lost /tmp filesystem?&lt;BR /&gt;Maybe this will answer it a little.&lt;BR /&gt;On Solaris boxes the /tmp filesystem is merely part of swap,&lt;BR /&gt;which means that you get an autoclaen of its content whenever you reboot.&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Aug 2007 06:48:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053138#M600477</guid>
      <dc:creator>Ralph Grothe</dc:creator>
      <dc:date>2007-08-10T06:48:29Z</dc:date>
    </item>
    <item>
      <title>Re: Temportay file deletion</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053139#M600478</link>
      <description>It is /tmp so if the application are OK, you could remove everything.&lt;BR /&gt;&lt;BR /&gt;You can also clear the tmp dir automaticaly at every reboot by changing the paramater&lt;BR /&gt;&lt;BR /&gt;CLEAR_TMP in /etc/rc.config.d/clean_tmps</description>
      <pubDate>Fri, 10 Aug 2007 06:52:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053139#M600478</guid>
      <dc:creator>Luk Vandenbussche</dc:creator>
      <dc:date>2007-08-10T06:52:20Z</dc:date>
    </item>
    <item>
      <title>Re: Temportay file deletion</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053140#M600479</link>
      <description>Shalom,&lt;BR /&gt;&lt;BR /&gt;What find can be deleted depends on what is there and who owns it.&lt;BR /&gt;&lt;BR /&gt;The general purpose of the directory is temp files and the directory is normally read-write-execute for all users.&lt;BR /&gt;&lt;BR /&gt;What sometimes happens is congestion and applications not cleaning up after themselves.&lt;BR /&gt;&lt;BR /&gt;Normally I handle it with a cron job that gets rid of files not accessed in the last 7 days.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Fri, 10 Aug 2007 06:53:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053140#M600479</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2007-08-10T06:53:46Z</dc:date>
    </item>
    <item>
      <title>Re: Temportay file deletion</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053141#M600480</link>
      <description>Managing /tmp and /var/tmp&lt;BR /&gt;-----------------------------------------&lt;BR /&gt;&lt;BR /&gt;/tmp is one of those directories where everyone has access but few seem to&lt;BR /&gt;treat it with respect. /tmp is defined as a temporary storage area and is&lt;BR /&gt;not to be considered permanent. Processes like email or the vi editor use&lt;BR /&gt;the /tmp directory for files, but normal operations will cleanup afterwards&lt;BR /&gt;and not leave files in the /tmp directory. Some HP programs will leave&lt;BR /&gt;their logfile in /tmp, but this is considered correct practice in&lt;BR /&gt;that the logfile should be reviewed for errors, and then removed or archived.&lt;BR /&gt;&lt;BR /&gt;There is a caveat that customers who are running Omniback should be&lt;BR /&gt;aware of. Omniback require that a file called CRS.pid exist in the /tmp&lt;BR /&gt;directory. Otherwise Omniback will not work.&lt;BR /&gt;&lt;BR /&gt;One way to enforce cleanup of the /tmp directory is to use a command such as:&lt;BR /&gt;&lt;BR /&gt;find /tmp -type f -atime +14 -exec rm {} \;&lt;BR /&gt;&lt;BR /&gt;which will remove any files in /tmp (or files in directories below /tmp)&lt;BR /&gt;that have not been accessed in more than 14 days. The other temporary&lt;BR /&gt;storage area, /var/tmp, is less often abused by users since they overlook&lt;BR /&gt;it's existence. Again, some processes will create temporary files in&lt;BR /&gt;/var/tmp and should (if they terminate correctly) remove their files&lt;BR /&gt;and editors like vi use /var/preserve. This command&lt;BR /&gt;will clear up /var/tmp of files not accessed in more than 7 days:&lt;BR /&gt;&lt;BR /&gt;find /var/tmp -atime +7 -exec rm {} \;&lt;BR /&gt;&lt;BR /&gt;System administrators need to decide if /tmp should allow regularly accessed&lt;BR /&gt;files to stay in /tmp. A user might bypass the above tests by using the&lt;BR /&gt;touch command on the files. In this caase, change the -atime option to&lt;BR /&gt;-mtime which means that the file must be modified.&lt;BR /&gt;&lt;BR /&gt;Once in a while, you may need to check for old directories which are not&lt;BR /&gt;removed by the above command. The contents will be cleared but after a&lt;BR /&gt;while, /tmp may get cluttered with empty directories.&lt;BR /&gt;&lt;BR /&gt;Here's a possibility for files in directories. This combination purges&lt;BR /&gt;files that are older than 7 days, followed by a removal of the directory&lt;BR /&gt;if it hasn't been updated for 7 days. However, a simple rmdir is used&lt;BR /&gt;so the command will fail if the directory isn't empty. Thus, until all&lt;BR /&gt;files have been removed, the directory will stay.&lt;BR /&gt;&lt;BR /&gt;find /tmp -type f -atime +7 -print -exec rm -f {} \;&lt;BR /&gt;find /tmp -type d -atime +7 -print -exec rmdir {} \;&lt;BR /&gt;find /var/tmp -type f -atime +7 -print -exec rm -f {} \;&lt;BR /&gt;find /var/tmp -type d -atime +7 -print -exec rmdir {} \;&lt;BR /&gt;&lt;BR /&gt;Another common practice is to cleanup /var/tmp after every full backup.&lt;BR /&gt;</description>
      <pubDate>Fri, 10 Aug 2007 07:01:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053141#M600480</guid>
      <dc:creator>AwadheshPandey</dc:creator>
      <dc:date>2007-08-10T07:01:17Z</dc:date>
    </item>
    <item>
      <title>Re: Temportay file deletion</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053142#M600481</link>
      <description>Hi:&lt;BR /&gt;&lt;BR /&gt;Everything depends on your management scheme.  As noted, you can elect to automatically remove everything in the '/tmp' directory during reboot and startup, by setting CLEAR_TMP=1 in '/etc/rc.config.d/clean_tmps'.&lt;BR /&gt;&lt;BR /&gt;Strictly speaking, according to standards [see the 'hier(5)' manpages], the '/tmp' directory is for *system* temporary files whereas '/var/tmp' is intended for *application* files.&lt;BR /&gt;&lt;BR /&gt;My preference is not to automatically clean the '/tmp' directory, but periodically purge (manually and programatically) what I don't want.  I don't want '/tmp' automatically cleaned upon reboot in order to preserve patch depots and/or individual patches that I may have staged there for installation following a reboot "health-check" prior to installation.&lt;BR /&gt;&lt;BR /&gt;Regards!&lt;BR /&gt;&lt;BR /&gt;...JRF...</description>
      <pubDate>Fri, 10 Aug 2007 07:08:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/temportay-file-deletion/m-p/4053142#M600481</guid>
      <dc:creator>James R. Ferguson</dc:creator>
      <dc:date>2007-08-10T07:08:03Z</dc:date>
    </item>
  </channel>
</rss>

