Web Hosting Forum | Lunarpages


*
Welcome, Guest. Please login or register.
Did you miss your activation email?



Login with username, password and session length
May 24, 2012, 02:42:00 AM

Pages: [1]   Go Down
  Print  
Author Topic: Inappropriate ioctl  (Read 263 times)
esm
Trekkie
**
Offline Offline

Posts: 17


WWW
« on: March 02, 2003, 05:23:00 PM »

I get the following error towards the end of the install of Ikonboard 3.02.

Inappropriate ioctl for device

Support at Lunar Pages suggested I contact Ikonboard as they should be able to help.

Ikonboard says this is a Unix problem and to "send that error report to your host and have them check out their server os and software."

so what's a guy to do...?
Logged

Gene
The older I get, the more I admire competence, just simple competence, in anything from adultery to zoology
stephan
Guest
« Reply #1 on: March 02, 2003, 05:39:00 PM »

Tell them that there is nothing wrong with the host!

Personally, I would use a different message board.

I have setup invisionboard, tforum and phpbb on lunarpages sucessfully.

Hundreds more are compatible. phpBB can be setup from the control panel.
Logged
esm
Trekkie
**
Offline Offline

Posts: 17


WWW
« Reply #2 on: March 02, 2003, 06:03:00 PM »

well, it is classic case of the hardware and software people pointing the finger at the other and neither trying to fix the problem.

I was hoping to save the members and msgs but I may have no choice.

I have been thinking of trying invision board. I have used fudform (http://fud.prohost.org) but it is more technical than it is user friendly.

thanks for the reply
Logged

Gene
The older I get, the more I admire competence, just simple competence, in anything from adultery to zoology
stephan
Guest
« Reply #3 on: March 02, 2003, 06:32:00 PM »

You can get converters to convert your database from one format to another.

That way you could keep all your messages and usernames.

I didn't realise that you had an existing forum already.
Logged
UnmodNick
Intergalactic Superstar
*****
Offline Offline

Posts: 125



WWW
« Reply #4 on: March 02, 2003, 09:40:00 PM »

I am pretty sure this is a Unix problem.. here is some more info:

ioctl(2) - control device

SYNOPSIS
#include <sys/ioctl.h>
int
ioctl(int d, unsigned long request, ...);

DESCRIPTION
The ioctl() function manipulates the underlying device parameters of special files.  In particular, many operating characteristics of character special files (e.g. terminals) may be controlled with ioctl() requests.
The argument d must be an open file descriptor.
The third argument to ioctl is traditionally named char *argp.  Most uses of ioctl in FreeBSD 3.0 however, require the third argument to be a      caddr_t or an int.

An  ioctl request has encoded in it whether the argument is an ``in'' parameter or ``out'' parameter, and the size of the argument argp in
bytes.  Macros and defines used in specifying an ioctl request are located in the file <sys/ioctl.h>.

IMPLEMENTATION NOTES
In the non-threaded library ioctl() is implemented as the ioctl syscall.

In the threaded library, the ioctl syscall is assembled to _thread_sys_ioctl() and ioctl() is implemented as a function which locks d for read and write, then calls _thread_sys_ioctl(). Before returning, ioctl() unlocks d.

RETURN VALUES
If an error has occurred, a value of -1 is returned and errno is set to indicate the error.

ERRORS
ioctl() will fail if:

[EBADF]d is not a valid descriptor.
[ENOTTY]d is not associated with a character special device.
[ENOTTY]The specified request does not apply to the kind of object that the descriptor d references.
[EINVAL]request or argp is not valid.
[EFAULT]argp points outside the process's allocated address space.

SEE ALSO
execve(2), fcntl(2), intro(4), tty(4)
Logged

Pages: [1]   Go Up
  Print  
 
Jump to: