11-25-2011
You mean all that SA would have done is to fire the rm command which did not work for me ?
I was not able to fire any command including df at the time of the issue.
Yes, the /tmp has some swap memory.
9 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Please solve the following
NOTICE HTFS:No space on dev hd(1/42) (2 Replies)
Discussion started by: msuheel
2 Replies
2. Linux
Hi all,
My disk space is 100% full.
df -k <dir> -> 100%
One of my debug files consume huge amount of space and i want to remove the same to start off fresh debugs.
However i'm unable to remove the file giving out the following error message:
rm -f debug.out22621
rm: cannot remove... (8 Replies)
Discussion started by: Pankajakshan
8 Replies
3. Linux
one of my servers / was full by 100% i cleard some space, now though i have
enough space on / partition still df is showing disk usage as 100% am not able to create any single txt file ? why so ? (3 Replies)
Discussion started by: bryanabhay
3 Replies
4. Solaris
Hi All,
My Solaris 8 firewall server is getting full on the / filesystem. I don't know which one should I delete. I think there's no more to delete on the file like logs or temp file.
Does someone knows about deleting a safe file (or folder) on FS like /usr, /opt, /platform, /kernel, /sbin?... (7 Replies)
Discussion started by: itik
7 Replies
5. UNIX for Dummies Questions & Answers
during installation i created four partitions mainly
/ 5GB
/home 1GB
/boot 100MB
swap 2GB
now since i didnt make the /usr partition all of the packages were being installed in the / partition ..now all the space in the / partition is filled ...i ran du -h... (3 Replies)
Discussion started by: tarunicon
3 Replies
6. AIX
Paging space is 100% full? what step can i take (3 Replies)
Discussion started by: ramraj731
3 Replies
7. Solaris
Hi,
Is there any chance that a file system that mounted on the server becomes read only when the space in that file system becomes full?
Regards,
Sreejith (9 Replies)
Discussion started by: Sreejith K
9 Replies
8. Emergency UNIX and Linux Support
Hello,
This is RHEL 5.7. swap is almost full, but I am not sure, what to release and how to release space. This is production server so I would like to try all possible options before reboot.
# top
top - 00:18:26 up 327 days, 7:01, 3 users, load average: 0.16, 0.21, 0.18
Tasks: 782 total, ... (7 Replies)
Discussion started by: solaris_1977
7 Replies
9. Shell Programming and Scripting
i want to create 1 script to monitor 1 particular filesystem out of the diferent filesystems. if disk space of that particular filesystem increases by 80% it sends an alert mail to an email id
---------- Post updated at 04:18 PM ---------- Previous update was at 04:17 PM ----------
no. I am... (1 Reply)
Discussion started by: rakeshhhhhhhh
1 Replies
null(n) null(n)
__________________________________________________________________________________________________________________________________________________
NAME
null - Create and manipulate null channels
SYNOPSIS
package require Tcl
package require memchan
null
_________________________________________________________________
DESCRIPTION
The command described here is only available in a not-yet released version of the package. Use the CVS to get the sources.
null creates a null channel which absorbs everything written into it. Reading from it is not possible, or rather will always return zero
bytes. These channels are essentially Tcl-specific variants of the null device for unixoid operating systems (/dev/null). Transfer-
ing the generated channel between interpreters is possible but does not make much sense.
OPTIONS
Memory channels created by null provide one additional option to set or query.
-delay ?milliseconds?
A null channel is always writable and readable. This means that all fileevent-handlers will fire continuously. To avoid starvation
of other event sources the events raised by this channel type have a configurable delay. This option is set in milliseconds and
defaults to 5.
A null channel is always writable and never readable. This means that a writable fileevent-handler will fire continuously and a readable
fileevent-handler never at all. The exception to the latter is only the destruction of the channel which will cause the delivery of an eof
event to a readable handler.
SEE ALSO
fifo, fifo2, memchan, random, zero
KEYWORDS
channel, i/o, in-memory channel, null
COPYRIGHT
Copyright (c) 1996-2003 Andreas Kupries <andreas_kupries@users.sourceforge.net>
Memory channels 2.2 null(n)