A Snit proc is really just a Tcl proc defined within the type's namespace. You can use procs for private code that isn't related to any particular instance.

snit::type mytype { # Pops and returns the first item from the list stored in the # listvar, updating the listvar proc pop {listvar} { ... } # ... }

None of the files in /proc are really therethey're all, "pretend," files made up by the kernel, to give you information about the system and don't take up any hard disk space. proc/kcore is like an "alias" for the memory in your computer. Its size is the same as the amount of RAM you have, and if you read it as a file, the kernel does memory reads.

So an IMPI job is composed of 1-32 IMPI clients, each of which will have one or more IMPI hosts, each of which will have one or more IMPI procs.

Files in /proc are not really files, they are pseudo files. Kcore can be used to debug the running kernel. The format is similar to a usual core file. You don't have to worry about this file, it will always exist and doesn't indicate any problem. If you use ls, the file will appear to have a size close to the amount of kernel memory in the system. But it does not take up any disk space or memory.

Any name can be used, so long as it does not begin with Snit_; names beginning with Snit_ are reserved for Snit's own use. However, the wise programmer will avoid proc names (set, list, if, etc.) that would shadow standard Tcl command names. proc names, being private, should begin with a capital letter according to convention; however, as there are typically no public procs in the type's namespace it doesn't matter much either way.

snit::type mytype { # Pops and returns the first item from the list stored in the # listvar, updating the listvar proc pop {listvar} { ... } variable requestQueue {} # Get one request from the queue and process it. method processRequest {} { set req [pop requestQueue] } }

The FreeBSD kernel will only allow a certain number of processes to exist at one time. The number is based on the MAXUSERS option in the kernel configuration. MAXUSERS also affects various other in-kernel limits, such as network buffers (see this earlier question). If your machine is heavily loaded, you probably want to increase MAXUSERS. This will increase these other system limit s in addition to the maximum number of processes. After FreeBSD 4.

Section 12- Kernel Programming Questions Answers to common questions about kernel programming details. See also Tigran Aivazian's page on kernel programming.

No, as_fault() is not part of the DDI/DKI. What it does and how it does it may change more or less arbitrarily from minor release to minor release. The only DDI-compliant way to lock down memory is with physio(9F)

quot;Proc" refers to any effect that has a chance to happen. For example, Seal of Light has a chance to heal you on any weapon hit; if you swing your weapon and the Seal actually does heal you, you say that Seal of Light procced. The chance for a paladin seal to proc on a weapon swing depends on the speed of the weapon. Slower weapons will have a higher chance to proc the seal on each swing than faster weapons.

This is related to the fakeinit fiddling that goes on to make the first-process in a context look-like it has pid=1 (pretending to be init, whereas the real pid=1a process is in a different context and so you can't access its resources.

the current proc-fs entries are a read-only representation of what could be set regarding state timeouts. ipvsadm --set will set for IPVS related connection entries

Answer: At the present time, SAS proc surveymeans does not have an option to produce geometric means and their standard errors. However, they can be obtained by running proc surveymeans on the log transformed variables to produce means and standard errors of the log transformed variable, constructing the confidence interval on the log-transformed scale, and then back transforming the endpoints.

The FreeBSD kernel will only allow a certain number of processes to exist at one time. The number is based on the MAXUSERS option in the kernel configuration. MAXUSERS also affects various other in-kernel limits, such as network buffers (see this earlier question). If your machine is heavily loaded, you probably want to increase MAXUSERS. This will increase these other system limits in addition to the maximum number of processes.

Please see the "Robustness" section in the "Understanding session state modes" section of of this article.

Add -p 3 to the yod command. Any size (or sz) parameter now specifies the number of virtual nodes to use. When using NQS, for the -lP parameter, specify 1/2 the number of virtual nodes to be used. NQS allocates physical nodes.

The /proc filesystem is a memory image of each process; it's a virtual filesystem that occupies no disk space. proc is used for programs such as ps(1) and top(public domain) and all the tools in /usr/proc/bin that can be used to examine process state.