01-30-2003
Thanks perdarabo
I inherited this firewall, and believe me, i am in total agreement about the logs on root thing, but at the moment the logs are extremely minimal in size and were used as an example of my inability to write to the disk. I also accept that df is reporting ok after trying df -k /proc, my apologies. However why when i run du -sk * on root does it report 2.6 gig on /proc and subsequently stop me writing to that disk. If /proc is virtual and is a reflection of processes running, does that mean that 2.6 gig of my disk space on root is being used by o/s and firewall daemons/processes, because that is all thats running on the box ( the o/s has been hardened and stripped down to basics), if so, i would find that hard to comprehend. (the firewall manufacturer does not indicate anything about 3 gig of space to run in its minimum spec).With all due respect to your suggestion of using kill -9 on the process ids, im sure you can appreciate that in a production environment this is not something i can do. Put basically, if there are 2.6 gigs being used by a few processes then something must be wrong, and I still need a workable suggestion if anyone has one
Any help would be greatly appreciated
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Dear Group,
I am not much used to UNIX. The company I am hosting wiht refuses to help me with this trouble, but as near as I can see, it is NOT my trouble.
I have had this service for over a year. I just renewed for another year and all of a sudden the disk quota has been disappearing. I... (3 Replies)
Discussion started by: cindy
3 Replies
2. UNIX for Dummies Questions & Answers
Hello
I run Gentoo Linux on my computer:
Athlon XP 1700+ ~1,46 mhz
512 mb ram
After a while, my computer works really slow, and when I cat /proc/meminfo, I see that I only have 8mb of 512 mb free!
How is that possible?
I dont run anything I can think of that eats that amount of... (4 Replies)
Discussion started by: Maestin
4 Replies
3. What is on Your Mind?
Hi, guys !
I was wondering... how many of you are vegetarians ? and why ? (31 Replies)
Discussion started by: Sergiu-IT
31 Replies
4. Solaris
Hi,
I am not very much fmiliar with Solaris OS. My main concern for posting is One application is eating 50% of CPU and I cannot run that application, If I perform any action in that application it takes real long time.
I have solaris installed on my development machine.I have my application... (11 Replies)
Discussion started by: pandu345
11 Replies
5. Solaris
Hi,
I have installed sendmail on my solaris server. But sendmail its up high memory. its eat upto around 9-10 GB memory.
What to do in this ?
Thanks
NeeleshG (6 Replies)
Discussion started by: neel.gurjar
6 Replies
6. Shell Programming and Scripting
Hi!
Could someone explain me why the below code is printing the contents of IF block 5 times instead of 0?
#!/bin/bash
VAR1="something"
VAR2="something"
for((i=0;i<10;i++))
do
if(($VAR1=~$VAR2))
then
echo VAR1: $VAR1
echo... (3 Replies)
Discussion started by: machinogodzilla
3 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I am trying to calculate the CPU Usage by getting the difference between the idle time reported by /proc/stat at 2 different intervals. Now the 4th entry in the first line of /proc/stat will give me the 'idle time'. But I also came across /proc/uptime that gives me 2 entries : 1st one as the... (0 Replies)
Discussion started by: coderd
0 Replies
8. Shell Programming and Scripting
how to find a job which is writing a big file and eating up space? (3 Replies)
Discussion started by: rush2andy
3 Replies
9. Shell Programming and Scripting
Hi all,
using AWK iam sorting auniq data from a file the file size is 8GB, while running that script , the over all cpu usage will be nearly 8
how to avoid this ?? any other alternate is available for awk?
Thanks in Advance
Anish kumar.V (13 Replies)
Discussion started by: anishkumarv
13 Replies
10. SuSE
Im issuing a cat /proc/mdstat, dmraid -r, and finding a cciss, to know if my server is software raid and hardware raid. But all of them are missing.
What is the other way to know, your disk are raid, your disks is sync, your disk are out of sync, your disk is failed, ASIDE LOOKING AT THEM... (0 Replies)
Discussion started by: invinzin21
0 Replies
memx(8) System Manager's Manual memx(8)
NAME
memx - memory exerciser
SYNOPSIS
/usr/field/memx -s [-h] [-ofile] [-ti] [-mj] [-pk]
OPTIONS
The memx options are as follows: Print the help message for the memx command. Disables automatic shared memory testing. Save diagnostic
output in file. Run time in minutes (i). The default is to run until the process receives a CTRL-C or a kill -15 pid command. The memory
size in bytes (j) to be tested by each spawned process. Must be greater than 4095. The default is (total-memory)/20. The number of pro-
cesses to spawn (k). The default is 20. The maximum is also 20.
DESCRIPTION
The memx memory exerciser spawns processes to exercise memory by writing and reading three patterns: 1's and 0's, 0's and 1's, and a random
pattern.
You specify the number of processes to spawn and the size of memory to be tested by each process. If the shmx Shared Memory exerciser is
present, it will be the first process spawned; the remaining processes are standard memory exercisers. The memx exerciser will run until
the process receives a CTRL-C or a kill -15 pid command.
A logfile for you to examine and then remove is created in the current working directory. If there are errors in the logfile, check the
syslog file where the driver and kernel error messages are saved.
RESTRICTIONS
The memx exerciser is restricted by the size of the available swap space. The size of the swap space and the size of internal memory
available determines how many processes can run on the system. For example, If there is 16 Mbytes of swap space and 16 Mbytes of memory,
all of the swap space would be used if all 20 spawned memory exercisers are running. In that event, no new processes would be able to run.
On systems with large amounts of memory and small swap space, you must restrict the number of memory exercisers and/or the size of memory
being tested.
If there is a need to run a system exerciser over an NFS link or on a diskless system there are some restrictions. For exercisers that
need to write into a file system, such as fsx(8), the target file system must be writable by root. Also, the directory in which any of the
exercisers are executed must be writable by root because temporary files are written into the current directory. These latter restrictions
are sometimes difficult to overcome because often NFS file systems are mounted in a way that prevents root from writing into them. Some of
the restrictions may be overcome by copying the exerciser to another directory and then executing it.
You should specify the -s option to disable automatic shared memory testing, which is not supported.
EXAMPLES
The following example tests all of memory by running 20 spawned processes until a CTRL-C or kill -15 pid command is received: %
/usr/field/memx The following example runs 10 spawned processes, memory size 500,000 bytes, for 180 minutes in the background. %
/usr/field/memx -t180 -m500000 -p10 &
SEE ALSO
Commands: cmx(8), diskx(8), fsx(8), shmx(8), tapex(8)
memx(8)