> >On Thu, 22 Apr 2010 23:07:55 -0700 Alan Coopersmith wrote: >> > can you point me to getcwd(2) or the place in getcwd(3) >> > where it mentions the system call > >> The system call is a private implementation detail of the libc function. >> Documenting how getcwd gets the information is not necessary for you to >> be able to use it correctly and safely. (System calls on Solaris are >> generally private implementation details, subject to change without >> warning, and you should always call the libc functions to access them.) > >thanks >for this particular case "you" is not the typical user > >with the system call possibly getting into library code that I control >I need the implementation details of the system call >e.g., does it implement posix getcwd() semantics w.r.t. >(1) ERANGE
It will return ERANGE when the computed result won't fix in the buffer. >(2) ENAMETOOLONG paths? (using result in chdir(2) gets ENAMETOOLONG) > If the caller calls with a buffer larger than MAXPATHLEN *and* the actual pathname is larger than MAXPATHLEN and it fits the buffer, a pathname larger than MAXPATHLEN will be returned but it won't be accepted by chdir(). Casper _______________________________________________ ksh93-integration-discuss mailing list ksh93-integration-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/ksh93-integration-discuss
