Utilities not dying after script run Post: 302771103

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

How to manage multiple versions of a set of shell and SQL script utilities

Hi all --- I have the need to manage multiple versions of a set of utility scripts -- both shell and SQL and other .dat files. I am wondering if anyone out there knows of a good way to "PATH" to SQL and text files in a way similar to how PATH facilitates finding executables in a pre-specified...

2. Ubuntu

Internet dying in Debian?

For some reason after a while my internet connection dies. I just moved on to Debian from Ubuntu and I can't find the dhclient-program to reconfigure dhcp. Pretty new to *nix's. ONe thing I noticed while rebooting (do get my connection back) is that it configures dhcp and says: reconfigure (or...

3. UNIX for Dummies Questions & Answers

how to run utilities

I have utilities installed on a UNIX platform and was wondering how i run them.

4. IP Networking

network connection dying after an uptime of a day or two days

hie guys I am running fedora 6 on remote machines which are connecting to my server. The remote machines connect through one machine (more like my router) to the server. The problem i am having is that the remote machines are suppose to be reporting in real time mode to the server. Most of these...

5. Programming

Java application dying randomly

Hi, (First post, please be gental!) I have a java app that I am running on unix (centos) But it keeps dying randomly. The times seem random from anything between 3 hours and 3 days. I have a cronjob running to restart it when ever it dies but I would rather this happened less often. ...

6. Shell Programming and Scripting

Expect script cronjob running but dying prematurely

I have an Ubuntu machine that I'd like to update automatically. I've written an expect script to run the aptitude package manager and update my packages. Essentially it does: aptitude update && aptitude upgrade while answering "yes" at the appropriate time. It works quite nicely when run...

7. Red Hat

Snmpd dying on centos7.1

Hello All, SNMPD dying after 2 mins once it started. Here is the configuration Oct 12 04:43:00 localhost systemd: Starting Simple Network Management Protocol (SNMP) Daemon.... Oct 12 04:43:00 localhost snmpd: dlopen failed: /usr/lib64/libcmaX64.so: cannot open shared object file: No such...

8. What is on Your Mind?

Are the BSDs dying?

Source a quick google search making clear that this isn't really new, and if we look at our bsd Forum we see that its the only operation systems forum with the last comment dated to June last year, whereas all the others have more recent comments. One comment dated to 2014 is exactly what I...

LEARN ABOUT LINUX

bosskill

BOSSKILL(8)						      System Manager's Manual						       BOSSKILL(8)

NAME

       bosskill - send a signal to your boss, or terminate your boss

SYNOPSIS

       bosskill [ -signal ] <bossname>

DESCRIPTION

       bosskill  sends	the  TERM  (terminate,	15) signal to the boss with the specified bossname.  If a signal name or number preceded by `-' is
       given as the first argument, that signal is sent instead of terminate. The killed boss must be in the  system  administrator's  supervisory
       chain.

       The following is a list of all signals with names as in the include file <signal.h>:

       SIGHUP	 1     hangup.	Forces	bossname  to re-read his/her job description and figure out that he/she knows squat about sysadmin work or
		      life, in general.

       SIGINT	 2    interrupt. Prevents the bossname from interrupting the sysadmin for one hour.

       SIGQUIT	 3    quit. Causes the boss to quit his/her job with no explanation.

       SIGILL	 4    illegal instruction. Makes the boss believe the last instruction he/she gave was illegal, so he/she withdraws it.

       SIGTRAP	 5    trace trap. Display the exact location of the boss.

       SIGABRT	 6    abort. Makes the boss go home and try again tomorrow.

       SIGKILL	 9    kill. Game over.

       SIGBUS	 10   bus error. Boss's transportation fails on the way to work.

       SIGSEGV	 11   segmentation violation. Boss realizes he/she is trying to do something for which he/she is not quailified and stops.

       SIGSYS	 12   bad argument. Boss loses.

       SIGPIPE	 13   smoke pipe. Boss samples some green leafy substance and mellows out.

       SIGALRM	 14   alarm. Boss is startled and falls over. Best used when boss is walking next to his/her boss.

       SIGTERM	 15   termination signal. Boss is fired.

BUGS

       Sending a SIGABRT to a boss that is already home will cause him/her to walk aimlessly in circles for two hours.

HISTORY

       Written by Eric L. Pederson <eric@bofh.org.uk>.

								 27 September 1995						       BOSSKILL(8)