Messages in this thread | | | From | Oliver Neukum <> | Subject | Re: error to be returned while suspended | Date | Tue, 3 Oct 2006 15:02:33 +0200 |
| |
Am Dienstag, 3. Oktober 2006 14:51 schrieb linux-os (Dick Johnson): > > On Tue, 3 Oct 2006, Oliver Neukum wrote: > > > Hi, > > > > which error should a character device return if a read/write cannot be > > serviced because the device is suspended? Shouldn't there be an error > > code specific to that? > > > > Regards > > Oliver > > The de-facto error codes were created long before one could "suspend" > a device, so there isn't a ESUSP code. However, I suggest EIO or EBUSY
CUPS chokes on these. Is it acceptable to say that you should know what you're doing when suspending?
> unless you want to define an ESUSP and get it accepted by the POSIX > committee.
This would be the cleanest solution. How does one do that?
Regards Oliver - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |