12-13-2010
It's never RAM -- even Solaris zones just purges your pages if you exceed RAM pages allowed! Someone is limiting you, as that is not the message for no swap (malloc'd space) or for no address space (all heap, code, stack, mapped file space). Google says it is PHP, and usually it means by script error you are taking in all the rows at once; 67M is a lot for a web page.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi All,
We have the commands top and ps through which we can find out the size of the running process.
These commnds are giving the size of my process in MB after rounding of the size.
Is there any way by which I can get the size of my process in Bytes or KBytes.
Any help would be greatly... (2 Replies)
Discussion started by: darshi
2 Replies
2. Shell Programming and Scripting
Hi all,
Does anybody know or guide me on how to remove the first N bytes and the last N bytes from a binary file? Is there any AWK or SED or any command that I can use to achieve this?
Your help is greatly appreciated!!
Best Regards,
Naveen. (1 Reply)
Discussion started by: naveendronavall
1 Replies
3. Linux
The title is clear: why does ext3 allocate 8 blocks for files that are few bytes long?
If I create a file named "test", put a few chars in it, and then I run:
stat test
I get that "Blocks: 8"
I searched in the web and found that ext does that, it allocates 8 blocks even if It doesn't need... (4 Replies)
Discussion started by: Tavo
4 Replies
4. Shell Programming and Scripting
Hi
I need to find and delete 0-4 bytes size files in a folder.
How can I achieve that? (1 Reply)
Discussion started by: kapilk
1 Replies
5. Web Development
Any clues on how to get rid of this PHP error?
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in /website/www/includes/functions_manpages.php on line 58
PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71... (4 Replies)
Discussion started by: Neo
4 Replies
6. Programming
Hi,
If I want to copy a 1024 byte data stream in to the target location in 3-bytes chunk, I guess I can use the following script.
dd bs=1024 count=3 if=/src of=/dest
But, I would like to know, how to do it via a C program. I have tried this with memcpy(), that did not help. (3 Replies)
Discussion started by: royalibrahim
3 Replies
7. UNIX for Dummies Questions & Answers
Hello guys. I really hope someone will help me with this one..
So, I have to write this script who:
- creates a file home/student/vmdisk of 10 mb
- formats that file to ext3
- mounts that partition to /mnt/partition
- creates a file /mnt/partition/data. In this file, there will... (1 Reply)
Discussion started by: razolo13
1 Replies
8. UNIX for Dummies Questions & Answers
Hi Friends,
Could you please tell me why i am getting the below eror while working with awk. I am confused :confused: what to do ?
awk: 0602-591 String 1,9,20,6,6 cannot be longer than 399 bytes. The source line is 1.
The error context is
>>> <<<
awk: 0602-591... (2 Replies)
Discussion started by: i150371485
2 Replies
9. Shell Programming and Scripting
hello,
suppose, entered input is of 1-40 bytes, i need it to be converted to 40 bytes exactly.
example: if i have entered my name anywhere between 1-40 i want it to be stored with 40 bytes exactly.
enter your name:
donald duck (this is of 11 bytes)
expected is as below - display 11... (3 Replies)
Discussion started by: shravan.300
3 Replies
MLOCK(2) Linux Programmer's Manual MLOCK(2)
NAME
mlock - disable paging for some parts of memory
SYNOPSIS
#include <sys/mman.h>
int mlock(const void *addr, size_t len);
DESCRIPTION
mlock disables paging for the memory in the range starting at addr with length len bytes. All pages which contain a part of the specified
memory range are guaranteed be resident in RAM when the mlock system call returns successfully and they are guaranteed to stay in RAM until
the pages are unlocked by munlock or munlockall, until the pages are unmapped via munmap, or until the process terminates or starts another
program with exec. Child processes do not inherit page locks across a fork.
Memory locking has two main applications: real-time algorithms and high-security data processing. Real-time applications require determin-
istic timing, and, like scheduling, paging is one major cause of unexpected program execution delays. Real-time applications will usually
also switch to a real-time scheduler with sched_setscheduler. Cryptographic security software often handles critical bytes like passwords
or secret keys as data structures. As a result of paging, these secrets could be transfered onto a persistent swap store medium, where they
might be accessible to the enemy long after the security software has erased the secrets in RAM and terminated.
Memory locks do not stack, i.e., pages which have been locked several times by calls to mlock or mlockall will be unlocked by a single call
to munlock for the corresponding range or by munlockall. Pages which are mapped to several locations or by several processes stay locked
into RAM as long as they are locked at least at one location or by at least one process.
On POSIX systems on which mlock and munlock are available, _POSIX_MEMLOCK_RANGE is defined in <unistd.h> and the value PAGESIZE from <lim-
its.h> indicates the number of bytes per page.
NOTES
With the Linux system call, addr is automatically rounded down to the nearest page boundary. However, POSIX 1003.1-2001 allows an imple-
mentation to require that addr is page aligned, so portable applications should ensure this.
RETURN VALUE
On success, mlock returns zero. On error, -1 is returned, errno is set appropriately, and no changes are made to any locks in the address
space of the process.
ERRORS
ENOMEM Some of the specified address range does not correspond to mapped pages in the address space of the process or the process tried to
exceed the maximum number of allowed locked pages.
EPERM The calling process does not have appropriate privileges. Only root processes are allowed to lock pages.
EINVAL len was not a positive number.
CONFORMING TO
POSIX.1b, SVr4. SVr4 documents an additional EAGAIN error code.
SEE ALSO
mlockall(2), munlock(2), munlockall(2), munmap(2), setrlimit(2)
Linux 1.3.43 1995-11-26 MLOCK(2)