That's not something one is supposed to take advantage of! >From vfork(2) (albeit admittedly the SX version of the man page): The vfork() function is deprecated. Its sole legitimate use as a prelude to an immediate call to a function from the exec family can be achieved safely by posix_spawn(3C) or posix_spawnp(3C).
Note the words "sole legitimate use". Even the Solaris 8 version of vfork(2) has some things to say about taking advantage of its odd side-effects: The use of vfork() for any purpose other than as a prelude to an immediate call to a function from the exec family or to _exit() is not advised. The vfork() function is unsafe in multithreaded applications. This function will be eliminated in a future release. The memory sharing semantics of vfork() can be obtained through other mechanisms. Also, for Solaris 8 (or anything prior to Solaris Express), you should be using (a) a paid support contract (Sun has to stay in business, right?) or (b) some forum appropriate to Solaris in general, like the Usenet newsgroup comp.unix.solaris. Having said that, I'm not aware that vfork() had suddenly become like fork(), so it's not necessarily uninteresting what you're saying. But I'm not familiar with this, nor having much luck spotting it in the bug database. How about providing some sample code that reproduces the problem? This message posted from opensolaris.org _______________________________________________ opensolaris-discuss mailing list [email protected]
