02-07-2019
It seems it happened again. I tried again to post my bug report. I assume it has to do with this special subforum and my user.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
My home PC is dual boot with Linux and Win98. I want to upgrade both to a newer version, and have the Linux CD's now. What I need to know is does Win2K Pro stomp (write over LiLo) on the boot record like NT (2 Replies)
Discussion started by: 98_1LE
2 Replies
2. UNIX for Advanced & Expert Users
Hi all,
How can I get the list of all Threads and the Total count of threads under a particular process ?
Do suggest !!
Awaiting for the replies !!
Thanks
Varun:b: (2 Replies)
Discussion started by: varungupta
2 Replies
3. Programming
I am looking for C program source code. Could you please help me in finding the source code required mentioned below.
program to create multiple threads (one master thread and rest worker threads) and using the threads write into and read from shared memory
Restrictions:
Only one thread... (2 Replies)
Discussion started by: kumars
2 Replies
4. Shell Programming and Scripting
hi friends
well m facing a different sort of issue in my cron.
i hav set job like this
30 09 * * 1 /bin/backup14M
01 14 * * 1 /bin/backup14N
20 18 * * 1 /bin/backup14E
that is for every Monday at three different times.
but, first job executes well, later ones do not. I checked my... (13 Replies)
Discussion started by: oracle.test2
13 Replies
5. Shell Programming and Scripting
Hi,
I'm looking to create a script which will find all the files created in the last 24h in a directory starting with a few different letters and send them to the printer. This would be run through the cron each morning to print the last 24 hours files.
I have started with this to find all... (2 Replies)
Discussion started by: rab
2 Replies
6. Shell Programming and Scripting
I was trying to write a script that will process recently creatd file.
From below, the script should process input_20111230.dat file.
sam:/top/work/data/input: ls -ltr input_*.dat
-rw-rw-rw- 1 work edprod 455668 Dec 24 09:16 input_20111224.dat
-rw-r--r-- 1 work edprod ... (7 Replies)
Discussion started by: siteregsam
7 Replies
7. Forum Support Area for Unregistered Users & Account Problems
I'm getting the following error (or something similar) whenever I try to view a thread when I'm logged in.
That is, I login, hit "New Posts", get a list of theads, click on one (in this example is was the "Not allowed to post URLs" thread), then get the following HTML error page instead of the... (1 Reply)
Discussion started by: cnamejj
1 Replies
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)