RE: thread-private working directory

["Jason Zions" <yyyyyyyy@xxxxxxxxxxxxxxxxxxx>]

Excellent. Existing industry practice. If you're serious, I'd start
here. 

-----Original Message-----
From: Markus Gyger [mailto:yyyyyy@xxxxxxxxx] 
Sent: Monday, August 04, 2003 4:23 PM
To: Jason Zions
Cc: Marcus Brinkmann; s lurndal; Kaz Kylheku; Alexander Terekhov;
yyyyyyyyyyyyyyyyyyyyyy@xxxxxxxxxxxxx; yyyyyyyyyyyyyy@xxxxxxxxxxxxx
Subject: Re: thread-private working directory

Jason Zions writes:
> Are you guys seriously suggesting a new family of API calls (one for 
> every call that takes a pathname) to specify the directory to which a 
> relative path is in fact relative simply to handle some very obscure 
> corner cases that can't be addressed by the use of absolute paths?

Solaris 9 does have some of them. Extracts from the fsattr(5) man page:

  int openat(int fd, const char *path, int oflag [, mode_t mode])

  The openat(2) function behaves exactly as open(2) except when given
  a relative path. Where open() resolves a relative path from the
  current working directory, openat() resolves the path based on the
  vnode indicated by the supplied file descriptor.
  [...]
  If openat() is passed the special value AT_FDCWD as its first (fd)
  argument, its behavior is identical to open() and the relative path
  arguments are interpreted relative to the current working directory.
  [...]

For full man page see http://docs.sun.com/doc/816-0220/6m6nkorp9?a=view


Markus