Sponsored Content
Full Discussion: High Mem & Cpu Utilisation
Operating Systems Linux High Mem & Cpu Utilisation Post 302077666 by jaryer on Saturday 24th of June 2006 11:53:42 AM
Old 06-24-2006
oh,my god.

max_connections=2000
wait_timeout=30
and optimizing your programa
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

need to know CPU utilisation

We have a Sun Sparc System which has multiple CPUs (4 Nos.). I need a command/program that can be used to monitor the % utilization per CPU. (2 Replies)
Discussion started by: saood
2 Replies

2. Red Hat

What would cause high kernel/system utilisation

We have a VM running RedHat that seems to have very high system (kernel) utilisation compared to our physical servers running the same OS and workload that show normal system time utilisation. Any ideas? Thanks in advance. (2 Replies)
Discussion started by: azurty
2 Replies

3. IP Networking

bandwidth utilisation high after implementing firewall

hi, we have one unix server which sends multicast packets in the network, recently we have implemented firewall in between unix server and clients.After implementing firewall we found our lease line utilisation has been increased dramatically. Is this because of firewall or else...please... (2 Replies)
Discussion started by: ajaysahoo
2 Replies

4. AIX

CPU and memory utilisation by one process

Hi, We need to monitor one process over time to see at which exact point it starts to consume to much memory and CPU (to correlate this with some other events). I am a newbie in AIX, so please could you tell me which command will give a snapshot of the current state of a process so that I... (1 Reply)
Discussion started by: yallow
1 Replies

5. UNIX for Dummies Questions & Answers

Kernel/ user space and high/ low mem

Need some clarification on this.... 1. how are kernel/ user spaces and high/low memory related? 2. What do they all mean when i have the kernel command line as: "console=ttyS0,115200 root=/dev/sda2 rw mem=exactmap memmap=1M@0 memmap=96M@1M irqpoll" or 2. what do mem and memmap mean in... (3 Replies)
Discussion started by: dragonpoint
3 Replies

6. UNIX for Dummies Questions & Answers

CPU Utilisation Report on Solaris 10

Hi all, I'm using Solaris 10 and have an occasional problem where a process that runs near to midnight each day, takes anywhere between 30 seconds and over two minutes to complete. I suspect that the CPU is highly utilised during the times where it takes a long time to complete, but I need a way... (3 Replies)
Discussion started by: wthomas
3 Replies

7. UNIX for Dummies Questions & Answers

Finding cpu utilisation

Hi , I need to find the average percentage of CPU utilisised by a particular process through a shell script. Suppose if a process is running for 6 hours i need to get average CPU utilised by it. Could you please assist me. Thanks, (0 Replies)
Discussion started by: praviper
0 Replies

8. Linux

Reason/components behind high memory utilisation on linux

Hi friends, Problem: High memory utilisation of one linux server, due to which a database crashed on the server. My question to all: How does glance calculate that memory utilisation on the linux server is 98%. I mean what components are part of (31.4gb-599mb)? How can i check that myself? Can... (3 Replies)
Discussion started by: kunwar
3 Replies

9. Shell Programming and Scripting

CPU utilisation in AIX

Hi, I want to write one script that sent mail when CPU utilisation is more then 70%. i used topas but problem is it will show output only when we press ctrl +c. Please let me know if there is some other command that will give cpu utilisation which i can use in shell script. Thanks (3 Replies)
Discussion started by: ranvijaidba
3 Replies

10. AIX

Overall cpu Utilisation

Hi, I need a command to check overall cpu utilisation TIA (3 Replies)
Discussion started by: sumanthupar
3 Replies
envelopes(5)							File Formats Manual						      envelopes(5)

NAME
envelopes - sender/recipient lists attached to messages INTRODUCTION
Electronic mail messages are delivered in envelopes. An envelope lists a sender and one or more recipients. Usually these envelope addresses are the same as the addresses listed in the mes- sage header: (envelope) from djb to root From: djb To: root In more complicated situations, though, the envelope addresses may differ from the header addresses. ENVELOPE EXAMPLES
When a message is delivered to several people at different locations, it is first photocopied and placed into several envelopes: (envelope) from djb to root From: djb Copy #1 of message To: root, god@brl.mil (envelope) from djb to god@brl.mil From: djb Copy #2 of message To: root, god@brl.mil When a message is delivered to several people at the same location, the sender doesn't have to photocopy it. He can instead stuff it into one envelope with several addresses; the recipients will make the photocopy: (envelope) from djb to god@brl.mil, angel@brl.mil From: djb To: god@brl.mil, angel@brl.mil, joe, frde Bounced mail is sent back to the envelope sender address. The bounced mail doesn't list an envelope sender, so bounce loops are impossi- ble: (envelope) from <> to djb From: MAILER-DAEMON To: djb Subject: unknown user frde The recipient of a message may make another copy and forward it in a new envelope: (envelope) from djb to joe From: djb Original message To: joe (envelope) from joe to fred From: djb Forwarded message To: joe A mailing list works almost the same way: (envelope) from djb to sos-list From: djb Original message To: sos-list (envelope) from sos-owner to god@brl.mil From: djb Forwarded message To: sos-list to recipient #1 (envelope) from sos-owner to frde From: djb Forwarded message To: sos-list to recipient #2 Notice that the mailing list is set up to replace the envelope sender with something new, sos-owner. So bounces will come back to sos- owner: (envelope) from <> to sos-owner From: MAILER-DAEMON To: sos-owner Subject: unknown user frde It's a good idea to set up an extra address, sos-owner, like this: the original envelope sender (djb) has no way to fix bad sos-list addresses, and of course bounces must not be sent to sos-list itself. HOW ENVELOPE ADDRESSES ARE STORED
Envelope sender and envelope recipient addresses are transmitted and recorded in several ways. When a user injects mail through qmail-inject, he can supply a Return-Path line or a -f option for the envelope sender; by default the envelope sender is his login name. The envelope recipient addresses can be taken from the command line or from various header fields, depending on the options to qmail-inject. Similar comments apply to sendmail. When a message is transferred from one machine to another through SMTP, the envelope sender is given in a MAIL FROM command, the envelope recipients are given in RCPT TO commands, and the message is supplied separately by a DATA command. When a message is delivered by qmail to a single local recipient, qmail-local records the recipient in Delivered-To and the envelope sender in Return-Path. It uses Delivered-To to detect mail forwarding loops. sendmail normally records the envelope sender in Return-Path. It does not record envelope recipient addresses, on the theory that they are redundant: you received the mail, so you must have been one of the envelope recipients. Note that, if the header doesn't have any recipient addresses, sendmail will move envelope recipient addresses back into the header. This situation occurs if all addresses were originally listed as Bcc, since Bcc is automatically removed. When sendmail sees this, it creates a new Apparently-To header field with the envelope recipient addresses. This has the strange effect that each blind-carbon-copy recipient will see a list of all recipients on the same machine. When a message is stored in mbox format, the envelope sender is recorded at the top of the message as a UUCP-style From (no colon) line. Note that this line is less reliable than the Return-Path line added by qmail-local or sendmail. SEE ALSO
qmail-header(5), qmail-local(8), qmail-inject(8) envelopes(5)
All times are GMT -4. The time now is 07:17 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy