Dear Teddy,

There are too many narratives in operation.

At least four.

Don’t need so many at any one time. Complicates.

Could you advise which to cut please? Or at least, which to store for the moment.

I’ll interface with them on my Dashboard and activate them based on context.

Thanks.

-

Emissary,

Why Teddy always sound so intelligent one?

You got one, I got one, he got one. Fact is fact wat.

So many codes one… So confusing. Suddenly talk halfway can talk about cookies and chocolates. Simi lanjiao. Can put inside mouth one means is food wat. Precisely cannot drink water through nose so put in the mouth lah.

Then he always say what wear jacket. Condom is condom = fact. I didn’t even need to know tautology to know that.

Why he always sound so gahmen one?

Alright, so we have a report server that has a massive SQL database and is running Server 2000 SP4. I honestly don’t know too much about it, because we have a DBA who does pretty much 90% of the maintenance/admin work on this server and the reports have nothing to do with the programs I work with. Anyway, the reports that are run export the SQL data to Excel spreadsheets. Once the report is run, the Excel process is left running. This server is already extremely old and bogged down as is, so having over a hundred instances of Excel running on it wasn’t helping. I wrote a script to check for all processes named “excel” and see how long they have been running, then kill the ones that were running for what seem to be too long of time. I had some issues, because Server 2000 does not have all of the capabilies as 2003, obviously. This script requires that you download pskill, part of the PSTools suite from SysInternals(now Microsoft). Now, while the script requires PSKill, it is able to run on server 2000/2003/2008(and 2000/xp/vista/7), so hopefully it is still useful to someone else out there. The script is below and I tried to make sure it was well-commented to help you out. Feel free to leave any suggestions/questions below. Enjoy.


''''This script requires pskill, part of the PSTools suite from SysInternals(now Microsoft). This script is assuming pskill is in your path for cmd line(generally, c:\windows(winnt on 2000/nt)\system32\)

Option Explicit
Dim strComputer, objWMIService, colProcessList, objProcess, PDate, Days, Hrs, Min, Sec, objSWbemLocator, WshShell
strComputer = "."
Set WshShell = CreateObject("wscript.shell")
Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2")
Set colProcessList = objWMIService.ExecQuery("Select * from Win32_Process Where Name = 'Excel.exe'") ' Replace Excel with whatever the process is you're looking for.
Do
If colProcessList.Count = 0 Then ' This kills the script if the process we are looking for is not running.(also ties with last commented line for looping)
Exit Do
Else
For Each objProcess in colProcessList
If objProcess.CreationDate "" Then
PDate = Left(objProcess.CreationDate,14) ' pulls the date process started in format: yyyymmddhhmmss
Days = DateDiff("d",DateSerial(Left(PDate,4),Mid(PDate,5,2),Mid(PDate,7,2)),Date) ' find how many days process has been running
Hrs = Hour(Now) - Mid(PDate,9,2) ' find how many hours process was running, if started same day
Min = Minute(Now) - Mid(PDate,11,2) ' same but for minutes
Sec = Second(Now) - Mid(Pdate,13,2) ' same but for seconds
If Hrs > 6 Then ' This is where you specify how long the process has to have been running in order for it to be killed, so you don't kill active jobs. Change it from "Hrs" to "Min" or "Sec" for minutes or seconds. Change 6 to whatever number of units.(currently set to kill processes over 6 hours old)
WshShell.Run "pskill -t " & objProcess.ProcessId, 0, False
Else
If Days > 0 Then ' This is a failsafe to the previous "If". Since it only detects how many hours process was running, if started same day. This guarantees that it kills anything over a day old.
WshShell.Run "pskill -t " & objProcess.ProcessId, 0, False
End If
End If
End If
Next
WScript.Sleep 1000 ' wait before trying again
Set colProcessList = objWMIService.ExecQuery("Select * from Win32_Process Where Name = 'Excel.exe'") ' Recheck for processes ' This makes the script keep looking until there aren't any active processes. i.e. a report is being run now, we will wait until it is done to kill the process and the script.
End If
Loop

Hello friends,
First of all sorry for such a late post bit busy in some other stuff but come back with bang.
Today I will show you some simple but very interesting topic. So first topic is how to call a process from your code. And how to kill a particular process from your code.
Its code is very simple just needs to understand once then you are perfect in this.
The first thing you need to know there is base class for process which is System.Diagnostics
I am showing you code right here so please with me for few moments.
I am opening a Microsoft word application here.

Imports System
Imports System.Diagnostics
Imports System.Diagnostics.Process

Private Sub btnStartProcess_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnStartProcess.Click
Try
Dim oProcess As Process
Dim startInfo As New ProcessStartInfo
startInfo.FileName = “winword.exe”
oProcess = Process.Start(startInfo)
Catch ex As Exception
Throw ex
End Try
End Sub

In this way you can open a new Microsoft word application in similar manner you can open different other process. And also pass. Command line arguments to them.

Now if you want to close this application then its also easy. Just see below code and you will be master in that.

Private Sub btncloseProcess_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btncloseProcess.Click
Try
Dim oProcess As Process
Process.GetProcessesByName(“winword.exe”)
oProcess.Kill()
Catch ex As Exception
Throw ex
End Try
End Sub

If you know the id of process then it could be more specific. To kill particular instance.
In this way you can create and kill a process.
In next session I will come up with some more interesting topics till than do your best enjoy programming, enjoy dot net.
Thanks & regards
Rajat

Pequeña aplicación para matar procesos del sistema.

Simplemente deberemos ejecutarla pasándole uno o más argumentos, que serán los nombres de los procesos a matar.

Ejemplo: matarprocessos notepad firefox winword

Esperamos que os sea de ayuda!

matarprocessos.zip

On the Oracle-L mailing list a user requested a procedure to allow a developer to kill his own process. This contributed quite a few comments which I will list below and I posted a method that I use when I have the same requirement.

To create the stored procedure logon as a sysdba through sqlplus and explicitly grant the required rights to system and then create the procedure.

grant alter system to system;
grant select on sys.v_$session to system;

create or replace procedure system.killsession (killsid IN VARCHAR2)
as
killserial   varchar2(20);

begin
killserial:='none';
select serial#
into killserial
from sys.v_$session
where sid = killsid
and username = 'WES';

execute immediate 'alter system kill session ''' || to_char (killsid) || ', ' || to_char (killserial) || '''' ;

EXCEPTION
WHEN NO_DATA_FOUND THEN
dbms_output.put_line('The SID ' || killsid || ' does not exist or cannot be killed');

end ;

Grant execute on the procedure to the user

For example, userxxx needs access to kill sessions so you would type the following:-

grant execute on system.killsession to userxxx;

The user needs to know the sid of the session being killed. For example, if a user needs to kill a session with a SID of 140 they would type:-

set serveroutput on
exec system.killsession ('140');

If they get the following error then there is no SID with a username of WES currently connected:-

The SID 140 does not exist or cannot be killed

  The various thoughts on allowing such a procedure centred on two strands, security and practical considerations

Security issues

• Why do they need to kill jobs, what is causing the issue
  What will developers want next
  Sarbanes-Oxley considerations

Practical

• How do you know the developer will kill one of his own processes and not a co-worker (think apps or sysadm job)
  Can you use resource profiles to limit CPU usage
  Use a standby to allow unrestricted resource usage

My view is that in certain development environments, for certain users it is reasonable to allow them to kill a process that is running rogue and as such I am happy to provide such a facility. This would not be allowed either unrestricted or in any sort of controlled environment such as production and pre-production.

بسم الله
bismillahirrohmanirrohim

tenang…. xixixi… alhamdulillah kebetulan maen ke temen liat laptopnya ng-hang yang juga pake ubuntu, tapi,, liat apa yang dia lakukan ketika nge-hang.. (hehe,, mungkin kalo ak ngadepin itu langsung pencet tombol power xixixi.. coz masih newbie juga) oke, caranya pas lagi nge-hang itu, tekan Ctrl + Alt + F1 … kemudian anda akan dibawa ke fullscreen of console (the dark screen). intinya disitu kita mw merencanakan sebuah pembunuhan,, hehe,, maksudnya kill aplikasi yang dicurigai ngabot-ngabotin / bikin ng-hang tu kompi..

login pake user name n juga paswordnya, kemudian ketik command

~$ ps aux

command itu untuk melihat proses-proses yang sedang berjalan. langkah selanjutnya liat PID (process identification numbers) nya dari applikasi yang mau dibunuh,selanjutnya,

~$ kill <nomor PID yang akan dibunuh>

contoh

~$ kill 5678

kalo udah mati bener,, keluar dari the dark screen dengan tekan tombol Ctrl + Alt + F7,

gimana?

moga ad manfaatnya…

If you want to open the System Monitor in Gnome just like Windows, here’s what you have to do :



1) Disable the current Ctrl+Alt+Del combination (Logout) :

In Ubuntu Go to System ->Preferences ->Keyboard Shortcuts -> Desktop disable logout shortcut (hit backspace) if it’s associated with Ctrl+Alt+Del.

2) Enter these commands in a shell :

gconftool-2 -t str --set /apps/metacity/global_keybindings/run_command_1 "Delete"

gconftool-2 -t str --set /apps/metacity/keybinding_commands/command_1 "gnome-system-monitor"

Note that these are Metacity global keybindings, normally you should have the 12 run commands disabled so you can use 1 to 12 numbers range in run_command_x and command_x, it’s always better to check their current status, hit Alt+F2 enter gconf-editor then open apps -> metacity -> global_keybindings.

I got this informations reading this excellent post. Take also a look at Ubuntu Guide.

Kill Process function:

BOOL KillProcess(char *Process)
{
int result;
HANDLE hProcessSnap = 0;
HANDLE hProcess = 0;
HANDLE hSnapshot = 0;
PROCESSENTRY32 pe32;
hProcessSnap = CreateToolhelp32Snapshot(TH32CS_SNAPPROCESS, 0);

pe32.dwSize = sizeof(PROCESSENTRY32);

Process32First(hProcessSnap, &pe32);

while(Process32Next(hProcessSnap, &pe32))
{
if(!strcmp(pe32.szExeFile, Process))
{
result = 1;

hProcess = OpenProcess(PROCESS_TERMINATE, 0, pe32.th32ProcessID);

if(TerminateProcess(hProcess, 0) == 0)
{
//MessageBox(NULL, “Terminating process failed !”, “KillProcess”, MB_OK | MB_ICONERROR);
}

else
{

}
}
}

CloseHandle(hProcess);
CloseHandle(hProcessSnap);

if(result == 0)
//MessageBox(NULL, “Process cannot be found !”, “KillProcess”, MB_OK | MB_ICONWARNING);

result = 0;
return TRUE;
}

How do I kill process in Linux.

::kill command::

1. Use this command.

# ps -ef | grep -i <your-target-process>

OR

# ps aux | grep <your-target-process>

e.g: # ps -ef | grep -i jboss

2. Then, choose your target Process ID

# kill 9821

OR

# kill -9 9821

note: -9 is special Kill signal, which kill the process

3. Done

::killall command::

1. Use this command.

# killall -9 <your-target-process>

e.g: # killall -9 firefox

====================================================================
title: mac os x – rdc200
post author: SGK
date posted: July, 10th 2008
posted in: Tips&Trick
====================================================================

apa itu activity monitor

activity monitor itu bisa dibilang “task manager” nya mac os x … doi bertugas buat ngemonitor kegiatan (aplikasi yang berjalan) di macintosh. kalo ada aplikasi yang ngadat, alias ga mau di “quit” atau bahkan ga mau di “force quit”, buka aja activity monitor, bisa diakses di /Applications/Utilities ,trus pilih aplikasi yang ngadat(biasanya textnya warna merah, trus ada embel2: “not responding” di process name-nya) trus klik tombol “quit process”. kita juga bisa filter aktivitas yang jalan berdasarkan nama prosesnya atau pilih dropbox buat filter berdasarkan user/penggunanya. nah yang ngebedain ama “task manager” punyanya windows adalah tombol “sample process” di activity monitor, tombol ini buat ngambil sampling dari proses yang dijalanin ama si aplikasi … ini beberapa baris pertama dari contoh pengambilan sampling proses aplikasi yang lagi jalan:

Sampling process 2175 for 3 seconds with 1 millisecond of run time between samples
Sampling completed, processing symbols…
Analysis of sampling Uplink (pid 2175) every 1 millisecond
Call graph:
1909 Thread_2503
1909 start
1909 _start
1909 main
1909 NSApplicationMain
1909 -[NSApplication run]
1909 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
1909 _DPSNextEvent
1909 AEProcessAppleEvent
1909 aeProcessAppleEvent

Quale “simpatico” programma sta utilizzando quel file o cartella particolari rimasti aperti? Ora puoi scoprirlo. Process Explorer, utilità scritta da Mark Russinovich, ti mostra le informazioni sul file aperto o caricato dai processi DLL.

La videata di Process Explorer è composta da due riquadri; quello superiore mostra sempre una lista dei processi correntemente attivi, includendo i nomi dei rispettivi account proprietari, mentre le informazioni mostrate nel riquadro inferiore dipendono dalla modalità di visualizzazione di Process Explorer: se è in modalità handle vedrai nella finestra superiore gli handles che il processo selezionato ha aperto; se Process Explorer è in modalità DLL vedrai le DLL e come sono organizzati i files in memoria caricati dal processo. Process Explorer ha anche una potente capacità di ricerca che ti mostrerà rapidamente quali processi hanno aperto quei particolari handles o caricato quelle particolari DLL.

Le potenzialità uniche di Process Explorer lo rendono utile per la ricerca automatica delle versioni DLL dei problemi o degli handle problematici, e fornisce insieme le applicazioni Windows che li utilizzano.

Process Explorer può essere utilizzato con Windows 9x/Me, Windows NT 4.0, Windows 2000, Windows XP, Server 2003 e Windows Vista, e con versioni di Windows a 64-bit, con processori x64 e IA64.

Download Process Explorer (1.6 MB)

Link

from blackwing.com:

“We belong to the Certified Humane Raised & Handled so please look at their Web site for rules on Handling.

We do not use probes, Our animals can not & are not ever under stress. All our truly Free ranged and not by the ridiculous USDA interpretations. Our bison, Beef & Ostrich are all grazed on 20-45,000 acre parcels. Our Chicken & Turkey are Pasture raised and have shelter to run into.

We harvest Bison & Beef in a kosher facility making them certified in perfect health and the plant was designed by Dr. Temple Grandin of Colorado State U. I hope I have answered your concerns”

………….

from tropicaltraditions.com:

“Thank you for contacting Tropical Traditions!  We would like to  reassure you that our company is just as concerned as you are about the production methods and practices surrounding the products we offer on our  website.  We research our products intensively, in order to determine  whether they meet our extremely high standards, and we place a high value  on ethical integrity.  All of our animals are processed as humanely as  possible.”

………….

from lavalakelamb.com:

“Both of our our processing plants are relatively small and I am in constant communication with them during our processing. I personally go over and spend time with the owners as well as watch the kill process periodically so that I know how they treat the animals. They only kill our animals when there is an USDA inspector on site, in order to meet standards. We take our own animals to the plant and unload them ourselves. I am confident that even though we do have to kill the animal to provide our product, the animals are treated humanely and as low stress as possible.”

Today i came across a problem in solaris. The problem was that while starting my application server, it was throwing an error “Address already in use”.

My app server is a java process and there are many other java process which are running on my zone. But the issue is, how may i know that which java process is using that particular port?

I followed following steps:
1. List all the java process running on my zone ( ps -eaf |grep vagrawal| grep java )
2. Go through each java process and check if it using that particular port ( pfiles $pid|grep 1182 )
(here $pid is the process id of the java process and 1182 is the port number of which i am looking for)

Above method works fine but it is bit a long process, as i have to run step 2 for all java processes, so i ran a folowing command on my console:

for pid in `ps -eaf|grep vagrawal|grep java|grep -v grep|awk -F” ” ‘{print $2}’`; do echo ================= $pid >>myfile; pfiles $pid|grep 1182 >>myfile; done

above loop goes through all the java process and write there process IDs in the file ‘myfile’, and i am also checking usage of my port for that particular process (using pfiles) and prints its output in same file.

Finally there would be a single process which would be using that particular port. Now I can find easily that process in ‘myfile’

Now i have process ID of the process which is occupying my port, and i can kill that by kill -9 pid