Have I found a bug? Post: 302195368

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Y2.038K bug

Does any1 hav the idea abt wat cause this bug in unix on jan 19th 2038??? please enlighten me abt it....

2. Shell Programming and Scripting

how can i check in csh if command found or not found ?

hello all im trying to use in sun Solaris the information received from the top command now i several machines that dont have install the top program so when im running the script im geting error saying after im running this code : set MemoryInfo = `top | grep Memory` if (...

3. Shell Programming and Scripting

Is it a bug ..?

Hi All, I am using Red Hat Linux on my servers. The problem that I am facing is, sometimes the /opt usage on the server shows used percentage as 100% , when actually it is simply 20%. When I reboot the system, it comes back to 20%.Is this a bug in the system or my settings have gone wrong...

4. AIX

bug in 43 ???

xxxxserver# lsattr -El inet0 | grep 255.240.0.0,32.224.0.0,32.78.120.254 | grep '.40' route net,-hopcount,1,-netmask,255.240.0.0,32.224.0.0,32.78.120.254 How this is possible?

5. UNIX for Dummies Questions & Answers

where's the bug?

#!/bin/bash if then #echo "infinite loop" exit 0 fi when I run this file I get the following error: ./test_infinite_loop: line 5: syntax error near unexpected token `fi' ./test_infinite_loop: line 5: `fi' :confused:

6. Shell Programming and Scripting

mv command not found bug

foreach x ( *.foo) echo "move file?" set move=$< if($move == y) then echo "enter new pathname:" set path=$< mv $x $path/$x endif end ok guys, im creating this script so i can move files with *.foo extensions and *.bar...

7. Programming

is this a bug of g++?

Hello, Im using the g++(g++ Ubuntu/Linaro 4.4.4-14ubuntu5 4.4.5) and im trying to compile a small snippet code and got into an endless loop.I recompiled that in VS2010 under Windows 7 and the answer is as expected.so i wonder is this a bug of g++?here is my code. #include<iostream> using...

8. UNIX for Advanced & Expert Users

Has AudioScope found a bug in bash 4.4.5?

Using AudioScope.sh on Ubuntu 17.04 from a live DVD disc I came across an error. Consider the code below it is a MUCH shortened version of the KEYBOARD input in AudioScope. #!/bin/bash bash --version uname -a status=0 KEYBOARD() { read -r -p "Enter QUIT or EXIT to quit:- " kbinput if ||...

LEARN ABOUT REDHAT

octave-bug

octave-bug(1)						      General Commands Manual						     octave-bug(1)

NAME

       octave-bug - report a bug in GNU Octave

SYNOPSIS

       octave-bug [-s subject]

DESCRIPTION

       octave-bug is a shell script to help the user compose and mail bug reports concerning Octave in a standard format.  octave-bug is typically
       invoked by the Octave command bug_report which is intended to be called interactively from within Octave. This provides	the  best  way	to
       submit  a  bug  report for Octave. It creates a template bug report file and starts an editor on that file.  The bug report will be sent to
       the bug-octave mailing list once the editing has been completed (this assumes of course that your system can use email). However, the  user
       could also call octave-bug outside of Octave.

       Please  read  the `Bugs' chapter in the Octave manual to find out how to submit a bug report that will enable the Octave maintainers to fix
       the  problem.   If  you	are  unable  to  use  the  bug_report  command,  send  your  message  to  the  bug-octave   mailing   list,   bug-
       octave@bevo.che.wisc.edu.

OPTIONS

       -s subject
	      Specify a subject line for the bug report.  Spaces in the subject must be quoted.

ENVIRONMENT VARIABLES

       octave-bug uses the environment variables USER, EDITOR, and PAGER which can be used for customization.

VERSION

       This document was last revised for Octave version 2.0.16.

SEE ALSO

       octave(1), bashbug(1)

AUTHOR

       John W. Eaton
       Department of Chemical Engineering
       University of Wisconsin-Madison
       Madison, WI 53706
       USA
       <jwe@bevo.che.wisc.edu>

GNU
								   6 March 2000 						     octave-bug(1)