good morning
The /tmp filesystem is full at 99 %
I have do a "rm" but the size is the same.
so i think that a process is always alive, but how can i do to know it ? (because I have deleted some file in /tmp)
thank you (9 Replies)
Can you help. My server sunning solaris 9 on x86 platform pretty much hung for a few hours... I could not use telnet or ssh to the box - it kept refusing connection. A few hours later - I was able to log in again.
The server has not rebooted but here are the first errors in the messages log... (5 Replies)
The /tmp is 100% full, I found there are the following big files/directory:
1301500 syslog.out.58
166692 vac
158552 install.dir.2928686
158552 install.dir.2236636
110980 install.dir.2887698
/tmp/vac have some files like :
.toc ... (3 Replies)
Hi,
I would like to know if /tmp file system is full, wheather it will affect the peformance of application installed on AIX. if Memory and CPU are not heavily utilized.
Regards,
Manoj. (1 Reply)
Dear All,
We are on AIX OS, /tmp directory is filled up to 99% percent,
Please suggest, How to get free space for "/tmp"?
which files can be deleted from /tmp? and How to delete it? is there any commands.....
Thanks in advance,
Its very urgent, Helpful answers will be appreciated,
Please... (7 Replies)
Hello all,
The issue is
# df -h /tmp
Filesystem size used avail capacity Mounted on
swap 4.0G 4.0G 8.7M 100% /tmp
# du -sh /tmp/
87M /tmp
By now you probably will say that this is open file destriptor issue.
Well no, nothing... (2 Replies)
I have a Sun-Fire-V210, the Server hangs for sometime and evn console wont be abled to access and after sometime the server comes back active. the messages file shows this , whats causing this ?
# tail -500 messages
Jan 25 07:02:16 xxxxxxxxxxxxx Corrupt label; wrong magic number
Jan 25... (2 Replies)
Hello,
AIX 6.1 TL7 SP6
POwerHA 6.1 SP10
I was experimenting with new hacmp build. It's 3-node cluster build on AIX 6.1 lpars. It contains Ethernet and diskhb networks. Shared vg disk is SAN disk. Two nodes see disk using vscsi, third node sees disk using npiv. Application is db2 server.
... (4 Replies)
Hi everybody,
few days ago we had a big issue with one of our solaris10 server.
Suddenly while my colleague was working on it for some troubleshooting he realized that the performance started to degrade.
At the end it reached the point that was not even possible to login usng the local console... (7 Replies)
Discussion started by: bdegiovanni
7 Replies
LEARN ABOUT MOJAVE
pagesizes
PAGESIZES(5) File Formats Manual PAGESIZES(5)NAME
pagesizes - HylaFAX page size definitions
DESCRIPTION
The pagesizes database defines the page dimensions and guaranteed reproducible areas (GRA) for well-known page sizes. The GRA is the por-
tion of the page that is guaranteed to be imaged during facsimile transmission. This region is typically less than the full page dimen-
sions because of paper roller contacts and other mechanical aspects of the printing process in a facsimile machine.
All HylaFAX programs that require page size information read the information from this database using a page size name. Documents should
be prepared such that the full page dimensions are employed with the imaged area contained within the GRA.
The system-wide default page size to use in preparing documents for transmission is given by the ``default'' entry in the database. (NB:
the default entry should be placed last so that inverse matches find the real page size name and not the default entry.)
The page size database is an ASCII file with the following format. Each entry consists of whitespace-separated fields:
name abbrev width height gra-width gra-height top-margin left-margin
Fields have the following interpretation:
name the full name for the page size; e.g. ISO A4;
abbrev an abbreviated version of the full name for use in compact listings such as the receive queue listing printed by faxstat(1);
width the full width of the page;
height the full height of the page;
gra-width the width of the GRA;
gra-height the height of the GRA;
top-margin the margin between the top of the full page and the top of the GRA;
left-margin the margin between the left side of the full page the left side of the GRA.
The first two fields must be separated from the subsequent fields by a tab character (possibly followed by more whitespace); this is done
to easily permit blank characters to be included in names. Otherwise fields can be separated by any amount of any kind of whitespace.
Numbers are all base 10 and in basic measurement units (BMU); defined as 1/1200 x 25.4 millimeters for paper output with a scale factor of
one. All fields must be present on a single line; otherwise the entry is ignored. Comments are introduced by the ``#'' character and con-
tinue to the end the line.
Page size database lookups are either by name or by page dimensions. Lookups by name are done by sequentially scanning the entries in the
database for the first entry that has a matching abbreviation or substring of the page size name field. The string comparisons ignore case
so, for example, ``a4'' would match a full name of ``ISO A4''. Lookups by dimension scan the entire database and return the page with the
closest dimensions using a straightforward distance metric. If the difference in dimensions of the closest match is greater than 1/2 inch
on each side, then no page entry is returned for a lookup by dimension.
SEE ALSO hylafax-client(1), faxmail(1), faxstat(1), sendfax(1), sgi2fax(1), textfmt(1).
December 5, 1994 PAGESIZES(5)