Sponsored Content
Full Discussion: System Resources?
Top Forums UNIX for Advanced & Expert Users System Resources? Post 43167 by jwolfe on Wednesday 12th of November 2003 01:03:49 PM
Old 11-12-2003
System Resources?

I am running a C program on a SCO box. There are multiple users on using the system resources. My problem is when using fprintfs in the program. I am writing to a log every thing I read in from a file after doing some formatting. I write out to the log with the fprintfs in groupings like 10 fprintfs in a row and then further on down in the program 75 more fprintfs all in a row. When it writes the 75 fprinfts it looses the valid data about midway through the writes to the log. I noticed when I comment out the 1st grouping of 10 fprintfs the second group of 75 fprintfs still lose valid data during the writes, but not till further down in sequence. Although it is not a direct 1 to 1 relationship the more fprintfs I comment out in the beginning of the sequence the further it gets to end of the fprinfts to the point that it will finish writing to the log all the valid data.

Could limited memory resources cause this problem by reallocating memory, if the available memory is less then when the program was compiled, or would it error out during execution?
 

3 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

VI hogging system resources???

Hello all. I was on my pc last night when I noticed that my hard drive light was on and when I typed in "uptime" I recieved some crazy load averages. load average: 3.30, 3.07, 2.95. Anyway I type in "top" to see what processes are being the resource hogs and im surprised as hell to see that one... (2 Replies)
Discussion started by: ThePreacher
2 Replies

2. UNIX for Advanced & Expert Users

Looking for utility to monitor system resources

Hi Community, I'm looking for a linux based utility for monitoring following system resources 1. Memory 2. CPU Usage I know there are plenty freewares which poll the data and print in form of html pages. For eg. MRTG, Novel's Linux Monitoring tools etc. But my requirement is deviated a... (1 Reply)
Discussion started by: anilgurwara
1 Replies

3. Ubuntu

Xorg is taking System Resources.

Hi All, I am facing System Speed problem.i saw in top command Xorg process was taking most of the time 20% of CPU and Memory.How to make it normal. Currently i am using AMD Athlon 64 HT technology processor(Socket 939) 512 DDR1 RAM Nvidia 5200 GeForce 128 MB Graphic card. i need help in... (2 Replies)
Discussion started by: arvindk.monu
2 Replies
savecore(8)						      System Manager's Manual						       savecore(8)

Name
       savecore - save a core dump of the operating system

Syntax
       /etc/savecore [ options ] dirname [ system ] [ corename ]

Description
       The  command  is  meant	to  be called near the end of the file.  The command saves the core dump of the system (assuming one was made) and
       writes a reboot message in the shutdown log.

       The command checks the core dump to be certain it corresponds with the current running ULTRIX.  If it does, it saves the core image in  the
       file  dirname/vmcore.n and saves the namelist in the file dirname/vmunix.n.  The trailing .n in the pathnames is replaced by a number which
       increments each time is run in that directory.

       After saving the core and namelist images, will save the error logger buffer into a predetermined file.	The error logger  buffer  contains
       information about why the crash occurred.  After completes, the daemon will extract the error logger file and translate its contents into a
       form familiar to the program.

       Before writes out a core image, it reads a number from the file dirname/minfree.  If there are fewer free blocks  on  the  filesystem  that
       contains  dirname  than the number obtained from the file, a core dump is not done.  If the file does not exist, savecore always writes out
       the core file (assuming that a core dump was taken).

       The command also writes a reboot message in the shut down log.  If the system crashed as a result of a panic, also records the panic string
       in the shut down log.

       For  partial  crash  dumps,  creates  a	sparse	core image file in dirname/vmcore.n.  If this sparse core image file is copied or moved to
       another location, the file expands to its true size which can take too much file system space.  Hence, to copy or move  sparse  core  image
       files, you must use the command. The command has a conversion option to create sparse output files.

Options
       -c   Clears  the core dump.  This option is useful when the core dump is corrupted in a way that will not allow to save it safely.  Use the
	    option with caution, because once it clears the core dump, the core dump cannot be retrieved.

       -d dumpdev dumplo
	    Specifies the dump device and the dump offset when running on a system image other than the currently running system image.  The  pro-
	    gram  assumes  that  the running system image is and it reads the dump device and dump device offset are different in the system image
	    that crashed, the option provides the correct dump device and dump device offset.

       -e   Saves only the error logger buffer into a file.  If used, core or namelist images are not saved.

       -f corename
	    Takes the i corefile name as the file from which to extract the the crash dump data instead of the default dump device.   This  option
	    is used only for diskless workstations.

       If  the	core  dump was from a system other than /vmunix, the name of that system must be supplied as system.  The program assumes that the
       running image is

       After successful completion, the core dump is cleared.  Also, a message is written in the file which tells whether the  dump  succeeded	or
       failed.

Files
       Shut down log

       Current running ULTRIX system

See Also
       dd(1), uerf(8)

																       savecore(8)
All times are GMT -4. The time now is 03:07 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy