I disagree with Corona688. Being in the foreground or background shouldn't affect what ioctl's a device supports.
It is my belief that the cause of the malfunction is that STDIN is not a terminal because the shell is redirecting STDIN from /dev/null when it runs the process (or pipeline) in the background.
Quote:
Originally Posted by POSIX
The standard input for an asynchronous list, before any explicit redirections are performed, shall be considered to be assigned to a file that has the same properties as /dev/null. If it is an interactive shell, this need not happen. In all cases, explicit redirection of standard input shall override this activity.
I don't know what system you're running, but on a circa 2007 Debian Linux install, /usr/include/asm-generic/errno-base.h (which is the ultimate destination of the #include breadcrumb trail beginning at /usr/include/errno.h) has this to say:
Regards,
Alister
Hi,
We are running a perl script to upload some data using SQL* Loader. We pipe the data in a http request to SQL*Loader which loads the data to the database. We encounter the error "Inappropirate ioctl for device" when we try to upload huge data. Any solution would be greatly appreciated.... (4 Replies)
When I try to format a slice in Solaris 10 I get the follow error :confused: :
-bash-3.00# mkfs /dev/dsk/c1d0s5 18877824
Can not determine partition size: Inappropriate ioctl for device
Some format command output:....
AVAILABLE DISK SELECTIONS:
0. c1d0 <DEFAULT cyl 38735 alt 2... (0 Replies)
Hello,
I have a cron entry:
59 23 * * * . $HOME/.profile;mydate=`date '+%Y%m%d'`;mv filename filename_$mydate
Which works fine interactively, but gives me the following error when it runs in cron:
Your "cron" job on servername
. $HOME/.profile;mydate=`date '+
produced the... (4 Replies)
When I try to format a slice in Solaris 10 I get the follow error :
-bash-3.00# mkfs /dev/dsk/c1d0s5 18877824
Can not determine partition size: Inappropriate ioctl for device
Some format command output:....
AVAILABLE DISK SELECTIONS:
0. c1d0 <DEFAULT cyl 38735 alt 2 hd 64 sec 63>... (2 Replies)
Dear all,
Problem goes like this:
I have a shell script which when run manually runs perfectly.
When same script is executed through a job schdeduler I get an error as Inappropriate ioctl for device and the script fails.
This problems seems quite guiling to me.
Any clues are heartly... (11 Replies)
Hello guys,
on my Red Hat machine the /bin/mt status command gives the output dev/tape: inappropriate ioctl for device. This messages comes up after the Server has been rebooted.
Anybody an idea?
Thx
masterofdesaster (8 Replies)
Hi All,
Am finding performance of my SD card using hdparm.
Code:
hdparm -tT /dev/BlockDev0
/dev/BlockDev0:
Timing cached reads: 1118 MB in 2.00 seconds = 558.61 MB/sec
HDIO_DRIVE_CMD(null) (wait for flush complete) failed: Inappropriate
ioctl for device
Timing buffered disk... (1 Reply)
Hello everyone
I am finishing a script allowing me to purge logs on multiple servers, i have one last pb with the ssh command.........it is throwing me the following error :
tcgetattr: Inappropriate ioctl for device (full screen in attached file 1, full script in attached file 2)
It... (15 Replies)
Hi!
I am getting a nohup issue on mac osx while trying to start a process through nohup in the startup script.
nohup: can't detach from console: Inappropriate ioctl for device
Please help!
Thanks,
Allan. (0 Replies)
Hi,
ssh -q -t -l $usr $host bin/test.sh
I am using above command to run script remotely. script is working without any issues. but I am getting "tcgetattr: Inappropriate ioctl for device" message on console.
plz help how can I avoid this message.
Thanks
Moved thread from Emergency... (1 Reply)
Discussion started by: Kri
1 Replies
LEARN ABOUT V7
init
INIT(8) System Manager's Manual INIT(8)NAME
init, rc - process control initialization
SYNOPSIS
/etc/init
/etc/rc
DESCRIPTION
Init is invoked as the last step of the boot procedure (see boot(8)). Generally its role is to create a process for each typewriter on
which a user may log in.
When init first is executed the console typewriter /dev/console. is opened for reading and writing and the shell is invoked immediately.
This feature is used to bring up a single-user system. If the shell terminates, init comes up multi-user and the process described below
is started.
When init comes up multiuser, it invokes a shell, with input taken from the file /etc/rc. This command file performs housekeeping like
removing temporary files, mounting file systems, and starting daemons.
Then init reads the file /etc/ttys and forks several times to create a process for each typewriter specified in the file. Each of these
processes opens the appropriate typewriter for reading and writing. These channels thus receive file descriptors 0, 1 and 2, the standard
input, output and error files. Opening the typewriter will usually involve a delay, since the open is not completed until someone is
dialed up and carrier established on the channel. Then /etc/getty is called with argument as specified by the last character of the ttys
file line. Getty reads the user's name and invokes login(1) to log in the user and execute the shell.
Ultimately the shell will terminate because of an end-of-file either typed explicitly or generated as a result of hanging up. The main
path of init, which has been waiting for such an event, wakes up and removes the appropriate entry from the file utmp, which records cur-
rent users, and makes an entry in /usr/adm/wtmp, which maintains a history of logins and logouts. Then the appropriate typewriter is
reopened and getty is reinvoked.
Init catches the hangup signal SIGHUP and interprets it to mean that the system should be brought from multi user to single user. Use
`kill -1 1' to send the hangup signal.
FILES
/dev/tty?, /etc/utmp, /usr/adm/wtmp, /etc/ttys, /etc/rc
SEE ALSO login(1), kill(1), sh(1), ttys(5), getty(8)INIT(8)