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
LEARN ABOUT FREEBSD
boot0cfg
BOOT0CFG(8) BSD System Manager's Manual BOOT0CFG(8)
NAME
boot0cfg -- boot manager installation/configuration utility
SYNOPSIS
boot0cfg [-Bv] [-b boot0] [-d drive] [-e bell character] [-f file] [-i volume-id] [-m mask] [-o options] [-s slice] [-t ticks] disk
DESCRIPTION
The FreeBSD 'boot0' boot manager permits the operator to select from which disk and slice an i386 machine (PC) is booted.
Note that what are referred to here as ``slices'' are typically called ``partitions'' in non-BSD documentation relating to the PC. Typi-
cally, only non-removable disks are sliced.
The boot0cfg utility optionally installs the 'boot0' boot manager on the specified disk; and allows various operational parameters to be con-
figured.
On PCs, a boot manager typically occupies sector 0 of a disk, which is known as the Master Boot Record (MBR). The MBR contains both code (to
which control is passed by the PC BIOS) and data (an embedded table of defined slices).
The options are:
-B Install the 'boot0' boot manager. This option causes MBR code to be replaced, without affecting the embedded slice table.
-b boot0
Specify which 'boot0' image to use. The default is /boot/boot0 which will use the video card as output, alternatively /boot/boot0sio
can be used for output to the COM1 port. (Be aware that nothing will be output to the COM1 port unless the modem signals DSR and CTS
are active.)
-d drive
Specify the drive number used by the PC BIOS in referencing the drive which contains the specified disk. Typically this will be 0x80
for the first hard drive, 0x81 for the second hard drive, and so on; however any integer between 0 and 0xff is acceptable here.
-e bell character
Set the character to be printed in case of input error.
-f file
Specify that a backup copy of the preexisting MBR should be written to file. This file is created if it does not exist, and replaced
if it does.
-i volume-id
Specifies a volume-id (in the form XXXX-XXXX) to be saved at location 0x1b8 in the MBR. This information is sometimes used by NT, XP
and Vista to identify the disk drive. The option is only compatible with version 2.00 of the 512-byte boot block.
-m mask
Specify slices to be enabled/disabled, where mask is an integer between 0 (no slices enabled) and 0xf (all four slices enabled).
Each mask bit enables corresponding slice if set to 1. The least significant bit of the mask corresponds to slice 1, the most sig-
nificant bit of the mask corresponds to slice 4.
-o options
A comma-separated string of any of the following options may be specified (with ``no'' prepended as necessary):
packet Use the disk packet (BIOS INT 0x13 extensions) interface, as opposed to the legacy (CHS) interface, when doing disk I/O.
This allows booting above cylinder 1023, but requires specific BIOS support. The default is 'packet'.
setdrv Forces the drive containing the disk to be referenced using drive number definable by means of the -d option. The default is
'nosetdrv'.
update Allow the MBR to be updated by the boot manager. (The MBR may be updated to flag slices as 'active', and to save slice
selection information.) This is the default; a 'noupdate' option causes the MBR to be treated as read-only.
-s slice
Set the default boot selection to slice. Values between 1 and 4 refer to slices; a value of 5 refers to the option of booting from a
second disk. The special string ``PXE'' or a value of 6 can be used to boot via PXE.
-t ticks
Set the timeout value to ticks. (There are approximately 18.2 ticks per second.)
-v Verbose: display information about the slices defined, etc.
FILES
/boot/boot0 The default 'boot0' image
/boot/boot0sio Image for serial consoles (COM1,9600,8,N,1,MODEM)
EXIT STATUS
The boot0cfg utility exits 0 on success, and >0 if an error occurs.
EXAMPLES
To boot slice 2 on the next boot:
boot0cfg -s 2 ada0
To enable just slices 1 and 3 in the menu:
boot0cfg -m 0x5 ada0
To go back to non-interactive booting, use fdisk(8) to install the default MBR:
fdisk -B ada0
SEE ALSO
geom(4), boot(8), fdisk(8), gpart(8)
AUTHORS
Robert Nordier <rnordier@FreeBSD.org>
BUGS
Use of the 'packet' option may cause 'boot0' to fail, depending on the nature of BIOS support.
Use of the 'setdrv' option with an incorrect -d operand may cause the boot0 code to write the MBR to the wrong disk, thus trashing its previ-
ous content. Be careful.
BSD
October 1, 2013 BSD