Hi all,
I have the following script:
-------------------------------------------------
#SCRIPT TO CHECK WHO HAS ACCESSED THE LOG/FILE IN PAST 'N' MINUTES, AND MAIL ACCORDINGLY.
MYPATH="/clocal/mqbrkrs/user/mqsiadm/sanjay/"
MAIL_RECIPIENTS="vg517@dcx.com"
Subject="File accessed in last... (6 Replies)
Hi friends
I am facing one problem while redirecting the out of the stderr and stdout to a file
let example my problem with a simple example
I have a file (say test.sh)in which i run 2 command in the background
ps -ef &
ls &
and now i am run this file and redirect the output to a file... (8 Replies)
Hi
I am not if this is possible: is it possible in bach (or another shell) to redirect GLOBALLY the stdout/stderr channels to a file.
So, if I have a script
script.sh
cmd1
cmd2
cmd3
I want all stdout/stderr goes to a file. I know I can do:
./script.sh 1>file 2>&1
OR
... (2 Replies)
Hi,
I would like to avoid re-directing line by line to a file.
What is the best way to re-direct STDOUT to a file in a subshell?
Thanks in advance.
Cheers
Vj (1 Reply)
Hello
I read a lot of post related to this topic, but nothing helped me. :mad:
I'm running a ksh script with subshell what processing some ldap command. I need to check output for possible errors.
#!/bin/ksh
...
readinput < $QCHAT_INPUT |&
while read -p line
do
echo $line
... (3 Replies)
Hi All,
I am using centOS.
When I try to redirect STDOUT to a file, it ends up in getting some funny characters. For example ...
STDOUT of the command as follows.
$ ls
H3k27me3
H3k36me3
H3k4me1
H3k4me2
H3k4me3
H3k9ac
H4k20me1
$ ls >test
$ cat test
^ (1 Reply)
Dear all,
redirecting STDOUT & STDERR to file is quite simple, I'm currently using:
exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.logBut during script execution I would like the output come back again to screen, how to do that?
Thanks
Lucas (4 Replies)
I am looking for a way to redirect standard output to a file from a C-code;
so, any 'cout<<..' or 'printf(...)' will be written into a file.
I have a server source that I need to debug.
That program called by RPC (remote procedure call) and has no any session to print out anything.
I have... (3 Replies)
Dear all,
redirecting STDOUT & STDERR to file is quite simple, I'm currently using:
Code:
exec 1>>/tmp/tmp.log; exec 2>>/tmp/tmp.log
But during script execution I would like the output come back again to screen, how to do that?
Thanks
Luc
edit by bakunin: please use CODE-tags like the... (6 Replies)
Discussion started by: tmonk1
6 Replies
LEARN ABOUT DEBIAN
apspreview
APSPREVIEW(1) BSD General Commands Manual APSPREVIEW(1)NAME
apspreview -- preview PostScript file(s) as generated by apsfilter
SYNOPSIS
apspreview [-Pqueue] [-Zoptions] [input...]
apspreview [-h]
DESCRIPTION
With apspreview you can create a PostScript representation of the file(s) you are about to print in order to check it before actually print-
ing.
Your file(s) will be converted to PostScript according to the queue specific configuration, and afterwards you will be able to print all or
some pages from your PostScript viewer application (gv, kghostview or ghostview).
OPTIONS -h show help screen
-Pqueue select a printer queue (different from the default one)
-Zoptions use apsfilter command line options (comma-separated list)
input... input file(s) [default: stdin]
NOTES
If you use the -P option, please remember to pass the same printer queue on to the lpr(1) command.
Be careful if your printer queue configuration includes a setting to create multiple pages per sheet (PS_NUP=2, PS_NUP=4 or PS_NUP=8). In
order to make sure that apsfilter(1) does not repeat n-up printing, use the 1pps command line option when actually printing the file.
apspreview only works correctly with entries in /etc/printcap that have been created by /usr/share/apsfilter/SETUP. All configuration set-
tings will be copied from the relevant apsfilterrc files.
FILES
/etc/printcap printer capability data base
/usr/share/apsfilter/bin/apsfilter apsfilter script
/usr/bin/aps2file tool to save apsfilter output to a file
SEE ALSO apsfilter(1), aps2file(1), apsfilter-bug(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 apspreview manpage has been written by Michael LoBin <phallobst@web.de> and first appeared in apsfilter V 7.1.0.
BSD Dec 27, 2001 BSD