when /tmp full ......

[Ridzuan Zakaria]

Hi,

Can some please explain to me why the following script behave differently when /tmp is full

Script 1:
#!/bin/ksh

sqlplus -s / @test.sql


Script 2:
#!/bin/ksh

sqlplus -s /nolog <connect /
@test.sql
exit;
Eof

Script1 run successfully but the script2 terminated with the following message:
msgcnt 152 vxfs: mesg 001: vx_nospace - /dev/vg00/lvol4 file system full (1 blo)

Why Script2 to need /tmp and script1 doesn't?

Thanks in advance.
ridzuan

[SS_6]

Some time scripts need to create temporary files during processing /tmp needs to have sufficient space. Not only scripts bu compress or swinstall sometime need space in /tmp but you would not find these files because the programe deletes them once the job is finished.

[Jeff Schussele]

Hi Ridzuan,

Becaused it's coded poorly.
/tmp is the OS domain, /var/tmp is for apps.
Anything other than the OS using /tmp is out of bounds.
Check your scripts & TMP / TMPDIR - they should be /var/tmp - *not* /tmp.

My 2 cents,
Jeff

[Ridzuan Zakaria]

Hi Jeff,

That why I puzzled me, my TMP and TMPDIR point to /local/lfs2/tmp. Only when I use script2 syntax it trying to access /tmp.

Is <
Any ideas?

Thanks.

[James A. Donovan · Accepted solution]

"Here" documents, (i.e. anything of the form <<[-]word) allocate space from /tmp in the form of files (like 99.sh or 338.sh, etc.)

The manpage for ksh describes their usage.