The problem is, 'time' is not an external command, it is a builtin, and one that doesn't seem to obey normal redirection either! I had to wrap it in brackets to get the shell to catch it.
Code:
( time wget -q sitename -O /dev/null ) 2> wlog
wget's built-in -q is easier than > /dev/null 2> /dev/null, and -O /dev/null stops it from cluttering your current directory with downloaded files.
thank you!, I may have head of hair left after I finish this script after all
This was driving me nuts! and the -O option is nice.. I was palnning on rm'ing the downloaded file afterwards... now I dont have to.
In bash, I need to send the STDOUT and STDERR from a command to one file, and then just STDERR to another file. Doing one or the other using redirects is easy, but trying to do both at once is a bit tricky. Anyone have any ideas? (9 Replies)
If I forget to set up stderr redirection on execution of a script, is there a way to set that redirection post-exec? In other words, if I have a script running and no errors are being logged... and then I remember that I forgot the 2>&1 on the script... can I turn it on after the fact?
...and... (1 Reply)
Friends
I have to redirect STDERR messages both to screen and also capture the same in a file.
2 > &1 | tee file works but it also displays the non error messages to file, while i only need error messages.
Can anyone help?? (10 Replies)
Doubt regarding using "exec" command to redirect the STDERR to a file. e.g I did it this way.
mystage.sh
#!/bin/sh exec 2>stage.err
....
....
cat stage.err
mv: cannot move `/root/stage' to a subdirectory of itself, `/root/stage_old/stage'
ls: *.zDB: No such file or... (0 Replies)
% ls -ld /usr /foo
ls: /foo: No such file or directory
drwxr-xr-x 14 root wheel 512 May 18 02:49 /usr
% ls -ld /usr /foo 1>/dev/null/
/dev/null/: Not a directory.
% ls -ld /usr /foo 2>/dev/null/
/dev/null/: Not a directory.
^^Why why why doesn't this work for me. Furthermore, where is... (7 Replies)
I am trying to redirect the output from stderr to a log file from within a bash script. the script is to long to add 2> $logfile to the end of each command. I have been trying to do it with the command exec 2> $logfile This mostly works. Unfortunately, when a read command requires that anything be... (5 Replies)
I'm not a complete novice at unix but I'm not all that advanced either. I'm hoping that someone with a little more knowledge than myself has the answer I'm looking for.
I'm writing a wrapper script that will be passed user commands from the cron...
Ex:
./mywrapper.sh "/usr/bin/ps -ef |... (1 Reply)
Hi,
I already searched through the forum and tried to find a answer for my problem but I didn't found a full working solution, thats way I start this new thread and hope, some can help out.
I wonder that I'm not able to find a working solution for the following scenario:
Working in bash I... (8 Replies)
Hi folks
I need/want to redirect output (stdout, stderr) from an exec call to separate files. One for stderr only and two(!) different (!) ones for the combined output of stderr and stdout.
After some research and testing i got this so far :
(( exec ${command} ${command_parameters} 3>&1... (6 Replies)
I know that
mmmmm 2> error.txt
will send the error message to the specified file instead of the screen. However, I have seen
>&2
in some scripts, and I can't get it to do anything. A source said it sends stdout and stderr to a file. What file?
Ubuntu 18.04.2; Xfce 4.12.3;... (11 Replies)
Discussion started by: Xubuntu56
11 Replies
LEARN ABOUT DEBIAN
aps2file
APS2FILE(1) BSD General Commands Manual APS2FILE(1)NAME
aps2file -- printing to a file via apsfilter
SYNOPSIS
aps2file [-D] [-Pqueue] [-Zoptions] [-ooutput] [input]
aps2file [-h]
DESCRIPTION
With aps2file you can direct the printer data generated by apsfilter(1) into an arbitrary file without the use of a spooler.
OPTIONS -h show help screen
-D enable debug mode
-Pqueue select a printer queue (different from the default one)
-Zoptions use apsfilter command line options (comma-separated list)
-ooutput direct data stream to output (default: stdout)
input read data from input (default: stdin)
Unlike printing with lpr(1), you can only use one input file at a time.
Using aps2file is also the recommended way to create a debugging log of a failed printing attempt. If you include the -D flag, the apsfilter
shell script will log every command and print it to stderr. To save the output for inclusion into a bug report, you should therefore use a
command of the sort
aps2file -D -o /dev/null [-P...] [-Z...] [input] 2> log.txt
NOTES
aps2file only works correctly with entries in /etc/printcap that have been created by /usr/share/apsfilter/SETUP.
FILES
/etc/printcap printer capability data base
/usr/share/apsfilter/bin/apsfilter apsfilter script
SEE ALSO apsfilter(1), apsfilter-bug(1), apspreview(1), apsfilterrc(5), printcap(5)BUGS
See apsfilter software center - http://www.apsfilter.org/ - for new versions, bugfixes and known bugs.
Please use the new tool apsfilter-bug(1) to release bug- or problem reports. It automatically presents you a form in an editor window which
asks you some standard questions. If you save and quit the editor session, then this report is sent automatically via e-mail to the proper
apsfilter mailinglist.
If apsfilter fails to print something or prints it in a way you wouldn't expect and you want to report an apsfilter error then please save
the debugging output of one print session using the new aps2file(1) utility by typing aps2file -D -Z options file > /dev/null 2> file.debug
and including the debugging output in the file file.debug into the edit session of the apsfilter-bug utility, so that it is included into the
mail to the apsfilter mailinglist.
Please note that you need to run /bin/sh (Bourne Shell), bash or a compatible shell, so that the above mentioned output redirection works.
Under C-shell (/bin/csh) or tcsh it would't work. If you don't know, then simply make sure you use the Bournce shell by typing /bin/sh or
bash, then you should have no problems with redirection of stdout and stderr (> /dev/null 2> file.debug).
DOCUMENTATION
See official apsfilter homepage
http://www.apsfilter.org/handbook.html Apsfilter Handbook including the Frequently Asked Questions (FAQ)
USER FORUM
Please send questions to the official apsfilter help channel apsfilter-help@apsfilter.org. The above section BUGS and the file
HOWTO-BUGREPORTS tells you how to report bugs. If you want to know how to troubleshoot your apsfilter installation, please read the manpage
aps2file(1) and apsfilter-bug(1) as well as the Apsfilter Handbook carefully.
HISTORY
The aps2file manpage has been written by Michael LoBin <phallobst@web.de> and first appeared in apsfilter V 7.1.0.
BSD Dec 19, 2001 BSD
02-10-2009
