Re: [osol-code] Is mkstemp() thread-safe?

A follow up question to the thread-safety issue. For a single PID is 26 the maximum number of files that can be opened before the open will fail and return a -1 for all subsequent files? david. This message posted from opensolaris.org ___ opensola

[osol-code] Is mkstemp() thread-safe?

I've looked at the code for mkstemp() and it looks thread-safe, but the man pages (at least for Solaris 8 and Solaris 10) don't mention if it is or isn't thread-safe. (The man pages should be updated.) The way the code is written if more than 1 thread calls mkstemp() at the same time, and the

[osol-code] Re: xdrrec_create() handle parameter

Thanks Mike, I'll try there. david. This message posted from opensolaris.org ___ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code

[osol-code] xdrrec_create() handle parameter

What is the correct way to pass in the "handle" parameter to xdrrec_create()? I've seen examples such as: ... ... XDR *xdrs = (XDR *)malloc(sizeof(XDR)); memset(xdrs, 0, sizeof(XDR)); ... xdrrec_create(&xdrs, 0, 0, (char *)xdrs, readFunc, writeFunc); ... ... Note that the xdrs variable is being

[osol-code] Is xdr_opaque safe in a multi-threaded environment?

According to the man pages the MT-Level of xdr_opaque() is "Safe" and not "MT-Safe". If I have multiple threads that each create their own XDR stream using xdrrec_create() and the buffer for each stream is tied to a separate socket is it safe to be calling xdr_opaque() at the same time from eac

[osol-code] Is the cplus_demangle call mt-safe or async-signal-safe

Is the cplus_demangle call multi-thread safe or async-signal safe? The man pages don't indicate that it is. David. This message posted from opensolaris.org ___ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.