On (06/26/07 09:20), Garrett D'Amore wrote: >> What we could do is to have a distinct error code to >> track this case (EINTR?) that could be caught by dladm to emit the >> information to the user- would that suffice? >> > > EAGAIN would be a better choice. >
EAGAIN translates to the perror "No more processes" in errno.h :-( whereas EBUSY is more in line with the update_drv error, which is the closest parallel. --Sowmini
