John Reiser (jreiser@xxxxxxxxxxxx) said: > If the problem is a failed system call, then print the name of the > system call, the errno, and the error string. (Even without national > language support, for instance.) If the problem lies with a file or > directory, then include the literal pathname which failed. I spent > many hours chasing a missing file whose name did not appear in > any message. The snippet you quoted *does* print strerror(errno)... there are various other errors that the SELinux routines catch, but they aren't propagated up in any way that that patch could catch. Bill -- fedora-selinux-list mailing list fedora-selinux-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-selinux-list
