topic Re: big here documents fill /tmp in Operating System - HP-UX

big here documents fill /tmp

Duncan Galbraith — Wed, 25 Sep 2002 17:59:56 GMT

Hi,
I'm using a here doument to take a uuencoded file out of a script (ksh). The file is bigger than the free space in /tmp so I direct it into somewhere with lots of free space. This does not work as the shell creates a /tmp/shPID.# file, apparently before it starts to create the real output. To me this is not very sensible as it means that the entire contents of the here document are written to disk twice (at least they would be if you had enough space). Can anyone tell me how you stop the shell writing this to /tmp ?

Thanks in advance,

Duncan

Re: big here documents fill /tmp

James R. Ferguson — Wed, 25 Sep 2002 18:24:44 GMT

Hi Duncan:

You don't indicate your release, but recent cumulative Posix shell patches moved the location from /tmp to /var/tmp under the assumption that the later generally has a larger amount of free space.

For 11.0 see PHCO_26789

Regards!

...JRF...

Re: big here documents fill /tmp

Duncan Galbraith — Wed, 25 Sep 2002 20:52:39 GMT

Thanks James. Release is 11.0. Unfortunately I don't happen to have anything like enough disk space in /tmp or /var/tmp and would like to be able to set my own 'tmp' directory for the shell to write into (that is unless I can get the shell not to do what would appear to me to be an extra disk write). I've tried setting $TMPDIR but I think that only works for things like vi.
Any more suggestions ?

Thanks.

Re: big here documents fill /tmp

curt larson_1 — Wed, 25 Sep 2002 21:35:52 GMT

just a couple of quick suggestions:
check to see if the script itself is creating the /tmp/shPID.# file instead of the shell.

make sure the script with the here doc isn't in the /tmp directory.