Maybe it's an stupid question but remeber... I'm Junior..
I use command line to run programs, and some of them gives a lot of information when, for example, you open a window or other actions. That's really bad because my terminal gets full of unwanted messages, so I use "bin file & >/dev/null"... (1 Reply)
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)
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)
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)
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)
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)
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)
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
LEARN ABOUT OPENSOLARIS
wsdup
wstring(3C) Standard C Library Functions wstring(3C)NAME
wstring, wscasecmp, wsncasecmp, wsdup, wscol - Process Code string operations
SYNOPSIS
#include <widec.h>
int wscasecmp(const wchar_t *s1, const wchar_t *s2);
int wsncasecmp(const wchar_t *s1, const wchar_t *s2, int n);
wchar_t *wsdup(const wchar_t *s);
int wscol(const wchar_t *s);
DESCRIPTION
These functions operate on Process Code strings terminated by wchar_t null characters. During appending or copying, these routines do not
check for an overflow condition of the receiving string. In the following, s, s1, and s2 point to Process Code strings terminated by a
wchar_t null.
wscasecmp(), wsncasecmp()
The wscasecmp() function compares its arguments, ignoring case, and returns an integer greater than, equal to, or less than 0, depending
upon whether s1 is lexicographically greater than, equal to, or less than s2. It makes the same comparison but compares at most n Process
Code characters. The four Extended Unix Code (EUC) codesets are ordered from lowest to highest as 0, 2, 3, 1 when characters from different
codesets are compared.
wsdup()
The wsdup() function returns a pointer to a new Process Code string, which is a duplicate of the string pointed to by s. The space for the
new string is obtained using malloc(3C). If the new string cannot be created, a null pointer is returned.
wscol()
The wscol() function returns the screen display width (in columns) of the Process Code string s.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------------------------------------+
|ATTRIBUTE TYPE ATTRIBUTE VALUE |
|MT-Level MT-Safe |
+-----------------------------------------------------------+
SEE ALSO malloc(3C), string(3C), wcstring(3C), attributes(5)SunOS 5.11 29 Dec 1996 wstring(3C)