10-26-2001
Try...
someprog > /dev/null 2>&1 &
...this will run "someprog" in the background with
stdout redirected to /dev/null and stderr redirected to
stdout (now /dev/null)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi ,
I am importing some table from /dev/null i dont understand what is /dev/null
Sorry i am new to UNIX
sam71 (3 Replies)
Discussion started by: sam71
3 Replies
2. UNIX for Advanced & Expert Users
Hi,
Q1-What does
nroff -ms > /dev/null
Q2- What does mean -A under STAT column :
ps aux |head -20
UTIL PID %CPU %MEM SZ RSS TTY STAT STIME TIME COMMAND
root 516 93,0 0,0 12 12 - A 04 nov 3906:51 wait
Thank you. (4 Replies)
Discussion started by: big123456
4 Replies
3. Shell Programming and Scripting
hello all,
In many shell scripts i found '> /dev/null' , i am not able to get this,
will any one please explain why we are using this.
thanks
sudha (2 Replies)
Discussion started by: rrs
2 Replies
4. Solaris
Hi, Anyone can help
My solaris 8 system has the following
/dev/null , /dev/tty and /dev/console
All permission are lrwxrwxrwx
Can this be change to a non-world write ??
any impact ?? (12 Replies)
Discussion started by: civic2005
12 Replies
5. Shell Programming and Scripting
Hi expert,
May I know what is the difference between below cron tab entry ?
0,12 * * * * /abc/myscript.sh > /dev/null 2>&1
0,12 * * * * /abc/myscript.sh (7 Replies)
Discussion started by: olaris
7 Replies
6. Shell Programming and Scripting
when do you use the path /dev/null (3 Replies)
Discussion started by: webmunkey23
3 Replies
7. UNIX for Dummies Questions & Answers
How are these two different? They both prevent output and error from being displayed. I don't see the use of the "&"
echo "hello" > /dev/null 2>&1
echo "hello" > /dev/null 2>1 (3 Replies)
Discussion started by: glev2005
3 Replies
8. Shell Programming and Scripting
I apologize if this question has been answered else where or is too elementary.
I ran across a KSH script (long unimportant story) that does this:
if ; then
CAS_SRC_LOG="/var/log/cas_src.log 2>&1"
else
CAS_SRC_LOG="/dev/null 2>&1"
fithen does this:
/usr/bin/echo "heartbeat:... (5 Replies)
Discussion started by: jbmorrisonjr
5 Replies
9. Shell Programming and Scripting
Hello All and a Happy New year to yous guys.
I'm running the below command on my AIX box and it keeps giving me the message that the file doesn't exist. I know the file don't exist, but I don't want to see the error. 2>/dev/null doesn't work.
bash-3.00$ ls -l C* | wc -l 2>/dev/null
ls:... (2 Replies)
Discussion started by: bbbngowc
2 Replies
10. Shell Programming and Scripting
Friends have the following problem
a search may not find anything which would correct example:
ls -ltr *prueba.txt | nawk '{ print $9 }' > Procesar.dat 2>/dev/null
When he finds nothing gives me the following error
ls: prueba.txt: No such file or directory
because 2> / dev / null... (4 Replies)
Discussion started by: tricampeon81
4 Replies
TTYS(5) File Formats Manual TTYS(5)
NAME
ttys - terminal initialization data
DESCRIPTION
The ttys file contains information that is used by various routines to initialize and control the use of terminal special files. This
information is read with the getttyent(3) library routines. There is one line in the ttys file per special file. Fields are separated by
tabs and/or spaces. Some fields may contain more than one word and should be enclosed in double quotes. Blank lines and comments can
appear anywhere in the file; comments are delimited by `#' and new line. Unspecified fields default to null. The first field is the termi-
nal's entry in the device directory, /dev. The second field of the file is the command to execute for the line, typically getty(8), which
performs such tasks as baud-rate recognition, reading the login name, and calling login(1). It can be, however, any desired command, for
example the start up for a window system terminal emulator or some other daemon process, and can contain multiple words if quoted. The
third field is the type of terminal normally connected to that tty line, as found in the termcap(5) data base file. The remaining fields
set flags in the ty_status entry (see getttyent(3)) or specify a window system process that init(8) will maintain for the terminal line.
As flag values, the strings `on' and `off' specify whether init should execute the command given in the second field, while `secure' in
addition to `on' allows root to login on this line. These flag fields should not be quoted. The string `window=' is followed by a quoted
command string which init will execute before starting getty. If the line ends in a comment, the comment is included in the ty_comment
field of the ttyent structure.
Some examples:
console "/usr/libexec/getty std.1200" vt100 on secure
ttyd0 "/usr/libexec/getty d1200" dialup on # 555-1234
ttyh0 "/usr/libexec/getty std.9600" hp2621-nl on # 254MC
ttyh1 "/usr/libexec/getty std.9600" plugboard on # John's office
ttyp0 none network
ttyp1 none network off
ttyv0 "/usr/new/xterm -L :0" vs100 on window="/usr/new/Xvs100 0"
The first example permits root login on the console at 1200 baud, the second allows dialup at 1200 baud without root login, the third and
fourth allow login at 9600 baud with terminal types of "hp2621-nl" and "plugboard" respectively, the fifth and sixth line are examples of
network pseudo ttys, which should not have getty enabled on them, and the last example shows a terminal emulator and window system startup
entry.
FILES
/etc/ttys
SEE ALSO
login(1), getttyent(3), gettytab(5), init(8), getty(8)
7th Edition November 16, 1996 TTYS(5)