davecb at canada.sun.com
Fri Mar 10 17:31:46 GMT 2000
James Sutherland wrote:
> Agreed. Essentially, at present crypt() CAN return NULL to us under some
> circumstances, so we MUST handle this gracefully. Either that, or provide
> our own crypt() which does not return NULL under any circumstances?
The spec actually says "Otherwise it returns a null pointer
and sets errno to indicate the error", and the errno
that's expected is ENOSYS, for "I don't have crypt".
As long as an implementor uses a different errno for different
failures, we'll survive it.
David Collier-Brown, | Always do right. This will gratify some people
185 Ellerslie Ave., | and astonish the rest. -- Mark Twain
Willowdale, Ontario | //www.oreilly.com/catalog/samba/author.html
Work: (905) 415-2849 Home: (416) 223-8968 Email: davecb at canada.sun.com
More information about the samba-technical