Memory problem


 
Thread Tools Search this Thread
Top Forums Programming Memory problem
# 1  
Old 06-17-2002
Memory problem

Hi:

I have a server with a very little memory leak (29 bytes) as reported by Purify.
Itīs a pooled server, so each process lives forever accepting conections.But top or ps commands show that used memory it is always increasing much more than 29 bytes (30K mor or less) in each conection.
How can this be if Purify reports such a little memory leak?
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Memory allocation problem

I am using ubuntu. I have written a program to calculate prime factors. it works perfectly fine till entered number is less than 9989 (or so ) but when one enters a number higher than that, for example 15000, it does not work. Can anyone guide me whats the problem ? although new codes are welcome,... (2 Replies)
Discussion started by: Abhishek_kumar
2 Replies

2. Red Hat

1Gb+ memory problem

Hi, I have a Linux distribution ( Oralce Enterprise Linux 5.3 i.e. Redhat ) that I have installed. It works fine when I used 2*512Mb dimms or replace them with a single 1Gb dimm. However when I try to go above 1 Gb the bootup and general performance deteriorates badly. The BIOS picks up the memory... (3 Replies)
Discussion started by: jimthompson
3 Replies

3. HP-UX

Problem with memory leak

Hi, This is my 1st post here. I am facing a rather weired problem. I have a C++ binary running on HP-UX. The output of top as well as glance shows periodic increase in memory. But when i use gdb to detect it, i dont get the desired output...gdb says...no leaks found. Just to mention that I have... (2 Replies)
Discussion started by: kshk123
2 Replies

4. Programming

memory leak problem

hi all Can any one plz explain me about memory leak problem Thankx (5 Replies)
Discussion started by: sonali
5 Replies

5. Programming

Memory allocation problem

I have a program that will fetch some particular lines and store it in a buffer for further operations.The code which is given below works but with some errors.I couldn't trace out the error.Can anybody help on this plz?? #include <stdio.h> #include <stdlib.h> #include<string.h> #define... (1 Reply)
Discussion started by: vigneshinbox
1 Replies

6. Shell Programming and Scripting

tcp/ip and memory problem

how the data from disk is loaded into memory and then it supplied to tcp/ip packet. how i can trace the no of pages loaded in memory by that process and rate of context switch for that process. (1 Reply)
Discussion started by: amar20
1 Replies

7. Solaris

out of memory problem

i am building open source software on a solaris 8 machine for couple of days i am getting error messages like out of memory or no more processes and then build is failing i tried with rebooting the machine but then after couple of days same problem is arising again. can any one... (1 Reply)
Discussion started by: mobydick
1 Replies

8. Programming

how to round up a memory address(memory alignment problem)

Hi, I try to marshal a unsigned int and a char * into a buffer, and then unmarshal them later to get them out. I need to put the char * in the front and unsigned int at the end of the buffer. However, my system always give me "BUS ERROR". I am using Sun Sparcs Sloris 2.10. My code to marshal... (6 Replies)
Discussion started by: nj302
6 Replies

9. Filesystems, Disks and Memory

memory Problem

Hi , One of java programs in our machine allocates 256M of heap memory and max of 512 memory(Tomcat to be specific). Our ulimit per process is 32M.How can a process allocates such a big amount of memory ps v output is PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND 24 220776 220892... (0 Replies)
Discussion started by: ganti
0 Replies

10. Programming

memory problem

Hi , One of java programs in our machine allocates 256M of heap memory and max of 512 memory(Tomcat to be specific). Our ulimit per process is 32M.How can a process allocates such a big amount of memory ps v output is PGIN SIZE RSS LIM TSIZ TRS %CPU %MEM COMMAND ... (0 Replies)
Discussion started by: ganti
0 Replies
Login or Register to Ask a Question
ovs-brcompatd(8)						Open vSwitch Manual						  ovs-brcompatd(8)

NAME
ovs-brcompatd - Bridge compatibility front-end for ovs-vswitchd SYNOPSIS
ovs-brcompatd [options] DESCRIPTION
A daemon that provides a legacy bridge front-end for ovs-vswitchd. It does this by listening for bridge ioctl commands (e.g., those gener- ated by the brctl program) to add or remove datapaths and the interfaces that attach to them. OPTIONS
--appctl=program Sets the name to the program that ovs-brcompatd runs to communicate with ovs-vswitchd. The default is ovs-appctl. Unless program contains /, ovs-brcompatd will search the PATH environment variable to find it. --vsctl=program Sets the name to the program that ovs-brcompatd runs to communicate with ovsdb-server. The default is ovs-vsctl. Unless program contains /, ovs-brcompatd will search the PATH environment variable to find it. --pidfile[=pidfile] Causes a file (by default, ovs-brcompatd.pid) to be created indicating the PID of the running process. If the pidfile argument is not specified, or if it does not begin with /, then it is created in /var/run/openvswitch. If --pidfile is not specified, no pidfile is created. --overwrite-pidfile By default, when --pidfile is specified and the specified pidfile already exists and is locked by a running process, ovs-brcompatd refuses to start. Specify --overwrite-pidfile to cause it to instead overwrite the pidfile. When --pidfile is not specified, this option has no effect. --detach Causes ovs-brcompatd to detach itself from the foreground session and run as a background process. --monitor Creates an additional process to monitor the ovs-brcompatd daemon. If the daemon dies due to a signal that indicates a programming error (e.g. SIGSEGV, SIGABRT), then the monitor process starts a new copy of it. If the daemon die or exits for another reason, the monitor process exits. This option is normally used with --detach, but it also functions without it. --no-chdir By default, when --detach is specified, ovs-brcompatd changes its current working directory to the root directory after it detaches. Otherwise, invoking ovs-brcompatd from a carelessly chosen directory would prevent the administrator from unmounting the file system that holds that directory. Specifying --no-chdir suppresses this behavior, preventing ovs-brcompatd from changing its current working directory. This may be useful for collecting core files, since it is common behavior to write core dumps into the current working directory and the root directory is not a good directory to use. This option has no effect when --detach is not specified. -vmodule[:facility[:level]], --verbose=module[:facility[:level]] Sets the logging level for module in facility to level: o module may be any valid module name (as displayed by the --list action on ovs-appctl(8)), or the special name ANY to set the logging levels for all modules. o facility may be syslog, console, or file to set the levels for logging to the system log, the console, or a file respec- tively, or ANY to set the logging levels for both facilities. If it is omitted, facility defaults to ANY. Regardless of the log levels set for file, logging to a file will not take place unless --log-file is also specified (see below). o level must be one of off, emer, err, warn, info, or dbg, designating the minimum severity of a message for it to be logged. If it is omitted, level defaults to dbg. See ovs-appctl(8) for a definition of each log level. -v, --verbose Sets the maximum logging verbosity level, equivalent to --verbose=ANY:ANY:dbg. -vPATTERN:facility:pattern, --verbose=PATTERN:facility:pattern Sets the log pattern for facility to pattern. Refer to ovs-appctl(8) for a description of the valid syntax for pattern. --log-file[=file] Enables logging to a file. If file is specified, then it is used as the exact name for the log file. The default log file name used if file is omitted is /var/log/openvswitch/ovs-brcompatd.log. -h, --help Prints a brief help message to the console. -V, --version Prints version information to the console. --check-leaks=file Logs information about memory allocation and deallocation to file, to allow for debugging memory leaks in ovs-brcompatd. This option slows down ovs-brcompatd considerably, so it should only be used when a memory leak is suspected. Use the ovs-parse-leaks script to interpret the leak file. --leak-limit=size Limits size of the leak file as specified by --check-leaks to size bytes. Finding leaks sometimes requires allowing the leak file to grow very large, up to 1GB. By default, files are limited to 10MB. NOTES
ovs-brcompatd requires the brcompat_mod.ko kernel module to be loaded. SEE ALSO
ovs-appctl(8), ovs-vsctl(8), ovs-vswitchd(8), ovsdb-server(1), INSTALL.bridge in the Open vSwitch distribution. Open vSwitch March 2009 ovs-brcompatd(8)