Stomp has created two threads recently that can't be read Post: 303030219

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

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

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

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

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

LEARN ABOUT DEBIAN

fvwm-bug

fvwm-bug(1)							   Fvwm Modules 						       fvwm-bug(1)

NAME

       fvwm-bug - report a bug in fvwm

SYNOPSIS

       fvwm-bug [--help] [--version] [address]

DESCRIPTION

       fvwm-bug is a shell script to help the user compose and mail bug reports concerning fvwm in a standard format.  fvwm-bug invokes the editor
       specified by the environment variable EDITOR on a temporary copy of the bug report format outline. The user must fill  in  the  appropriate
       fields  and  exit  the  editor.	 fvwm-bug  then  mails the completed report to the local fvwm maintainer, the fvwm workers list fvwm-work-
       ers@fvwm.org, or address.  If the report cannot be mailed, it is saved in the file dead.fvwm-bug in the invoking user's home directory.

       The bug report format outline consists of several sections.  The first section provides information about the  machine,	operating  system,
       the  fvwm  version, and the compilation environment.  The second section should be filled in with a description of the bug.  The third sec-
       tion should be a description of how to reproduce the bug.  The optional fourth section is for a proposed fix.  Fixes are encouraged.

ENVIRONMENT

       fvwm-bug will utilize the following environment variables if they exist:

       EDITOR Specifies the preferred editor. If EDITOR is not set, fvwm-bug defaults to emacs.

       HOME   Directory in which the failed bug report is saved if the mail fails.

Fvwm							       09 May 2010 (2.5.30)						       fvwm-bug(1)