Cmd can make own signal handling and then make own exit codes. So you must search answer from isql documentation.
Also it's easy to test something like:
Run script in background, look cmd process id, sent some signals.
Ex. I tested in my own system what is value of exit status if my cmd is find.
Exit code tell the interrupt signal (exitcode - 256 = signal). Also kill -9.
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)
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)
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)
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)
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)
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)
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)
Hi reader,
I'm making a tool out of korn shell script that is running on a HP-UX server. But everytime i invoke the tool, it gets killed after a while (mid-process). I have tried re-running it a couple of times but each invocation ending up the same way ..
following is a snippet of the o/p... (8 Replies)
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)
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
LEARN ABOUT DEBIAN
osql
osql(1) FreeTDS Utilities osql(1)NAME
osql - utility to test FreeTDS connections and queries
SYNOPSIS
osql -S dsn -U username -P password [-I ini_dir]
DESCRIPTION
osql is a diagnostic tool provided as part of FreeTDS. It is a Bourne shell script that checks and reports on your configuration files. If
everything checks out OK, it invokes isql.
osql works only with the isql that comes with unixODBC.
OPTIONS -S dsn the Data Source Name to which to connect, as known to odbc.ini.
-U username
database login name.
-P password
database password.
-I ini_dir
override odbc.ini file location.
EXAMPLE
If you have an odbc.ini with a section like this:
[myDSN]
servername = myserver
TDS_Version = 5.0
You would invoke osql as:
osql -S myDSN [...]
NOTES
If you can connect with "osql -S servername -U user -P passwd", your FreeTDS ODBC installation is working.
osql guesses where unixODBC might look for its odbc.ini by examining the binary. This is not always an effective approach. If it doesn't
work, you'll receive a report of candidate strings. Kindly pass along the output to help improve the guessing.
If osql cannot intuit your odbc.ini directory, you can force the issue with the -I option. However, you're instructing osql what to test,
not where unixODBC will eventually look. Your override is therefore only as good as you are. Look carefully at the error output before
overriding.
If you have suggestions for ways to make osql more useful as a diagnostic tool, please post them to the FreeTDS mailing list.
HISTORY
osql first appeared in FreeTDS 0.65.
AUTHORS
The osql utility was written by James K. Lowden
doc 13 November 2011 osql(1)