05-20-2011
Quote:
/home/casa/clakkad/bin/one_shot_build.sh[1015]: 7177 Killed
It's the script which is being killed.
I'd look for a "kill" command within the script itself or failing that some sort of process clean-up cron which is killing the script after a certain period of time.
(There is no timeout as such with HP-UX "ftp". It can be implemented by backgrounding the "ftp" and then killing the "ftp" process if it takes too long.
That is not what has happened here.)
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a process that is in the sleeping state "S" and I have tried to stop it with a run control script that I use to stop/start it - but it does not stop.
I have tried kill -9 <PID of process> with no change. I imagine that this process is sleeping with the kernel.
It does not respond to... (5 Replies)
Discussion started by: finster
5 Replies
2. UNIX for Dummies Questions & Answers
Suppose we have the following process tree:
init-> ProcessA->processB->processC
then I kill processB
Who is the parent of the processC?
init or the processA (6 Replies)
Discussion started by: Puntino
6 Replies
3. Programming
We are forking a process B from process A and the process B should display the details it reads from process C(daemon process) continuously.
Let us say that the process C sents 100 packets.The process B receives all the 100 packets from the process C before it prints all details of 31... (1 Reply)
Discussion started by: cijkmysj
1 Replies
4. Solaris
hi,
i am creating a daemon process for updating the file at regular interval.one problem with this is if anybody kills the daemon it wont update the file.anybody have idea how to rerun the daemon if it killed.the code is written in c++ in solaries environment.
thnaks & regards
suresh (8 Replies)
Discussion started by: suresh_rtp
8 Replies
5. Shell Programming and Scripting
I have this shell script and in case the sybase process is been killed how can identify whether the process was killed or not, as the error code always returns 0.
#!/bin/sh
isql -S SERVER -U user -P pass<<TOP
select * from tableName
go
TOP
echo $? (2 Replies)
Discussion started by: dinjo_jo
2 Replies
6. Solaris
Hi all,
Currently I am using LDAP to store some network related data, When I run following script
./ns-slapd ldif2db
Execution of above script terminates displaying "Killed" on the console.
As far as I know, a process can be killed by two ways-
1. manually running " kill -9 <PID of LDAP... (1 Reply)
Discussion started by: akash_mahakode
1 Replies
7. UNIX for Dummies Questions & Answers
HI all,
I am very new to AIX (matter of fact Unix). We are currently automating out manual process using Unix Shell Scripting.
My wrote a shell script which will accept the name of the sas job as parameter, checks the existense of the sas file in the specified folder.
If it is not present,... (1 Reply)
Discussion started by: anubhav2020
1 Replies
8. UNIX for Dummies Questions & Answers
Hi,
I have a process which takes 13-15 mins for execution and its getting killed in the meantime.So can you please helpme out how to protect the process from getting killed.
Thanks in advance.
Regards,
Harika (9 Replies)
Discussion started by: harikagrp
9 Replies
9. Shell Programming and Scripting
Hi,all.Well,I know someone has already asked this question before,however,It's too long before.So i post a new thread here.
Here is the issue.I have a shell script that use awk to calculate something and the script takes about 15 mins,it will use 100% CPU,and the system automatically killed the... (2 Replies)
Discussion started by: homeboy
2 Replies
10. Shell Programming and Scripting
I have two set of questions.
1) To skip killing some process automatically.
2) To kill other process and capture their log.
I have set of process, some needs to be killed gracefully and others should be skipped.
Listed are the process.
adm 1522... (1 Reply)
Discussion started by: murali1687
1 Replies
emsweb(1M) emsweb(1M)
NAME
emsweb - starts the HP-UX Event Monitoring Service tool (a Web interface)
SYNOPSIS
[ ] [ ]
DESCRIPTION
The HP-UX Event Monitoring Service tool ( ) is used to monitor resource instances and manages requests created on these instances.
The HP-UX Event Monitoring Service tool provides both Web-based and terminal user interface. The Web-based interface is launched through
the HP System Management Homepage.
Superuser privileges are required to access the HP-UX Event Monitoring Service tool. A user who does not have superuser privileges has
read-only access to the requests area in the HP-UX Event Monitoring Service tool and cannot modify requests.
An attempt will be made to connect to a Mozilla/Netscape Web browser running on the X server defined by the DISPLAY environment variable.
If a running Mozilla/Netscape client is found, it will be used, otherwise a new Mozilla/Netscape session will be initiated. This will only
happen if the Mozilla/Netscape process is running in the same system as that referenced by the DISPLAY variable, unless the -F option is
used.
Note: By default, the HP-UX Event Monitoring Service tool (emsweb) invokes the Mozilla Web browser. If you want to support any other
browser (Netscape), set the $BROWSER environment variable as shown below:
The terminal user interface is invoked if any of the following conditions are true:
o The command is invoked with the option.
o The environment variable is not set.
The Web-based interface is launched if all the following conditions are true:
o The command is invoked with option.
o The environment variable is set.
o The command is available on the system.
If the Web-based interface cannot be launched, invokes the terminal user interface.
Options
recognizes the following options:
Forces a client browser to be used in less secure ways.
The option forces the client browser to be used or started, even when the X-traffic between the X-server and the Mozilla
browser is not secure.
Use this option only when you are sure the network traffic between the host where Mozilla is running and the host in the
DISPLAY variable is secure.
If cannot start the Web browser, the terminal interface is started.
When the HP-UX Event Monitoring Service Web interface is invoked by SAM, the option is used.
If a privileged user (root) executes the
command with the option, a temporary login bypass key is generated. The bypass key enables the user to access the Web
interface without having to provide login information again.
When the HP-UX Event Monitoring Service Web interface is invoked by SAM, the option is used.
Opens the terminal interface for managing requests created to monitor resource instances regardless of the current setting of the
environment variable.
You can also start the HP-UX Event Monitoring Service tool using one of the following methods:
o Invoke and select the Event Monitoring Service (character mode) functional area to launch the terminal user interface and the
Event Monitoring Service (Web-based Interface) to launch the Web-based tool
o Invoke the HP-UX Event Monitoring Service tool Web interface by typing the URL in the address bar of your browser, where hostname
is the name of the server
o Launch the HP-UX Systems Insight Manager on the server and select the Event Monitoring Service tool from the Configure -> HP-UX
Configuration menu
Online Help
After the HP-UX Event Monitoring Service tool is started, the online help provides details on how to use the tool.
RETURN VALUES
Upon completion, emsweb returns one of the following values:
o 0 Successful
o 1 An error occurred
AUTHOR
was developed by Hewlett-Packard.
SEE ALSO
emscli(1M), resls(1), resdata(1)
emsweb(1M)