Sponsored Content
Top Forums UNIX for Advanced & Expert Users solaris 8 sparc kernel configuration guide Post 38609 by thehoghunter on Monday 21st of July 2003 02:50:23 PM
Old 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

Linux Kernel configuration (laptop)

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

Need help on Kernel Configuration for FreeBSD

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

SuSE Linux Kernel & Veritas MultiNIC Configuration...!!!

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

Extremely high kernel CPU Usage (Solaris 10 SPARC)

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

can I emulate solaris/sparc on virtualbox? Or other emulator to run solaris for sparc in my win7 PC?

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

SPARC T4-1/Solaris 11/Add 2 new HDDs in RAID 0 configuration

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
SEM_OVERVIEW(7) 					     Linux Programmer's Manual						   SEM_OVERVIEW(7)

NAME
sem_overview - overview of POSIX semaphores DESCRIPTION
POSIX semaphores allow processes and threads to synchronize their actions. A semaphore is an integer whose value is never allowed to fall below zero. Two operations can be performed on semaphores: increment the semaphore value by one (sem_post(3)); and decrement the semaphore value by one (sem_wait(3)). If the value of a semaphore is currently zero, then a sem_wait(3) operation will block until the value becomes greater than zero. POSIX semaphores come in two forms: named semaphores and unnamed semaphores. Named semaphores A named semaphore is identified by a name of the form /somename; that is, a null-terminated string of up to NAME_MAX-4 (i.e., 251) characters consisting of an initial slash, followed by one or more characters, none of which are slashes. Two processes can operate on the same named semaphore by passing the same name to sem_open(3). The sem_open(3) function creates a new named semaphore or opens an existing named semaphore. After the semaphore has been opened, it can be operated on using sem_post(3) and sem_wait(3). When a process has finished using the semaphore, it can use sem_close(3) to close the semaphore. When all processes have finished using the semaphore, it can be removed from the system using sem_unlink(3). Unnamed semaphores (memory-based semaphores) An unnamed semaphore does not have a name. Instead the semaphore is placed in a region of memory that is shared between multiple threads (a thread-shared semaphore) or processes (a process-shared semaphore). A thread-shared semaphore is placed in an area of memory shared between the threads of a process, for example, a global variable. A process-shared semaphore must be placed in a shared memory region (e.g., a System V shared memory segment created using shmget(2), or a POSIX shared memory object built created using shm_open(3)). Before being used, an unnamed semaphore must be initialized using sem_init(3). It can then be operated on using sem_post(3) and sem_wait(3). When the semaphore is no longer required, and before the memory in which it is located is deallocated, the semaphore should be destroyed using sem_destroy(3). The remainder of this section describes some specific details of the Linux implementation of POSIX semaphores. Versions Prior to kernel 2.6, Linux only supported unnamed, thread-shared semaphores. On a system with Linux 2.6 and a glibc that provides the NPTL threading implementation, a complete implementation of POSIX semaphores is provided. Persistence POSIX named semaphores have kernel persistence: if not removed by sem_unlink(3), a semaphore will exist until the system is shut down. Linking Programs using the POSIX semaphores API must be compiled with cc -pthread to link against the real-time library, librt. Accessing named semaphores via the file system On Linux, named semaphores are created in a virtual file system, normally mounted under /dev/shm, with names of the form sem.somename. (This is the reason that semaphore names are limited to NAME_MAX-4 rather than NAME_MAX characters.) Since Linux 2.6.19, ACLs can be placed on files under this directory, to control object permissions on a per-user and per-group basis. CONFORMING TO
POSIX.1-2001. NOTES
System V semaphores (semget(2), semop(2), etc.) are an older semaphore API. POSIX semaphores provide a simpler, and better designed inter- face than System V semaphores; on the other hand POSIX semaphores are less widely available (especially on older systems) than System V semaphores. EXAMPLE
An example of the use of various POSIX semaphore functions is shown in sem_wait(3). SEE ALSO
sem_close(3), sem_destroy(3), sem_getvalue(3), sem_init(3), sem_open(3), sem_post(3), sem_unlink(3), sem_wait(3), pthreads(7) COLOPHON
This page is part of release 3.44 of the Linux man-pages project. A description of the project, and information about reporting bugs, can be found at http://www.kernel.org/doc/man-pages/. Linux 2012-05-13 SEM_OVERVIEW(7)
All times are GMT -4. The time now is 04:37 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy