Error output of cat to /dev/null Post: 302493929

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

error piping nohup to /dev/null

Hi, I have a script as follows: #!/bin/sh nohup ./my_program >& /dev/null & However, i get a "Generated or received a file descriptor number that is not valid" whenever I run it. running the command up in prompt is ok though. if i change the first line to #!/bin/csh i get a then:...

2. Solaris

URGENT - setup port and dump all output to /dev/null or a file

Please help urgently. I need to setup up some sort of service on a solaris server on a port. I dont need it do anything special, anything that is sent to this port from an external server should be dump to /dev/null or a flat file.. Can you help urgently?

3. Solaris

What is /dev/tty /dev/null and /dev/console

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 ??

4. UNIX for Dummies Questions & Answers

cat /dev/null

Hi, Excuse my ignorance here - I'm a networks man and my knowledge of all things unix is somewhat limited. We have a very large file (/var/tmp/mond.log) that we need to zero - does the "cat /dev/null > /var/tmp/mond.log" command achieve this?

5. UNIX for Dummies Questions & Answers

cp output /dev/null results in not a directory

Hello, I am working on a script to measure the read performance of a busybox environment. The logical choice is to use a command line like: (time cp * /dev/null) 2> /tmp/howlong.txt Ah, the rub is cp or /dev/null will only accept a single file at a time. The result in the txt file is and...

6. Ubuntu

tar not reading if output directed to /dev/null

I stumbled across a somewhat strange behavior of tar and find no explanation for it: i was testing a DVD for read errors and thought to simply tar the content and direct the output to /dev/null: tar -cvf - /my/mountpoint/*ts > /dev/null This way i expected the system to read the complete...

7. UNIX for Dummies Questions & Answers

/dev/null 2>&1 Versus /dev/null 2>1

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

8. HP-UX

/dev/Null error

Hi Guru's, I am trying to test the network speed or load by this command. but getting error " Not Connected ". Could you guys please help. ftp> put "|dd if=/dev/zero bs=8k count=1000000" /dev/null Not connected. Please use code tags!

9. Shell Programming and Scripting

Redirecting standard out to /dev/null goes to file "/dev/null" instead

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:...

10. Shell Programming and Scripting

redirect the audio output to /dev/null

I'm using an text-to-speech synthesis in a script, and I need to redirect it's output to /dev/null how can I do that ? And how to redirect the stream to his normal output then （sound card ) ? thankx

LEARN ABOUT DEBIAN

apsfilter-bug

APSFILTER-BUG(1)					    BSD General Commands Manual 					  APSFILTER-BUG(1)

NAME

     apsfilter-bug -- create a half-automatic bug report for apsfilter

SYNOPSIS

     apsfilter-bug

OPTIONS

     none

DESCRIPTION

     With the apsfilter-bug script you can automatically create a bug report for apsfilter(1).	A template report file is created which you can
     edit with your favourite editor ( emacs(1) by default, or whatever is entered in the environment variable EDITOR ).

     You will see a couple of lines starting with '#'; these lines will be removed before the report is sent. So if you want to use the '#' char-
     acter at the beginning of a line, just indent it with a space.

     A very important piece of the bug report is the debugging log created by aps2file(1), probably with a command like
	   aps2file -D -o /dev/null [-P...] [-Z...] [input] 2> log.txt
     Unless you don't even have a chance to create a debugging log, it is crucial for serious bug hunting.

     After you have filled in as much (useful) information as possible, you must save the file under its original name, then exit your editor.

     If you invoked apsfilter-bug by accident, or if you need some additional system information to include into the bug report, just exit your
     editor without saving the file.

NOTES

     In addition to the stuff you've edited, some more information is appended to the bug report automatically:

     apsfilter version	  7.2.6-stable
     ghostscript version  (from 'gs --version')
     system id		  (from 'uname -a')
     configure options	  --prefix=/usr --sysconfdir=/etc --mandir=/usr/share/man --with-awk=/usr/bin/awk --with-sendmail=/usr/sbin/sendmail
     shell executable	  /bin/bash
     awk executable	  /usr/bin/awk
     sendmail executable  /usr/sbin/sendmail

FILES

     /usr/bin/aps2file	script to create debugging output

SEE ALSO

     apsfilter(1), aps2file(1)

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 apsfilter-bug manpage has been written by Michael LoBin <phallobst@web.de> and first appeared in apsfilter V 7.1.0.

BSD
								   Dec 26, 2001 							       BSD

10 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

error piping nohup to /dev/null

Discussion started by: mochi

2. Solaris

URGENT - setup port and dump all output to /dev/null or a file

Discussion started by: frustrated1

3. Solaris

What is /dev/tty /dev/null and /dev/console

Discussion started by: civic2005

4. UNIX for Dummies Questions & Answers

cat /dev/null

Discussion started by: freakydancer