Browse Prior Art Database

Method for Tracking Processes to Their Root Creation

IP.com Disclosure Number: IPCOM000110867D
Original Publication Date: 1994-Jan-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 63K

Publishing Venue

IBM

Related People

Johnson, WJ: AUTHOR [+2]

Abstract

A desktop user frequently discovers processes running on his/her desktop, with no way to determine how the processes were created, and, therefore, whether they are still required. For example, Joe starts several applications on his already busy desktop, including Windows*, Calendar, and Data Base. Later in the day, his desktop has become so busy that he needs to close some applications. He closed Windows and Calendar, and then displays the task list to see what else he can close. The task list shows:

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 52% of the total text.

Method for Tracking Processes to Their Root Creation

      A desktop user frequently discovers processes running on
his/her desktop, with no way to determine how the processes were
created, and, therefore, whether they are still required.  For
example, Joe starts several applications on his already busy desktop,
including Windows*, Calendar, and Data Base.  Later in the day, his
desktop has become so busy that he needs to close some applications.
He closed Windows and Calendar, and then displays the task list to
see what else he can close.  The task list shows:

     OS/2** Full Screen 1

     DOS Window

     OS/2 Full Screen 2

     Data Base

     Clipboard

     Data Update

      Since Joe has started and used several applications, and some
of them are still needed, he has no way to tell whether it is safe
for him to shut down anymore applications.  He would like to shut
down clipboard, but since he hasn't explicitly used the Clipboard
today, he doesn't even know why it is running.  However, he is afraid
to shut it down in case it was initiated by an application he still
needs.  To try to figure out where Clipboard came from, he
double-clicks on it, and a blank clipboard window appears, but he
still doesn't know where it came from.  When he double-clicks on Data
Update, no window appears, but he assumes that Data Update was
initiated by Data Base, since the names are similar, but this is a
wrong assumption.  The user needs a method of tracking any process in
the task list back to its root process or invocation.

      This system provides a method by which the user can visually
verify how any process in the task list was created, and to which
root process it belongs.  This is accomplished by starting and
tracking a...