Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
| Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
06-30-2005, 12:31 PM
|
#1
|
|
LQ Newbie
Registered: Jun 2005
Posts: 3
Rep:
|
Tracking the source of a killed job
Dear forum,
I am running calculations on a linux (redhat 8) cluster. We submit our jobs to an NQS type queuing system. I suspect that someone possibly w/ root permissions is killing my jobs. Is there any way I can track this possibly nefarious activity?
thanks,
gorets
|
|
|
|
06-30-2005, 02:13 PM
|
#2
|
|
Moderator
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,505
Rep: 
|
Not without kernel patches. Killing is done through inter-process signaling, which is handled by the kernel. Process A tells the kernel "send a SIGHUP to 1234." The kernel then tells process 1234 "Hi, I have a SIGHUP for a process 1234."
|
|
|
|
06-30-2005, 09:07 PM
|
#3
|
|
Member
Registered: Dec 2003
Location: Mississippi, USA
Distribution: Fedora
Posts: 435
Rep:
|
Re: Tracking the source of a killed job
Quote:
Originally posted by gorets
Dear forum,
I am running calculations on a linux (redhat 8) cluster. We submit our jobs to an NQS type queuing system. I suspect that someone possibly w/ root permissions is killing my jobs. Is there any way I can track this possibly nefarious activity?
thanks,
gorets
|
The queuing system almost certainly produces logs. You can grep the logfile for your job id. Alternatively, many queuing systems provide a job history command, which might provide some details.
|
|
|
|
06-30-2005, 09:09 PM
|
#4
|
|
Moderator
Registered: Nov 2004
Location: San Jose, CA
Distribution: Ubuntu
Posts: 8,505
Rep: 
|
Oops... I didn't think about the clustering software. :-P
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 03:44 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|