Sponsored Content
Contact Us Post Here to Contact Site Administrators and Moderators Stomp has created two threads recently that can't be read Post 303030219 by stomp on Thursday 7th of February 2019 08:09:42 AM
Old 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

Does WIN2K stomp on the boot record like NT?

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

Threads and Threads Count ?

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

shared memory read/write using threads

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

cron job issue..i hav read the basic threads already...

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

[Solved] Find Files Created Recently and Print

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

How to read a file name that was recently edited when listed using ls command?

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

Unable to read threads when logged in

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
CHICKEN-BUG(1)						      General Commands Manual						    CHICKEN-BUG(1)

NAME
chicken-bug - generates a bug report from user input SYNOPSIS
chicken-bug [ filename | OPTION ... ] OPTIONS
-help Show usage information. -to-stdout Write bug report to standard output instead of writing it to a file. - Read user input from standard input, even if files are given on the command line. DESCRIPTION
chicken-bug generates a bug report file that collects user-input, optional files and system information obtained from the installed CHICKEN executables and libraries. Non-option arguments given on the command line are inserted into the bug report. If no option is given, or if - has been passed on the command line, then a description of the problem is read from standard input, until EOF (CTRL-D) or a line consisting only of "." (period) is read. The bug report will be written to a file in the current directory, which should be sent to CHICKEN maintainers as it contains various use- ful bits of information that make it easier to classify the problem described. Bug reports should be as detailed as possible. It is also very helpful to include code that reproduces the problem. The more detailed the input and the more thorough the description is, the easier you make it for the CHICKEN developers to help you. BUGS
Submit bug reports by e-mail to chicken-janitors@nongnu.org AUTHOR
The CHICKEN Team. SEE ALSO
chicken(1) 19 Sep 2001 CHICKEN-BUG(1)
All times are GMT -4. The time now is 11:47 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy