Re: listener and /tmp

Restrict your /tmp from using all the swap by setting the mount option for /tmp in your /etc/vfstab to something less than your swap size.

For example, if you have 2GB of swap, make a backup of your /etc/vfstab and then add the entry

size=200m

to the options column of the /tmp line. This will restrict your /tmp from using more than 200M of space on your swap.

Regards,

-Lou

"I.A. Saez" <i.a.saez.scheihingGEENSPAM_at_tue.nl> wrote:

>Vsevolod,
>
>/tmp and swap space are (always?) the same. Take a look at /var/adm/messages.
>There you probably will find errors like this:
>
>Nov 11 11:04:09 xxx.domain.nl unix: WARNING: Sorry, no swap space to grow stack
>for pid 26166 (httpd)
>Nov 11 11:04:10 xxx.domain.nl last message repeated 6 times
>
>It's not a good idea to just start changing permissions. Let your system
>administrator deal with the problem.
>
>kind regards,
>
>Ivan
>
>Vsevolod Afanassiev wrote:
>
>> I found that if /tmp is full, Oracle listener cannot start
>> a new process. At the same time, if I change permissions on /tmp
>> so UNIX user "oracle" cannot read/write/cd /tmp, the listener works OK.
>> Isn't it strange? I mean, if the listener needs to create a
>> temporary file in /tmp when establishing a connection, then persmissions
>> should affect it in the same way as /tmp being full.
>>
>> Environment:
>> Sun Solaris 8, Oracle 8.1.6.2.0
>>
>> Is there any way to tell listener not to use /tmp and use another directory?
>> I tried setting env. variables TMP and TMPDIR, but it did not help.
>>
>> Thanks,
>> Sev
>
Received on Thu Nov 14 2002 - 02:49:44 CST