| To: | Alexander Terekhov <yyyyyyyy@xxxxxxxxxx> |
|---|---|
| Subject: | Re: thread-private working directory |
| From: | Harti Brandt <yyyyyy@xxxxxxxxxxxxxxxxxxx> |
| Date: | Fri, 1 Aug 2003 15:25:19 +0200 (CEST) |
| Cc: | yyyyyyyyyyyyyyyyyyyyyy@xxxxxxxxxxxxx |
| References: | <OFB7D492BD.64512203-ONC1256D75.0048EE46-C1256D75.00492B68@de.ibm.com> |
On Fri, 1 Aug 2003, Alexander Terekhov wrote: AT>Harti Brandt wrote: AT>[...] AT>> I wonder how one would implement a per-thread current directory AT>> in an environment where there is no 1:1 mapping between user AT>> threads and kernel threads. AT> AT>Something similar to (but probably a bit less convoluted ;-) ) AT>a per-thread signal mask, I guess. AT> AT>> While I could think of ways, they seem too convoluted to me. Given that I have only one per-process current working directory this would force me to intercept all systemcalls that contain pathnames and fiddle with these, doesn't it? harti -- harti brandt, http://www.fokus.fraunhofer.de/research/cc/cats/employees/hartmut.brandt/private yyyyyy@xxxxxxxxxxxxxxxxxxx, yyyyy@xxxxxxxxxxx |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: thread-private working directory, Alexander Terekhov |
|---|---|
| Next by Date: | Re: thread-private working directory, Dave Butenhof |
| Previous by Thread: | Re: thread-private working directory, Alexander Terekhov |
| Next by Thread: | Re: thread-private working directory, Dave Butenhof |
| Indexes: | [Date] [Thread] [All Lists] |