Sponsored Content
Top Forums UNIX for Dummies Questions & Answers Closing information to stdout‏ Post 302473458 by DGPickett on Saturday 20th of November 2010 11:05:16 AM
Old 11-20-2010
Maybe terminate them with something that does not log, like a caught signal and exit?

Of run them with the logging redirected to an appropriate, dedicated log file?

One trick to not hear from your children is to make them orphan grandchildren by starting them in a subshell (). For instance, as I recall this does not tell you the pid or exit:
Code:
(
for f in *
do
 fgrep -l DeWoid $f &
done
)

 

9 More Discussions You Might Find Interesting

1. IP Networking

Closing out ports???

Hi all Is there a command that I can use to close out open ports? I did a netstat - a -p and got a long list of ports open (see sample below). I have disabled the some of the applications from /etc/services/. But there are still applications listening on certain ports. I need to know how to... (6 Replies)
Discussion started by: skotapal
6 Replies

2. Post Here to Contact Site Administrators and Moderators

Closing a thread

hi, Just wondering if there could be a way to close threads whose creator has got the desired reply. however if someone still wants to give a remark or suggest further on the thread one can still do so. Besides on the control panel there should be some kind of selection criteria to view... (3 Replies)
Discussion started by: linuxpenguin
3 Replies

3. Shell Programming and Scripting

closing windows

Ok i know to open a window from a script (mac); open whatever(name of a directory) but i don't how to close it. please some help. thanks. (0 Replies)
Discussion started by: Tártaro
0 Replies

4. IP Networking

Closing the socket

Hi, I have a question on closing the listen socket in server. In the application I am working, the server is continously receiving requests from the client in its master socket to handle each request. There is an option to shutdown the server process. In this case do I need to explicitly close... (1 Reply)
Discussion started by: naan
1 Replies

5. Post Here to Contact Site Administrators and Moderators

Thread Closing

Not sure as to How to close a thread so people understand that the issue was solved and the issue is not just sitting in limbo still waiting for a resolution. (1 Reply)
Discussion started by: mrmurdock
1 Replies

6. UNIX for Advanced & Expert Users

Build catalogue for sliced dar archive‏

Hi I have a use case where I use Dar to backup a huge filesystem into 4GB slices and build catalogue for incremental backup later. Since I don't have enough space for all slices, I have to upload one slice to target server and delete, and then generate another slice... (using something like... (0 Replies)
Discussion started by: overmindxp
0 Replies

7. What is on Your Mind?

AllTheWeb closing

It was officially announced that AllTheWeb is closing. Yahoo! no longer supports the function as per april 2011: AlltheWeb.com Before the world turned to google by default, there used to be a plethora of search engines. Most of them gave a headache with the prolific use of colors and animated gifs... (4 Replies)
Discussion started by: figaro
4 Replies

8. Red Hat

Installing EBS 12.1.1 on RHEL 6.1 x86_64‏

i am in process to install R12.1.1 on RHEL 6.1. while installing pre-requisite on RHEL 6.1 i am facing following error : rpm -ivh xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386.rpm error: Failed dependencies: libX11.so.6 is needed by xorg-x11-libs-compat-6.8.2-1.EL.33.0.1.i386 ... (3 Replies)
Discussion started by: rehantayyab82
3 Replies

9. Post Here to Contact Site Administrators and Moderators

Closing thread

Hi, I guess, users do not have rights to close a thread. Please close thread 'Small automation' as it is resolved. Regards, snjksh (1 Reply)
Discussion started by: snjksh
1 Replies
IO::Async::Signal(3pm)					User Contributed Perl Documentation				    IO::Async::Signal(3pm)

NAME
"IO::Async::Signal" - event callback on receipt of a POSIX signal SYNOPSIS
use IO::Async::Signal; use IO::Async::Loop; my $loop = IO::Async::Loop->new; my $signal = IO::Async::Signal->new( name => "HUP", on_receipt => sub { print "I caught SIGHUP "; }, ); $loop->add( $signal ); $loop->run; DESCRIPTION
This subclass of IO::Async::Notifier invokes its callback when a particular POSIX signal is received. Multiple objects can be added to a "Loop" that all watch for the same signal. The callback functions will all be invoked, in no particular order. EVENTS
The following events are invoked, either using subclass methods or CODE references in parameters: on_receipt Invoked when the signal is received. PARAMETERS
The following named parameters may be passed to "new" or "configure": name => STRING The name of the signal to watch. This should be a bare name like "TERM". Can only be given at construction time. on_receipt => CODE CODE reference for the "on_receipt" event. Once constructed, the "Signal" will need to be added to the "Loop" before it will work. AUTHOR
Paul Evans <leonerd@leonerd.org.uk> perl v5.14.2 2012-10-24 IO::Async::Signal(3pm)
All times are GMT -4. The time now is 06:11 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy