12-02-2005
Hi Perderabo,
this is sun box running solaris 8.few days back a file system was full.
i had made space in it..but it didn't work out.
Actually,it was not FS problem...bcoz when i observed ,i found that system was running on very low memory ( hardly 200 MB real) ,so i guess only root was allowed.
I killed few sessions;brought down my databse;& re-booted machine.
now i hav almost 7GB real memory free after reboot,so its working now.
Idea of rebooting was the first to struck at my mind..but that ,i guess,could not be a solution all time.
my worry was where all memory was getting used?
bcoz most of the processes were run by root itself..( daemon etc..)
thanks for your suggestion,
regards
Abhijeet
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I am very new to the world of Unix, in the middle of a crash course as I write this due to a system failure for my company. This system went down approximately 24 hours ago due to some apparent thunderstorms that passed through. The problem is that my company, like many others, has laid off... (5 Replies)
Discussion started by: Phaedirean
5 Replies
2. HP-UX
fatal server error:
couldn't open x pointer device! is one attached?
xinit: connection refused (errno 239): unable to connect to X server
xinit: no such process (errno3): server error. (1 Reply)
Discussion started by: nobody
1 Replies
3. UNIX for Advanced & Expert Users
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (0 Replies)
Discussion started by: mcastill66
0 Replies
4. AIX
$ errpt | more
IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION
3074FEB7 0802050205 T H fscsi1 ADAPTER ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
B8113DD1 0802050205 T H fcs1 LINK ERROR
3074FEB7 0802050205 T H fscsi0 ADAPTER ERROR
B8113DD1 ... (2 Replies)
Discussion started by: mcastill66
2 Replies
5. UNIX for Dummies Questions & Answers
I'm trying to set up x2x between my desktop and laptop, and as a precondition to that, I'm just trying to get each to be able to display programs on the other (e.g. "desktop$ xterm -display laptop:0").
OS is Ubuntu 5.10 and X version is X.org 6.8.2
I've set up X to run without -nolisten, and... (1 Reply)
Discussion started by: vertigo23
1 Replies
6. Programming
hi
i have written a program to display files in a directory
but it doesnt compile on the sun/solaris system....
im using gcc(inbuilt compiler)
im generally used to working on a windows environment so maybe im overlookiing something
ive added comments to help readability of the program
i also... (2 Replies)
Discussion started by: anything2
2 Replies
7. UNIX for Dummies Questions & Answers
Hi all, dummy here.... I have major errors on entering the shell. On login I get:
-bash: dircolors: command not found
-bash: tr: command not found
-bash: fgrep: command not found
-bash: grep: command not found
-bash: grep: command not found
-bash: id: command not found
-bash: [: =: unary... (12 Replies)
Discussion started by: wcmmlynn
12 Replies
8. UNIX for Advanced & Expert Users
Hi,
I can see "udpInOverflows" errors when I execute 'netstat -s' on my Solaris box.
The number of errors are small - about 40.
e.g.
$ netstat -s|grep udp
UDP udpInDatagrams =1249190732 udpInErrors = 0
udpOutDatagrams =31663030 udpOutErrors = 0... (1 Reply)
Discussion started by: chaandana
1 Replies
9. Shell Programming and Scripting
Hi I am new to shell scripting. I am using a shell script to create a SQL script file and then call it as well. The created SQL script file has calls to 2 other sql script file, as well as compile and execute a procedure. all this works fine. I am getting some simple errors. My code is as below
... (8 Replies)
Discussion started by: man_expo
8 Replies
10. Shell Programming and Scripting
ln: Filename1 and Filename2 are identical.
Seems to be an error.. Unable to proceed further
Can you ppl help me? (5 Replies)
Discussion started by: DevM
5 Replies
REBOOT(8) System Manager's Manual REBOOT(8)
NAME
reboot - stopping and restarting the system
SYNOPSIS
/sbin/reboot [ -lqnhdarsfRD ]
/sbin/halt [ -lqndars ]
/sbin/fastboot [ -lqndarsRD ]
DESCRIPTION
2.11BSD is started by placing it in memory at location zero and transferring to its entry point. Since the system is not reentrant, it is
necessary to read it in from disk or tape each time it is to be boot strapped.
Rebooting a running system: When the system is running and a reboot is desired, shutdown(8) is normally used to stop time sharing and put
the system into single user mode. If there are no users then /sbin/reboot can be used without shutting the system down first.
Reboot normally causes the disks to be synced and allows the system to perform other shutdown activities such as resynchronizing hardware
time-of-day clocks. A multi-user reboot (as described below) is then initiated. This causes a system to be booted and an automatic disk
check to be performed. If all this succeeds without incident, the system is then brought up for multi-user operation.
Options to reboot are:
-l Don't try to tell syslogd(8) what's about to happen.
-q Reboot quickly and ungracefully, without shutting down running processes first.
-n Don't sync before rebooting. This can be used if a disk or the processor is on fire.
-h Don't reboot, simply halt the processor.
-d Dump memory onto the dump device, usually part of swap, before rebooting. The dump is done in the same way as after a panic.
-a Have the system booter ask for the name of the system to be booted, rather than immediately booting the default system (/unix).
-r Mount the root file system as read only when the system reboots. This is not supported by the kernel in 2.11BSD.
-s Don't enter multi-user mode after system has rebooted - stay in single user mode.
-f Fast reboot. Omit the automatic file system consistency check when the system reboots and goes multi-user. This is accomplished by
passing a fast reboot flag on to the rebooting kernel. This currently prevents the use of -f flag in conjunction with the -h (halt)
flag.
-D Set the autoconfig(8) debug flag. This is normally not used unless one is debugging the autoconfig program.
-R Tells the kernel to use the compiled in root device. Normally the system uses the device from which it was booted as the
root/swap/pipe/dump device.
Reboot normally places a shutdown record in the login accounting file /usr/adm/wtmp. This is inhibited if the -q or -n options are
present. Note that the -f (fast reboot) and -n (don't sync) options are contradictory; the request for a fast reboot is ignored in this
case.
Halt and fastboot are synonymous with ``reboot -h'' and ``reboot -f'', respectively.
Power fail and crash recovery: Normally, the system will reboot itself at power-up or after crashes if the contents of low memory are
intact. An automatic consistency check of the file systems will be performed, and unless this fails, the system will resume multi-user
operations.
SEE ALSO
autoconfig(8), sync(2), utmp(8), shutdown(8), syslogd(8)
3rd Berkeley Distribution May 24, 1996 REBOOT(8)