07-21-2003
Not sure what you are looking for since you would not really do the same type of rebuilding of the kernel in Solaris 8 as you would in Freebsd. You can change some parameters but you don't recompile the kernel in Solaris 8. You can check the man page for system (4) for more info.
From SunSolve (note the second line):
Quote:
The SunOS[TM] 2.X kernel modules are automatically loaded when needed.This makes rebuilding the kernel unnecessary.
There are parameters for the kernel and kernel modules that can be tuned. However, it isn't necessary to change these parameters, exceptunder special circumstances.
The module variables associated with semaphores are:
Parameter Default Description
--------- ------- -----------
seminfo_semmap 10 Number of entries in the semaphore map
seminfo_semmni 10 Number of semaphore identifiers
seminfo_semmns 60 Number of semaphores in the system
seminfo_semmnu 30 Number of undo structures in the system
seminfo_semmsl 25 Maximum number of semaphores, per id
seminfo_semopm 10 Maximum number of operations, per
semaphore call
seminfo_semume 10 Maximum number of undo entries, per
process
seminfo_semvmx 32767 Semaphore maximum value
seminfo_semaem 16384 Adjust on exit maximum value
1. Enter a line in the /etc/system file, using the following
syntax:
set semsys:seminfo_variable=value
For example, to increase seminfo_semmap from the default of 10 to 20,
add the following line to the /etc/system file:
set semsys:seminfo_semmap=20
2. Reboot the system
The kernel parses the /etc/system file during autoconfiguration
and overrides the default value for the parameters specified
in this file.
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi!
I'm recompiling a kernel (Linux 2.4.18) for my laptop just to take away all unnecessary stuff and add some other various things :)
I would consider myself a beginner slowly becoming an intermediate, thus my knowledge in the linux kernel and hardware aren't that great.
My question is... (1 Reply)
Discussion started by: J.P
1 Replies
2. BSD
Does anyone know how to enter the Kernel Configuration program in FreeBSD before installation to resolve conflicts of hardware?:confused: (3 Replies)
Discussion started by: Enoch Chan
3 Replies
3. SuSE
Dear All,
I would like to install VERITAS Cluster 4.1 on SuSE Linux 10 with SP1 & following is the requirement of the kernel from VERITAS side;
SUSE Linux Enterprise Server 10 with SP1 with following kernel level: 2.6.16-37-0.18-smp/2.6.16-37-0.18-bigsmp
After installing the SuSE 10 with... (1 Reply)
Discussion started by: jumadhiya
1 Replies
4. UNIX for Advanced & Expert Users
I've got a domain running on a few boards of a 25k. I'm seeing very high kernel cpu usage in top and cant' quite explain it. System runs a large number of smallish Oracle 10g2 databases (30), used mainly for development.
load average: 36.63, 36.68, 37.42
2489 processes: 2452 sleeping, 21... (0 Replies)
Discussion started by: utopiajoe
0 Replies
5. UNIX for Dummies Questions & Answers
Hi Gurus
can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC?
regards,
Israel. (9 Replies)
Discussion started by: iga3725
9 Replies
6. Solaris
Hi,
Couple of sentences for background: I'm a software developer, whose task was to create a server software for our customer. Software is ready for deployment and customer has a new T4-1 SPARC, but somehow it also became my task also to setup the server. I have managed to get the server is up... (13 Replies)
Discussion started by: julumme
13 Replies
LEARN ABOUT SUSE
apache::session::lock::semaphore
Session::Lock::Semaphore(3) User Contributed Perl Documentation Session::Lock::Semaphore(3)
NAME
Apache::Session::Lock::Semaphore - Provides mutual exclusion through semaphores
SYNOPSIS
use Apache::Session::Lock::Semaphore;
my $locker = new Apache::Session::Lock::Semaphore;
die "no semaphores" unless $locker;
$locker->acquire_read_lock($ref);
$locker->acquire_write_lock($ref);
$locker->release_read_lock($ref);
$locker->release_write_lock($ref);
$locker->release_all_locks($ref);
DESCRIPTION
Apache::Session::Lock::semaphore fulfills the locking interface of Apache::Session. Mutual exclusion is achieved through system semaphores
and the IPC::Semaphore module.
CONFIGURATION
The module must know how many semaphores to use, and what semaphore key to use. The number of semaphores has an impact on performance.
More semaphores means less lock contention. You should use the maximum number of semaphores that your platform will allow. On stock NetBSD,
OpenBSD, and Solaris systems, this is probably 16. On Linux 2.2, this is 32. This module tries to guess the number based on your operating
system, but it is safer to configure it yourself.
To set the number of semaphores, you need to pass an argument in the usual Apache::Session style. The name of the argument is NSems, and
the value is an integer power of 2. For example:
tie %s, 'Apache::Session::Blah', $id, {NSems => 16};
You may also need to configure the semaphore key that this package uses. By default, it uses key 31818. You can change this using the
argument SemaphoreKey:
tie %s, 'Apache::Session::Blah', $id, {NSems => 16, SemaphoreKey => 42};
PROBLEMS
There are a few problems that people frequently encounter when using this package.
If you get an invalid argument message, that usually means that the system is unhappy with the number of semaphores that you requested.
Try decreasing the number of semaphores. The semaphore blocks that this package creates are persistent until the system is rebooted, so if
you request 8 semaphores one time and 16 semaphores the next, it won't work. Use the system commands ipcs and ipcrm to inspect and remove
unwanted semphore blocks.
Cygwin
IPC on Cygwin requires running cygserver. Without it, program will exit with "Bad System call" message. It cannot be intercepted with eval.
Read /usr/share/doc/Cygwin/cygserver.README for more information.
Darwin/MacOS X
Darwin and MacOS X may not have semaphores, see <http://sysnet.ucsd.edu/~bellardo/darwin/sysvsem.html>
*BSD
Error "No space left on device" means that maximum number of semaphores is reached. See
http://www.postgresql.org/docs/7.3/static/kernel-resources.html <http://www.postgresql.org/docs/7.3/static/kernel-resources.html> for more
information.
AUTHOR
This module was written by Jeffrey William Baker <jwbaker@acm.org>.
SEE ALSO
Apache::Session
perl v5.12.1 2008-04-30 Session::Lock::Semaphore(3)