08-21-2008
Zak,
Yes. I feel shutting down application which is eating most of the memory free up some memory to delete swap space. Rather than shutting down box, its better option.
- nilesh
10 More Discussions You Might Find Interesting
1. Programming
Hi,
I am using gmake to compile a c program with a makefile. The make file runs ld. I get the following error
jsh1035c:/users/egate453/admegate/kapil/samples $ gmake -e -f GNUmakefile queue_c
gmake -f ./GNUmakefile queue_c in_objdir=1 build_root=/users/egate453/admegate/kapil/samples... (2 Replies)
Discussion started by: handak9
2 Replies
2. Solaris
When i try to type swap -l ,nothing come out but blinking.
May i know what is the problem and solutions ?
thanks (6 Replies)
Discussion started by: Farbegas
6 Replies
3. Solaris
Hello and thanks in advance.
I have a Sun box with raid 1 on the O/S disks using solaris svm.
I want to unmirror my swap partition, and add the slice on the second disk as an additional swap device. This would give me twice as much swap space.
I have been warned not to do this by some... (3 Replies)
Discussion started by: BG_JrAdmin
3 Replies
4. HP-UX
I have a HP-UX B.11.23 server with 16 gb of memory 84 gb of swap configured. I am being pushed to define more swap to try and get more Tuxedo domains to start. At what point do we have too much swap for the amount of memory? Thanks in advance. (11 Replies)
Discussion started by: scotbuff
11 Replies
5. UNIX for Advanced & Expert Users
Usually when su rejects an attempt to switch user it responds with "Sorry" but with a certain username on some unix servers the response is "Killed". I'm guessing the su accepted the username/password but refused to spawn child shell with the specified username. What's causing this and what has to... (8 Replies)
Discussion started by: twk
8 Replies
6. Red Hat
free -m : 1023 total swap space
created default partition /dev/sdb1 50M using fdisk. i did write the changes.
#mkswap /dev/sdb1
#swapon /dev/sdb1
free -m : 1078 total swap space
this shows that the swap is on
Question : i did not change the type LINUX SWAP (82) in fdisk.
so why is... (5 Replies)
Discussion started by: dplinux
5 Replies
7. HP-UX
Hi
I have an integrity machine rx7620 and rx8640 running hp-ux 11.31. I'm planning to fine tune the system:
- I would like to know when does the memory swap space spill over to the device swap space?
- And how much % of memory swap utilization should be specified (swap space device... (6 Replies)
Discussion started by: lamoul
6 Replies
8. UNIX for Dummies Questions & Answers
hi power went out. next day unix sco wont boot up error code 303. any help appreciated as we are clueless. (11 Replies)
Discussion started by: fredthayer
11 Replies
9. Solaris
Hi,
Can somebody please help here, since iam just a beginner.
According to my book knowledge.
the Avalilable memory calculated by swap -l (includes only swap) should be small as compared to swap -s value(includes Virtual memory=swap +physical).
but this is quite opposite in my case.
swap... (6 Replies)
Discussion started by: Laxxi
6 Replies
10. Solaris
Hi Solaris Folks :),
I need to calculate the swap usage on solaris server, please let me understand the output of below swap -s and swap -l commands.
$swap -s
total: 1774912k bytes allocated + 240616k reserved = 2015528k used, 14542512k available
$swap -l
swapfile dev swaplo... (6 Replies)
Discussion started by: seenuvasan1985
6 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)