11-21-2003
very simple
mv /path/to/data/'$var1' /path/to/new/location 2>/dev/null
However, it is always a good practice to log all kind of messages in your log. This can help you find if anything is messed up.
I guess you must be knowing about redirection, but still since this question is related to that let me explain what exactly the 2>/dev/null do
well 2 stands for the file descriptor, standard errors. so any errors that are directed to standard error are written in file descriptor 2. by doing 2> you are asking to redirect the standard errors. /dev/null is a null device. so 2>/dev/null is instructing to direct standard errors to a null device instead of the console or your error log
other standard file descriptors are
0 standard output
1 standard input
one more remark i feel "done < /path/to/file/$file1" is redundant, you may discard it as well since you are already doing a "cat < /path/to/file/$file1"
let me make this a bit more straight, (if i havent misinterpreted what you intend to do)
cat /path/to/file/$file1 | while read a
do
mv /path/to/data/"$a" /path/to/new/location 2>/dev/null
echo "Moved File" $a" >>/path/to/file/logs/filesmoved$year$month$day.txt 2>/dev/null
done
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I'm getting an error - symbol referencing errors. No output written to, etc
Can anybody tell me why this is? (2 Replies)
Discussion started by: Dan Rooney
2 Replies
2. AIX
When I try to list a directory that I have been using rsync to copy, I now am getting the following message.
root # ls -alt /directory
ls: /directory: Value too large to be stored in data type.
total 0
I can change directory and list the contents of directories within /directory, but I... (2 Replies)
Discussion started by: sallender
2 Replies
3. Solaris
Hi,
My Solaris 5.8 system keeps getting this error at boot -
"Can't set vol root to /vol"
then
/usr/sbin/vold: can't set vol root to /vol: Resource temporarily unavailiable
Any idea what is wrong, and how do I fix it? (0 Replies)
Discussion started by: ghuber
0 Replies
4. UNIX for Advanced & Expert Users
Hi,
My Solaris 5.8 system keeps getting this error at boot -
"Can't set vol root to /vol"
then
/usr/sbin/vold: can't set vol root to /vol: Resource temporarily unavailiable
Any idea what is wrong, and how do I fix it? (1 Reply)
Discussion started by: ghuber
1 Replies
5. UNIX for Dummies Questions & Answers
I keep getting an error message in a script im writing, this line is allways pointed out.
if
and this is the message i keep getting.
line 32: [: 8: unary operator expected
Whats wrong with it?
Please Help. (5 Replies)
Discussion started by: chapmana
5 Replies
6. Solaris
Hi,
I'm trying to install Solaris 10 on my Ultra 10 but it won't boot. I tried an original cd and a downloaded one. I got the following error:
"error reading sectors" (yes, i checked the md5 sums)
For the complete error see the following shot:
... (2 Replies)
Discussion started by: doelman
2 Replies
7. Linux
Hello
I got this message error on my box with linux red hat
2887a374 WsServer E WSVR0009E: Error occurred during startup
Do you know what does that mean !
Thanks in advance (1 Reply)
Discussion started by: lo-lp-kl
1 Replies
8. UNIX for Dummies Questions & Answers
I am getting a error message when I try to assign this? Can someone help I am new to unix?
$ First-name=james
ksh:First-Name=james not found (1 Reply)
Discussion started by: vthokiefan
1 Replies
9. UNIX for Advanced & Expert Users
Hi - I am getting the error
`Error reading response length from authentication socket'
when I ssh from my cluster to another cluster, and then back to my cluster. It doesn't seem to affect anything, but it's just annoying that it always pops up and tends to confuse new users of the cluster. I... (1 Reply)
Discussion started by: cpp6f
1 Replies
10. SCO
Hello...
i got an error in my SCO OpenServer 6. the error is:
msgcnt 1 vxfs: mesg 016: vx_ilisterr - / file system error reading inode 373
Can anyone help me? (1 Reply)
Discussion started by: AndryMB
1 Replies
LEARN ABOUT FREEBSD
daemon
DAEMON(3) BSD Library Functions Manual DAEMON(3)
NAME
daemon -- run in the background
LIBRARY
Standard C Library (libc, -lc)
SYNOPSIS
#include <stdlib.h>
int
daemon(int nochdir, int noclose);
DESCRIPTION
The daemon() function is for programs wishing to detach themselves from the controlling terminal and run in the background as system daemons.
Unless the argument nochdir is non-zero, daemon() changes the current working directory to the root (/).
Unless the argument noclose is non-zero, daemon() will redirect standard input, standard output, and standard error to /dev/null.
RETURN VALUES
The daemon() function returns the value 0 if successful; otherwise the value -1 is returned and the global variable errno is set to indicate
the error.
ERRORS
The daemon() function may fail and set errno for any of the errors specified for the library functions fork(2) and setsid(2).
SEE ALSO
fork(2), setsid(2), sigaction(2)
HISTORY
The daemon() function first appeared in 4.4BSD.
CAVEATS
Unless the noclose argument is non-zero, daemon() will close the first three file descriptors and redirect them to /dev/null. Normally,
these correspond to standard input, standard output, and standard error. However, if any of those file descriptors refer to something else,
they will still be closed, resulting in incorrect behavior of the calling program. This can happen if any of standard input, standard out-
put, or standard error have been closed before the program was run. Programs using daemon() should therefore either call daemon() before
opening any files or sockets, or verify that any file descriptors obtained have values greater than 2.
The daemon() function temporarily ignores SIGHUP while calling setsid(2) to prevent a parent session group leader's calls to fork(2) and then
_exit(2) from prematurely terminating the child process.
BSD
June 9, 1993 BSD