Sponsored Content
Operating Systems Solaris Application not working in multi core platform Post 302911828 by achenle on Sunday 3rd of August 2014 10:52:36 PM
Old 08-03-2014
It would also help if you would describe the problems you have in a multi-core environment.

What could be causing the problem? Anything and everything, unfortunately. It all depends on how your application code is written.

Do you know what "reentrant" means? If not, you shouldn't be writing multithreaded code.

Although I would like to know how much use your application makes of static variables.
 

3 More Discussions You Might Find Interesting

1. Programming

Multi-platform includes?

I know that <cstudio> can also be <stdio> and can be written different ways on Linux then with windows. I've see some code doing a IFDEF __APPLE__ (I'm guessing, if compiled on a mac do whats between this) Is there one for Linux/Window? (3 Replies)
Discussion started by: james2432
3 Replies

2. UNIX for Advanced & Expert Users

Multi-platform Centralized Patch Management

We have a mix of AIX, HP-UX, Linux (RHEL and SLES), and Solaris in our environment. Currently we have seperate patch management systems for each platform (NIM, SD, Spacewalk, etc), but have started looking for a centralized patch management solution that would work for most, if not all, of our... (0 Replies)
Discussion started by: kknigga
0 Replies

3. Shell Programming and Scripting

Multi platform script perl or awk

Hi gurus, I am trying to match records in following format: (-,username,domain1.co.uk)\ (-,username,domain2.co.uk) either awk or perl must be used. I am using cygwin. I wrote following code which works and matches both above entries: awk 'BEGIN {musr="(-,username,+.co.uk)"} {if... (8 Replies)
Discussion started by: wakatana
8 Replies
getprotoent(3N) 														   getprotoent(3N)

NAME
getprotoent(), getprotobynumber(), getprotobyname(), setprotoent(), endprotoent() - get, set, or end protocol entry SYNOPSIS
_XOPEN_SOURCE_EXTENDED only DESCRIPTION
The and functions each return a pointer to a structure of type protoent containing the broken-out fields of a line in the network protocol data base, The members of this structure are: The official name of the protocol. A null-terminated list of alternate names for the protocol. The protocol number. Functions behave as follows: Reads the next line of the file, opening the file if necessary. Opens and rewinds the file. If the stayopen flag is non-zero, the protocol data base is not closed after each call to (either directly or indirectly through one of the other calls). Closes the file. Each sequentially searches from the beginning of the file until a matching protocol name (among either the official names or the aliases) or protocol number is found, or until EOF is encountered. In a multithreaded application, and use thread-specific storage that is re-used in each call. The return value should be unique for each thread and should be saved, if desired, before the thread makes the next call. For enumeration in multithreaded applications, the position within the enumeration is a process-wide property shared by all threads. may be used in a multithreaded application, but resets the enumeration position for all threads. enumerates protocol entries: successive calls to will return either successive protocol entries or NULL. If multiple threads interleave calls to the threads will enumerate disjoint subsets of the protocol database. If the system is running the Network Information Service (NIS), and get the protocol information from the NIS server (see ypserv(1M) and ypfiles(4)). Name Service Switch-Based Operation The library routines and their reentrant counterparts, internally call the name service switch to access the "protocols" database lookup policy configured in the file (see nsswitch.conf(4)). The lookup policy defines the order and the criteria of the supported name services used to resolve protocol names and numbers. RETURN VALUE
and return a null pointer(0) on EOF or when they are unable to open OBSOLESCENT INTERFACES
The above reentrant interfaces have been moved from to They are included to support existing applications and may be removed in a future release. New multithreaded applications should use the regular APIs without The reentrant interfaces performs the same operation as their regular counterpart (those without the suffix.) However, and expect to be passed the address of a parameter and will store the address of the result at this supplied parameter. An additional parameter, an address to struct protoent_data, which is defined in the file cannot be a NULL pointer. The reentrant routines return if the operation is unsuccessful, or, in the case of if the end of the services list has been reached. is returned otherwise. EXAMPLES
The following code excerpt counts the number of protocols entries: WARNINGS
Programs that use the interfaces described in this manpage cannot be linked statically because the implementations of these functions employ dynamic loading and linking of shared objects at run time. AUTHOR
was developed by Sun Microsystems Inc. FILES
SEE ALSO
ypserv(1M), nsswitch.conf(4), protocols(4), ypfiles(4), thread_safety(5). STANDARDS CONFORMANCE
getprotoent(3N)
All times are GMT -4. The time now is 09:54 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy