process kill

If I keep having to kill a process in the task manager is there a shortcut
I can create that will kill that process by clicking that shortcut?

Alojzy Bednarz wrote:
If I keep having to kill a process in the task manager is there a shortcut
I can create that will kill that process by clicking that shortcut?

https://www.computerhope.com/taskkill.htm

taskkill /f /im notepad.exe

https://www.computerhope.com/tskill.htm

tskill notepad /V # maybe in Home version?

But it's probably easier to just rename the EXE file
so it cannot start.

One thing you should know about computers, is they
can generally start processes, faster than you can
stop them. Study "fork bombs" for more information.
Even for commands structured for the job (like a PPID
based solution), it's still not possible for a
"repetitive killer" program to make progress against
a "fork bomb". We tried this at work a few times,
after someone in my department wrote a fork bomb by
accident. It was easier to just power off the computer
and pray there would be no file system damage.

When Windows 10 gets under memory pressure, you cannot
count on Task Manager being available to restore
control of the machine.

Paul

On 25/07/2019 04.48, Paul wrote:
Alojzy Bednarz wrote:
If I keep having to kill a process in the task manager is there a
shortcut I can create that will kill that process by clicking that
shortcut?

https://www.computerhope.com/taskkill.htm

Â*Â* taskkill /f /im notepad.exe

https://www.computerhope.com/tskill.htm

Â*Â* tskill notepad /VÂ*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â*Â* # maybe in Home version?

But it's probably easier to just rename the EXE file
so it cannot start.

Is that always possible? :-?


One thing you should know about computers, is they
can generally start processes, faster than you can
stop them. Study "fork bombs" for more information.
Even for commands structured for the job (like a PPID
based solution), it's still not possible for a
"repetitive killer" program to make progress against
a "fork bomb". We tried this at work a few times,
after someone in my department wrote a fork bomb by
accident. It was easier to just power off the computer
and pray there would be no file system damage.

Now that you can run bash in Windows, it may be possible to run such
bombs easier ;-)


--
Cheers, Carlos.

Carlos E.R. wrote:


But it's probably easier to just rename the EXE file
so it cannot start.

Is that always possible? :-?

I do those using offline materials. (Boot some CD or DVD
and fix whatever needs fixing.)

To make the materials more accessible, you can

compact /compactOS:never

as well as "sudo ntfsfix /dev/sda1" or whatever, to
correct the $MFTMIRR damaged by Windows 10. You also
want Fast Boot disabled, a quick "powercfg /h off"
will cover that.

There are ways to increase the odds of fixing something.

Paul

In article , Paul wrote:
Alojzy Bednarz wrote:
If I keep having to kill a process in the task manager is there a shortcut
I can create that will kill that process by clicking that shortcut?

https://www.computerhope.com/taskkill.htm

taskkill /f /im notepad.exe

https://www.computerhope.com/tskill.htm

tskill notepad /V # maybe in Home version?

But it's probably easier to just rename the EXE file
so it cannot start.

Why assume that is the problem? (See below)

One thing you should know about computers, is they
can generally start processes, faster than you can
stop them. Study "fork bombs" for more information.

I think you're making a rather large leap assuming that OP's actual problem
is something sinister - that is, either a process running that shouldn't be
running at all (hence your suggestion to rename the EXE) or some kind of
evil "fork bomb".

There are plenty of simpler and innocuous explanations. For example, who
here hasn't been in the situation of developing/debugging a long-running
process (sometimes referred to as a "daemon") and needing to kill the
running process every time you want to deploy/test a new version? In that
case, some kind of script or icon to quickly kill the old one is an
entirely reasonable thing to want to have.

--
Men rarely (if ever) manage to dream up a God superior to themselves.
Most Gods have the manners and morals of a spoiled child.

Kenny McCormack wrote:
In article , Paul wrote:
Alojzy Bednarz wrote:
If I keep having to kill a process in the task manager is there a shortcut
I can create that will kill that process by clicking that shortcut?
https://www.computerhope.com/taskkill.htm

taskkill /f /im notepad.exe

https://www.computerhope.com/tskill.htm

tskill notepad /V # maybe in Home version?

But it's probably easier to just rename the EXE file
so it cannot start.

Why assume that is the problem? (See below)

One thing you should know about computers, is they
can generally start processes, faster than you can
stop them. Study "fork bombs" for more information.

I think you're making a rather large leap assuming that OP's actual problem
is something sinister - that is, either a process running that shouldn't be
running at all (hence your suggestion to rename the EXE) or some kind of
evil "fork bomb".

There are plenty of simpler and innocuous explanations. For example, who
here hasn't been in the situation of developing/debugging a long-running
process (sometimes referred to as a "daemon") and needing to kill the
running process every time you want to deploy/test a new version? In that
case, some kind of script or icon to quickly kill the old one is an
entirely reasonable thing to want to have.


There is a separate command for stopping services.

net stop bits
sc query bits
net start bits

Paul

In article , Paul wrote:
Kenny McCormack wrote:
In article , Paul wrote:
Alojzy Bednarz wrote:
If I keep having to kill a process in the task manager is there a shortcut
I can create that will kill that process by clicking that shortcut?
https://www.computerhope.com/taskkill.htm

taskkill /f /im notepad.exe

https://www.computerhope.com/tskill.htm

tskill notepad /V # maybe in Home version?

But it's probably easier to just rename the EXE file
so it cannot start.

Why assume that is the problem? (See below)

One thing you should know about computers, is they
can generally start processes, faster than you can
stop them. Study "fork bombs" for more information.

I think you're making a rather large leap assuming that OP's actual problem
is something sinister - that is, either a process running that shouldn't be
running at all (hence your suggestion to rename the EXE) or some kind of
evil "fork bomb".

There are plenty of simpler and innocuous explanations. For example, who
here hasn't been in the situation of developing/debugging a long-running
process (sometimes referred to as a "daemon") and needing to kill the
running process every time you want to deploy/test a new version? In that
case, some kind of script or icon to quickly kill the old one is an
entirely reasonable thing to want to have.


There is a separate command for stopping services.

net stop bits
sc query bits
net start bits

Totally irrelevant.

But thank you for playing our game. Lovely parting gifts, etc, etc.

--
Modern Conservative: Someone who can take time out from flashing her
wedding ring around and bragging about her honeymoon to complain that a
fellow secretary who keeps a picture of her girlfriend on her desk is
"flauting her sexuality" and "forcing her lifestyle down our throats".

Kenny McCormack wrote:
In article , Paul wrote:
Kenny McCormack wrote:
In article , Paul wrote:
Alojzy Bednarz wrote:
If I keep having to kill a process in the task manager is there a shortcut
I can create that will kill that process by clicking that shortcut?
https://www.computerhope.com/taskkill.htm

taskkill /f /im notepad.exe

https://www.computerhope.com/tskill.htm

tskill notepad /V # maybe in Home version?

But it's probably easier to just rename the EXE file
so it cannot start.
Why assume that is the problem? (See below)

One thing you should know about computers, is they
can generally start processes, faster than you can
stop them. Study "fork bombs" for more information.
I think you're making a rather large leap assuming that OP's actual problem
is something sinister - that is, either a process running that shouldn't be
running at all (hence your suggestion to rename the EXE) or some kind of
evil "fork bomb".

There are plenty of simpler and innocuous explanations. For example, who
here hasn't been in the situation of developing/debugging a long-running
process (sometimes referred to as a "daemon") and needing to kill the
running process every time you want to deploy/test a new version? In that
case, some kind of script or icon to quickly kill the old one is an
entirely reasonable thing to want to have.

There is a separate command for stopping services.

net stop bits
sc query bits
net start bits

Totally irrelevant.

But thank you for playing our game. Lovely parting gifts, etc, etc.


A daemon is a service.

Paul

In article , Paul wrote:
Kenny McCormack wrote:
In article , Paul wrote:
Kenny McCormack wrote:
In article , Paul wrote:
Alojzy Bednarz wrote:
If I keep having to kill a process in the task manager is there a shortcut
I can create that will kill that process by clicking that shortcut?
https://www.computerhope.com/taskkill.htm

taskkill /f /im notepad.exe

https://www.computerhope.com/tskill.htm

tskill notepad /V # maybe in Home version?

But it's probably easier to just rename the EXE file
so it cannot start.
Why assume that is the problem? (See below)

One thing you should know about computers, is they
can generally start processes, faster than you can
stop them. Study "fork bombs" for more information.
I think you're making a rather large leap assuming that OP's actual problem
is something sinister - that is, either a process running that shouldn't be
running at all (hence your suggestion to rename the EXE) or some kind of
evil "fork bomb".

There are plenty of simpler and innocuous explanations. For example, who
here hasn't been in the situation of developing/debugging a long-running
process (sometimes referred to as a "daemon") and needing to kill the
running process every time you want to deploy/test a new version? In that
case, some kind of script or icon to quickly kill the old one is an
entirely reasonable thing to want to have.

There is a separate command for stopping services.

net stop bits
sc query bits
net start bits

Totally irrelevant.

But thank you for playing our game. Lovely parting gifts, etc, etc.


A daemon is a service.

A fish is not a bicycle.

--
The randomly chosen signature file that would have appeared here is more than 4
lines long. As such, it violates one or more Usenet RFCs. In order to remain
in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/GodDelusion

Kenny McCormack wrote:

A daemon is a service.

A fish is not a bicycle.


This is the IIS FTPd service.

Listening on port 21.

https://i.postimg.cc/cC0LddCN/ftp.gif

Paul

On 7/24/2019 10:32 PM, Alojzy Bednarz wrote:
If I keep having to kill a process in the task manager is there a shortcut
I can create that will kill that process by clicking that shortcut?

First attempt should be a REQUEST kill: TASKKILL /IM "xxx.exe" /T

Second attempt would be FORCE kill: TASKKILL /IM "xxx.exe" /T /F

Where xxx.exe is name of process shown in Task Manager

Some processes must use FORCE and will not respond to polite request.


--
Zaidy036

On 25/07/2019 19.11, Paul wrote:
Carlos E.R. wrote:


But it's probably easier to just rename the EXE file
so it cannot start.

Is that always possible? :-?

I do those using offline materials. (Boot some CD or DVD
and fix whatever needs fixing.)

To make the materials more accessible, you can

Â*Â* compact /compactOS:never

as well as "sudo ntfsfix /dev/sda1" or whatever, to
correct the $MFTMIRR damaged by Windows 10. You also
want Fast Boot disabled, a quick "powercfg /h off"
will cover that.

There are ways to increase the odds of fixing something.

Ah, ok. With those tricks ;-)

--
Cheers, Carlos.

Paul wrote:
Kenny McCormack wrote:

A daemon is a service.

A fish is not a bicycle.

This is the IIS FTPd service.

Listening on port 21.

https://i.postimg.cc/cC0LddCN/ftp.gif

Paul

I tend to agree [1] with Kenny.

A (Windows) service can be considered to fall under the general
computer term "daemon".

BUT, a daemon is not necessarily a (Windows) service. I.e. you can
write a program which acts as a daemon, but is *not* a (Windows)
service, i.e. it's *not* listed my services.msc.

IOW, a Mercedes is a car, but a car is not necessarily a Mercedes.

So (IMO) you should have written "A (Windows) service is a daemon.".
That would have been correct, but irrelevant for the scenario Kenny was
describing.

[1] Very reluctantly, considering Kenny's recent behaviour and this
non-discussion looks to be more of the same.

Frank Slootweg wrote:
Paul wrote:
Kenny McCormack wrote:

A daemon is a service.
A fish is not a bicycle.
This is the IIS FTPd service.

Listening on port 21.

https://i.postimg.cc/cC0LddCN/ftp.gif

Paul

I tend to agree [1] with Kenny.

A (Windows) service can be considered to fall under the general
computer term "daemon".

BUT, a daemon is not necessarily a (Windows) service. I.e. you can
write a program which acts as a daemon, but is *not* a (Windows)
service, i.e. it's *not* listed my services.msc.

IOW, a Mercedes is a car, but a car is not necessarily a Mercedes.

So (IMO) you should have written "A (Windows) service is a daemon.".
That would have been correct, but irrelevant for the scenario Kenny was
describing.

[1] Very reluctantly, considering Kenny's recent behaviour and this
non-discussion looks to be more of the same.

One of the benefits of writing a daemon as a service, is
it fits into the service framework. You get automatic
monitoring for free. If the service dies, the system
has restart policies for it.

A service also uses fewer resources.

Many services do not execute even one CPU tick during
a given second.

Some services are constantly gnawing on the CPU. They never stop.

The OS may have a couple hundred services, but the vast majority
are the "quiet kind".

Some services are manually started, for attack surface
reasons. The service that holds the TrustedInstaller token,
isn't running all the time. If you have a copy of the program
that acquires the TrustedInstaller token, you have to start
the service manually your own self, in order to be able to
acquire a copy of the token. Many other system paths, automatically
start whatever holds the TrustedInstaller token. If you run "Setup.exe"
from something, that would be a trigger condition for a sequence
of that nature.

Yes, you can write an idiotic program that functions
as a daemon.

You can load up scheduled tasks with a set of entries to
keep your creation running. Now you have no convenient
command line commands to manage the daemon. You can always
create them yourself, because you love work, and you love
to clutter an OS with irrelevant crap (Apple, I'm lookin
at you).

You can pay a runtime price for running a full process.
Chances are, it will use slightly more CPU than if loaded
as a service in a SVCHOST.

In terms of Task Manager, your creation now sticks out like
a sore thumb, and will tempt users to kill it for all sorts
of reasons. They will see "Wally.exe" running and go
"why not kill this?". That's what users do.

While you *can* do that, your software developer peers
will think you're from Apple or something. Apple
always does the converse of whatever a Windows
developer would consider a "best practice".

Your daemon would still not be a daemon.
It would be a process. A process propped up by
"a variety of things you shouldn't be doing".

I picked my example (ftpd) for a reason.
As an analog. As a best practice.

I'm sure in Linux or Unix, you can do stupid
stuff too. Like instead of creating a daemon
and using init/systemd tools intended for
daemon launch/control, using your own creative
methods. But, others are going to laugh at
you, and your "hayseed ways". What will you
achieve by doing that ? Will you be putting
that project on your resume ? As an indicator
of "what you're capable of" ?

Paul

In article , Paul wrote:
Kenny McCormack wrote:

A daemon is a service.

A fish is not a bicycle.


This is the IIS FTPd service.

Listening on port 21.

The below sig describes well what this thread has degenerated into.

--
Faced with the choice between changing one's mind and proving that there is
no need to do so, almost everyone gets busy on the proof.

- John Kenneth Galbraith -