1. Daemon Tools Windows 10
2. Remove Programs From Startup Windows 7
3. Stopped Daemon Tools Startup Windows 7
4. Startup Windows 7

Can my python script spawn a process that will run indefinitely?

I'm not too familiar with python, nor with spawning deamons, so I cam up with this:

The process continues to run past python.exe, but is closed as soon as I close the cmd window.

Startup program entry details: DAEMON Tools Lite (DTLite.exe) This page expands upon the information already available for this entry in the Pacman's Portal Windows start-up programs database. DAEMON Tools is a disk image emulator for Microsoft Windows that mounts images of DVD and CD media on virtual drives. The program is able to defeat most copy protection schemes such as. Threat's profile. Win32 (Windows XP, Vista/7, 8/8.1, Windows 10) Google Chrome, Mozilla Firefox, Internet Explorer, Safari Windows Registry characteristic that allows programs to be applied automatically when opening the system boots can be treated by Daemon to cheat attempts to remove itself during the proceeding of badware removal.

zzandyzzandy

3 Answers

Using the answer Janne Karila pointed out this is how you can run a process that doen't die when its parent dies, no need to use the win32process module.

DETACHED_PROCESS is a Process Creation Flag that is passed to the underlying CreateProcess function.

zzandyzzandy

This question was asked 3 years ago, and though the fundamental details of the answer haven't changed, given its prevalence in 'Windows Python daemon' searches, I thought it might be helpful to add some discussion for the benefit of future Google arrivees.

There are really two parts to the question:

1. Can a Python script spawn an independent process that will run indefinitely?
2. Can a Python script act like a Unix daemon on a Windows system?

The answer to the first is an unambiguous yes; as already pointed out; using subprocess.Popen with the creationflags=subprocess.CREATE_NEW_PROCESS_GROUP keyword will suffice:

Note that, at least in my experience, CREATE_NEW_CONSOLE is not necessary here.

That being said, the behavior of this strategy isn't quite the same as what you'd expect from a Unix daemon. What constitutes a well-behaved Unix daemon is better explained elsewhere, but to summarize:

1. Close open file descriptors (typically all of them, but some applications may need to protect some descriptors from closure)
2. Change the working directory for the process to a suitable location to prevent 'Directory Busy' errors
3. Change the file access creation mask (os.umask in the Python world)
4. Move the application into the background and make it dissociate itself from the initiating process
5. Completely divorce from the terminal, including redirecting STDIN, STDOUT, and STDERR to different streams (often DEVNULL), and prevent reacquisition of a controlling terminal
6. Handle signals, in particular, SIGTERM.

The reality of the situation is that Windows, as an operating system, really doesn't support the notion of a daemon: applications that start from a terminal (or in any other interactive context, including launching from Explorer, etc) will continue to run with a visible window, unless the controlling application (in this example, Python) has included a windowless GUI. Furthermore, Windows signal handling is woefully inadequate, and attempts to send signals to an independent Python process (as opposed to a subprocess, which would not survive terminal closure) will almost always result in the immediate exit of that Python process without any cleanup (no finally:, no atexit, no __del__, etc).

Rolling your application into a Windows service, though a viable alternative in many cases, also doesn't quite fit. The same is true of using pythonw.exe (a windowless version of Python that ships with all recent Windows Python binaries). In particular, they fail to improve the situation for signal handling, and they cannot easily launch an application from a terminal and interact with it during startup (for example, to deliver dynamic startup arguments to your script, say, perhaps, a password, file path, etc), before 'daemonizing'. Additionally, Windows services require installation, which -- though perfectly possible to do quickly at runtime when you first call up your 'daemon' -- modifies the user's system (registry, etc), which would be highly unexpected if you're coming from a Unix world.

In light of that, I would argue that launching a pythonw.exe subprocess using subprocess.CREATE_NEW_PROCESS_GROUP is probably the closest Windows equivalent for a Python process to emulate a traditional Unix daemon. However, that still leaves you with the added challenge of signal handling and startup communications (not to mention making your code platform-dependent, which is always frustrating).

That all being said, for anyone encountering this problem in the future, I've rolled a library called daemoniker that wraps both proper Unix daemonization and the above strategy. It also implements signal handling (for both Unix and Windows systems), and allows you to pass objects to the 'daemon' process using pickle. Best of all, it has a cross-platform API:

For that purpose you could daemonize your python process or as you are using windows environment you would like to run this as a windows service.

You know i like to hate posting only web-links:

But for more information according to your requirement:

A simple way to implement Windows Service. read all comments it will resolve any doubt

Daemon Tools Windows 10

If you really want to learn more

First read this

what is daemon process or creating-a-daemon-the-python-way

Remove Programs From Startup Windows 7

update:Subprocess is not the right way to achieve this kind of thing

Stopped Daemon Tools Startup Windows 7

Rahul Gautam

Startup Windows 7

Rahul Gautam

Not the answer you're looking for? Browse other questions tagged pythonwindowsdaemon or ask your own question.

I lately installed Daemon tools lite on my 64bit win7 pc. Few startups after this and a couple hours of use, my pc froze completely, only the mouse cursor moved (clicking anything or any key presses don't have any effect, not even ctrl alt del). I unplugged the pc and now this same condition occurs 2-3 minutes after booting up, or even sooner if I try to open any program like chrome, then it freezes instantly. To me the timing would strongly indicate it's something to do with daemon tools, since that's the only recent change to my pc. I tried to boot up in safe mode, and it worked fine. I then proceeded to uninstall daemon, which too seemed to work correctly, but did not resolve the issue. Safe mode doesn't seem to be completely immune to these symptons, since I couldn't get notepad, calculator, my computer and many other programs to start at all. After some googling I found some instructions involving changing SPTD's registry entry to disable it to fix the problem, and regedit did work, but there was no sptd folder where I was supposed to look for it. I do have a linux live cd at hand if I need to manipulate any files and I know how to use it. I had this exact same problem a year ago, also after installing daemon tools. At that time I resorted to reinstalling windows. I would like to know if there are any other ideas to try, as I would need this computer as soon as possible to do some work. There is no risk of data loss involved, everything important is on another hdd, but I would like to avoid having to go through reinstalling all of my software, as there is quite a lot.

edit: oh, and my windows is on a 60gt ssd, so there are no system recovery points :/