Re: Inappropriate ioctl for device

should I be concerned about this error?

No. Not every failing system call is indicative of a problem. In fact, it's pretty normal to see many system calls return with an error code. In many cases it's faster/easier/the-only-way to just make the call and react appropriately, rather than trying to determine beforehand whether the call would fail... (it's kinda like simply asking the question, instead of "May I ask a question?", followed by the question if you get "Yes" :)

Comment on Re: Inappropriate ioctl for device

Replies are listed 'Best First'.
Re^2: Inappropriate ioctl for device by MidLifeXis (Monsignor) on Jul 21, 2008 at 16:29 UTC
Additionally, if you ask if you can ask a question and then ask, there is a race condition where the ability to ask the question may change, so you have to check the response code anyway. --MidLifeXis	[reply]
Re^2: Inappropriate ioctl for device by Bloodnok (Vicar) on Jul 22, 2008 at 11:36 UTC
... for a simple example of this (an abundance of not entirely unexpected errors), you only have to trace a perl script that 'use'es a module from a non-standard location - you'll see any amount of `ENOEXIST` errors before perl manages to locate and open the 'use'd module. At last, a user level that overstates my experience :-))	[reply] [d/l]