Roland Mainz <roland.mainz at nrubsig.org> wrote:
> The problem is that the Solaris 10 version of |libc::vfork()| (the
> public function, not the internal |_vfork()|) is 100% identical to
> |fork()|. AFAIK all consumers who previously used the
> |vfork();exec()|-sequence should now use |posix_spawn()| instead
> (otherwise some performance gets lost).
This is obviously wrong:
[6353] | 655488| 215|FUNC |GLOB |0 |11 |_vfork
[5907] | 655488| 215|FUNC |WEAK |0 |11 |vfork
[5245] | 0| 0|FILE |LOCL |0 |ABS |vfork.s
> Another problem is that we'd like to make libshell threadsafe (yes, I
> know, things like the process's current working directory still need
> something like a "global lock") in the future and this issue may then
> really hurt (ksh93/libdll uses the dynamic linker for builtins) ...
Doing this is a really big task. Why do you like to do this?
J?rg
--
EMail:joerg at schily.isdn.cs.tu-berlin.de (home) J?rg Schilling D-13353 Berlin
js at cs.tu-berlin.de (uni)
schilling at fokus.fraunhofer.de (work) Blog:
http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
