03-30-2008
You could add a df /tmp to the script to see that there is enough space for your file. If it's a RAM disk then it's quite possible that you simply run out of space.
Do you have support for compressed file systems? On Linux there's squashfs and a few others but I don't know about Solaris.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hello,
does anyone have a script that can check the contents of the /tmp directory and for example e-mail the directory content if anything other than session files are present?
Maybe there are better ways to monitor suspicous /tmp and /var/tmp activity, if so I'm listening :) (1 Reply)
Discussion started by: jamesbond
1 Replies
2. Shell Programming and Scripting
Hi,
I am encountring this problem from some time now...
ksh creates temp files /tmp/sh$$.* .
Sometimes if some of my shell script crashes or I kill it... these temp
files remain in the /tmp directory.
At some later time when some script gets the same PID it tries to
create files in the... (5 Replies)
Discussion started by: amitkr
5 Replies
3. Solaris
I have a Solris 9 box my problem is when I restart my box all my files and dirs in /tmp dir will be deleted exept 2 directories I found them since installation phase !!!!
How to keep my files at that dir " /tmp " even after restarting ??? (1 Reply)
Discussion started by: DarkSoul
1 Replies
4. AIX
Trying to setup user to have the ability to delete any files (regardless of owner) in /tmp.
I've tried almost everything... the permission on the folder is drwxrwxrwt 10 bin bin, and at one point I give all the possible permission (short of root) I can give to the user, and he still can't delete... (2 Replies)
Discussion started by: cchiang12
2 Replies
5. Solaris
Hi all,
I would like to know how to save files in /tmp...
I was interested in knowing this because when ever i booted into solaris there would already be a few files present in /tmp.however any file that is freshly stored in would be lost on reboot...
can anyone answer this pls!! (3 Replies)
Discussion started by: wrapster
3 Replies
6. AIX
How do I find what is creating these bunch of zero byte files under /tmp directory every few minutes.
AIX - 5.3 TL05
# ls -l /tmp
-rw-r--r-- 1 root system 0 Nov 05 16:54 n83n7a
-rw-r--r-- 1 root system 0 Nov 05 16:54 ZO3S7a
-rw-r--r-- 1 root system ... (3 Replies)
Discussion started by: mbak
3 Replies
7. UNIX for Dummies Questions & Answers
what is proper syntax to ls all files under /tmp/*, and wc -c ? (4 Replies)
Discussion started by: tjmannonline
4 Replies
8. AIX
I have a lot of files with the following names in /etc
/tmp/<num>.mktcpip
like
/tmp/934030.mktcpip
Anyone knows which process creates these files? (1 Reply)
Discussion started by: petervg
1 Replies
9. UNIX for Dummies Questions & Answers
Hey Guys,
I am facing an annoying scenario, fewer times when I execute the sort command, it throws out on error saying that "No Space on available on /var/tmp/<temp file name>. May be it is set to /var/tmp directory. I was wondering, if I cant redirect the temporary file creation to any other... (3 Replies)
Discussion started by: abhisheksunkari
3 Replies
10. Red Hat
I wanted to know whether all files under /tmp can be safely removed. I guess that /tmp may also have temporary files for applications currently being worked on, so at the most those applications may just shut down.
I hope that my question is clear whether all files under /tmp can be safely... (5 Replies)
Discussion started by: RHCE
5 Replies
RAM(4) Kernel Interfaces Manual RAM(4)
NAME
ram - ram disk driver
SYNOPSIS
/sys/conf/SYSTEM:
NRAM ram_size # RAM disk size (512-byte blocks)
major device number(s):
block: 3
minor device encoding:
must be zero (0)
DESCRIPTION
The ram pseudo-device provides a very fast extended memory store. It's use is intended for file systems like /tmp and applications which
need to access a reasonably large amount of data quickly.
The amount of memory dedicated to the ram device is controlled by the NRAM definition in units of 512-byte blocks. This is also patchable
in the system binary through the variable ram_size (though a patched system would have to be rebooted before any change took effect; see
adb(1)). This makes it easy to test the effects of different ram disk sizes on system performance. It's important to note that any space
given to the ram device is permanently allocated at system boot time. Dedicating too much memory can adversely affect system performance
by forcing the system to swap heavily as in a memory poor environment.
The block file accesses the ram disk via the system's buffering mechanism through a buffer sharing arrangement with the buffer cache. It
may be read and written without regard to physical disk records. There is no `raw' interface since no speed advantage is gained by such an
interface with the ram disk.
DISK SUPPORT
The ram driver does not support pseudo-disks (partitions). The special files refer to the entire `drive' as a single sequentially
addressed file.
A typical use for the ram disk would be to mount /tmp on it. Note that if this arrangement is recorded in /etc/fstab then /etc/rc will
have to be modified slightly to do a mkfs(8) on the ram disk before the standard file system checks are done.
FILES
/dev/ram block file
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
hk(4), ra(4), rl(4), rk(4), rp(4), rx(4), si(4), xp(4) dtab(5), autoconfig(8)
DIAGNOSTICS
ram: no space. There is not enough memory to allocate the space needed by the ram disk. The ram disk is disabled. Any attempts to access
it will return an error.
ram: not allocated. No memory was allocated to the ram disk and an attempt was made to open it. Either not enough memory was available at
boot time or the kernel variable ram_size was set to zero.
BUGS
The ram driver is only available under 2.11BSD.
3rd Berkeley Distribution Januray 27, 1996 RAM(4)