Re: How to force a thread to stop

"Gerhard Fiedler" <[EMAIL PROTECTED]> wrote: | On 2006-08-04 02:33:07, H J van Rooyen wrote: | | > The next step above the 555 is a PIC... then you can steal power from the | > RS-232 line - and its a small step from "PIC" to "PIG"... | | I see... you obviously know what to do, if you want to :)

Re: How to force a thread to stop

On 2006-08-04 02:33:07, H J van Rooyen wrote: > The next step above the 555 is a PIC... then you can steal power from the > RS-232 line - and its a small step from "PIC" to "PIG"... I see... you obviously know what to do, if you want to :) But I'm not sure such a device alone is of much help in

Re: How to force a thread to stop

"Gerhard Fiedler" <[EMAIL PROTECTED]> wrote: | On 2006-08-03 06:07:31, H J van Rooyen wrote: | | > Thanks - will check it out - seems a lot of money for 555 functionality | > though | > | > Especially if like I, you have to pay for it with Rand - I have started | > to call the local currency

Re: How to force a thread to stop

"Carl J. Van Arsdall" <[EMAIL PROTECTED]> wrote: | Alex Martelli wrote: | > H J van Rooyen <[EMAIL PROTECTED]> wrote: | > | > | >> "Paul Rubin" Writes: | >> | >> | "H J van Rooyen" <[EMAIL PROTECTED]> writes: | >> | > *grin* - Yes of course - if the WDT was enabled - i

Re: How to force a thread to stop

"Carl J. Van Arsdall" <[EMAIL PROTECTED]> writes: > Yea, there are other free solutions you might want to check out, I've > been looking at ganglia and nagios. These require constant > communication with a server, however they are customizable in that you > can have the server take action on vario

Re: How to force a thread to stop

Alex Martelli wrote: > H J van Rooyen <[EMAIL PROTECTED]> wrote: > > >> "Paul Rubin" Writes: >> >> | "H J van Rooyen" <[EMAIL PROTECTED]> writes: >> | > *grin* - Yes of course - if the WDT was enabled - its something that >> | > I have not seen on PC's yet... >> | >> |

Re: How to force a thread to stop

On 2006-08-03 06:07:31, H J van Rooyen wrote: > Thanks - will check it out - seems a lot of money for 555 functionality > though > > Especially if like I, you have to pay for it with Rand - I have started > to call the local currency Runt... Depending on what you're up to, you can make suc

Re: How to force a thread to stop

"Alex Martelli" <[EMAIL PROTECTED]> Wrote: | H J van Rooyen <[EMAIL PROTECTED]> wrote: | | > "Paul Rubin" Writes: | > | > | "H J van Rooyen" <[EMAIL PROTECTED]> writes: | > | > *grin* - Yes of course - if the WDT was enabled - its something that | > | > I have not seen

Re: How to force a thread to stop

H J van Rooyen <[EMAIL PROTECTED]> wrote: > "Paul Rubin" Writes: > > | "H J van Rooyen" <[EMAIL PROTECTED]> writes: > | > *grin* - Yes of course - if the WDT was enabled - its something that > | > I have not seen on PC's yet... > | > | They are available for PC's, as pl

Re: How to force a thread to stop

"Damjan" <[EMAIL PROTECTED]> wrote: | > | A common recovery mechanism in embedded systems is a watchdog timer, | > | which is a hardware device that must be poked by the software every | > | so often (e.g. by writing to some register). If too long an interval | > | goes by without a poke, the WD

Re: How to force a thread to stop

> | A common recovery mechanism in embedded systems is a watchdog timer, > | which is a hardware device that must be poked by the software every > | so often (e.g. by writing to some register). If too long an interval > | goes by without a poke, the WDT hard-resets the cpu. Normally the > | softw

Re: How to force a thread to stop

"H J van Rooyen" <[EMAIL PROTECTED]> writes: > That is cool, I was not aware of this - added to a long running server it will > help to make the system more stable - a hardware solution to hard to find bugs > in Software - (or even stuff like soft errors in hardware - speak to the > Avionics boys a

Re: How to force a thread to stop

"Dennis Lee Bieber" <[EMAIL PROTECTED]> wrote: | On Fri, 28 Jul 2006 08:27:18 +0200, "H J van Rooyen" | <[EMAIL PROTECTED]> declaimed the following in comp.lang.python: | | > | > Dennis - did your OS not have a ticker running? | > | That ancient machine, while round-robin, multi-priority, | pre-e

Re: How to force a thread to stop

"Paul Rubin" Writes: | "H J van Rooyen" <[EMAIL PROTECTED]> writes: | > *grin* - Yes of course - if the WDT was enabled - its something that | > I have not seen on PC's yet... | | They are available for PC's, as plug-in cards, at least for the ISA | bus in the old days

Re: How to force a thread to stop

"H J van Rooyen" <[EMAIL PROTECTED]> writes: > *grin* - Yes of course - if the WDT was enabled - its something that > I have not seen on PC's yet... They are available for PC's, as plug-in cards, at least for the ISA bus in the old days, and almost certainly for the PCI bus today. -- http://mail.

Re: How to force a thread to stop

"Paul Boddie" <[EMAIL PROTECTED]> writes: > Anyway, the py.execnet thing is presumably designed to work over the > Internet and over local networks, with the benefit of SSH being that it > applies well to both domains. Whether it's a better solution for the > questioner's problem than established a

Re: How to force a thread to stop

"Paul Rubin" Wrote: | "H J van Rooyen" <[EMAIL PROTECTED]> writes: | > So on a processor that does not have protected instructions - if an | > idiot writes something to the following effect : | > | > *instructions to disable interrupts* | > | > followed by : | > | > *in

Re: How to force a thread to stop

Paul Rubin wrote: > "Paul Boddie" <[EMAIL PROTECTED]> writes: > > Whether this solves the questioner's problems remains to be seen, but > > issues of handling SSH-based communications streams do seem to be > > addressed. > > Actually I don't understand the need for SSH. This is traffic over a > LA

Re: How to force a thread to stop

"H J van Rooyen" <[EMAIL PROTECTED]> writes: > So on a processor that does not have protected instructions - if an > idiot writes something to the following effect : > > *instructions to disable interrupts* > > followed by : > > *instructions that go into an infinite loop AND that make no OS cal

Re: How to force a thread to stop

"Dennis Lee Bieber" <[EMAIL PROTECTED]> Wrote: | On Thu, 27 Jul 2006 08:48:37 -0400, Jean-Paul Calderone | <[EMAIL PROTECTED]> declaimed the following in comp.lang.python: | | > | > If a thread never performs any I/O operations, signal handlers will still | > get invokes on the arrival of a signa

Re: How to force a thread to stop

Paul Rubin wrote: > Actually I don't understand the need for SSH. Who are you and what have you done with the real Paul Rubin? > This is traffic over a > LAN, right? Is all of the LAN traffic encrypted? That's unusual; SSH > is normally used to secure connections over the internet, but the > l

Re: How to force a thread to stop

Paul Rubin wrote: > "Paul Boddie" <[EMAIL PROTECTED]> writes: > > Whether this solves the questioner's problems remains to be seen, but > > issues of handling SSH-based communications streams do seem to be > > addressed. > > Actually I don't understand the need for SSH. This is traffic over a > LA

Re: How to force a thread to stop

Paul Rubin wrote: > "Paul Boddie" <[EMAIL PROTECTED]> writes: > >> Whether this solves the questioner's problems remains to be seen, but >> issues of handling SSH-based communications streams do seem to be >> addressed. >> > > Actually I don't understand the need for SSH. This is traffic o

Re: How to force a thread to stop

"Paul Boddie" <[EMAIL PROTECTED]> writes: > Whether this solves the questioner's problems remains to be seen, but > issues of handling SSH-based communications streams do seem to be > addressed. Actually I don't understand the need for SSH. This is traffic over a LAN, right? Is all of the LAN tr

Re: How to force a thread to stop

Carl J. Van Arsdall wrote: > Well, I guess I'm thinking of an event driven mechanism, kinda like > setting up signal handlers. I don't necessarily know how it works under > the hood, but I don't poll for a signal. I setup a handler, when the > signal comes, if it comes, the handler gets thrown in

Re: How to force a thread to stop

Paul Rubin wrote: > > Instead of using os.system, maybe you want to use one of the popens or > the subprocess module. For each ssh, you'd spawn off a process that > does the ssh and communicates back to the control process through a > set of file descriptors (Unix pipe endpoints or whatever). The

Re: How to force a thread to stop

On Thu, 27 Jul 2006 02:30:03 -0500, Nick Craig-Wood <[EMAIL PROTECTED]> wrote: >[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Hans wrote: >> > Is there a way that the program that created and started a thread also >> > stops >> > it. >> > (My usage is a time-out). >> > >> > E.g. >> > >> > threa

Re: How to force a thread to stop

On Thu, 27 Jul 2006 07:07:05 GMT, Dennis Lee Bieber <[EMAIL PROTECTED]> wrote: >On Wed, 26 Jul 2006 17:38:06 -0700, "Carl J. Van Arsdall" ><[EMAIL PROTECTED]> declaimed the following in comp.lang.python: > >> Well, I guess I'm thinking of an event driven mechanism, kinda like >> setting up signal h

Re: How to force a thread to stop

[EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Hans wrote: > > Is there a way that the program that created and started a thread also stops > > it. > > (My usage is a time-out). > > > > E.g. > > > > thread = threading.Thread(target=Loop.testLoop) > > thread.start() # This thread is expected to

Re: How to force a thread to stop

Carl J. Van Arsdall wrote: > [EMAIL PROTECTED] wrote: > > Carl J. Van Arsdall wrote: > > > >> [EMAIL PROTECTED] wrote: > >> > >>> Carl J. Van Arsdall wrote: > >>> > >>> I don't get what threading and Twisted would to do for > >>> you. The problem you actually have is that you sometimes > >>> need

Re: How to force a thread to stop

Dennis Lee Bieber <[EMAIL PROTECTED]> writes: > Ugh... Seems to me it would be better to find some Python library > for SSH, something similar to telnetlib, rather than doing an > os.system() per command line. EACH of those os.system() calls probably > causes a full fork() operation on Linux/

Re: How to force a thread to stop

"Carl J. Van Arsdall" <[EMAIL PROTECTED]> wrote: 8< | point). Its not only important that the threads die, but that they die | with grace. There's lots of cleanup work that has to be done when | things exit or things end up in an

Re: How to force a thread to stop

Gerhard Fiedler wrote: > Carl J. Van Arsdall wrote: > > Well, I guess I'm thinking of an event driven mechanism, kinda like > > setting up signal handlers. I don't necessarily know how it works under > > the hood, but I don't poll for a signal. I setup a handler, when the > > signal comes, if it

Re: How to force a thread to stop

On 2006-07-26 21:38:06, Carl J. Van Arsdall wrote: >>> Also, threading's condition and event constructs are used a lot >>> (i talk about it somewhere in that thing I wrote). They are easy to use >>> and nice and ready for me, with a server wouldn't I have to have things >>> poll/wait for messa

Re: How to force a thread to stop

Gerhard Fiedler wrote: > On 2006-07-26 19:08:44, Carl J. Van Arsdall wrote: > > >> Also, threading's condition and event constructs are used a lot >> (i talk about it somewhere in that thing I wrote). They are easy to use >> and nice and ready for me, with a server wouldn't I have to have thi

Re: How to force a thread to stop

On 2006-07-26 19:08:44, Carl J. Van Arsdall wrote: > Also, threading's condition and event constructs are used a lot > (i talk about it somewhere in that thing I wrote). They are easy to use > and nice and ready for me, with a server wouldn't I have to have things > poll/wait for messages? Ho

Re: How to force a thread to stop

[EMAIL PROTECTED] writes: > > Have you looked at POSH yet? http://poshmodule.sf.net > > Paul, have you used POSH? Does it work well? Any major gotchas? I haven't used it. I've been wanting to try. I've heard it works ok in Linux but I've heard of problems with it under Solaris. Now that I un

Re: How to force a thread to stop

On 2006-07-26 17:33:19, Carl J. Van Arsdall wrote: > Alright, if you read all that, thanks, and thanks for your input. Whether > or not I've agreed with anything, me and a few colleagues definitely > discuss each idea as its passed to us. For that, thanks to the python > list! I think you should

Re: How to force a thread to stop

Paul Rubin wrote: > "Carl J. Van Arsdall" <[EMAIL PROTECTED]> writes: > >> Alright, so manually running builds is going to be crazy and >> unmanageable. So what the people who came before me did to manage >> this scenario was to fork on thread per build. The threads invoke a >> series of calls

Re: How to force a thread to stop

Paul Rubin wrote: > Have you looked at POSH yet? http://poshmodule.sf.net Paul, have you used POSH? Does it work well? Any major gotchas? I looked at the paper... well, not all 200+ pages, but I checked how they handle a couple parts that I thought hard and they seem to have good ideas. I didn

Re: How to force a thread to stop

"Carl J. Van Arsdall" <[EMAIL PROTECTED]> writes: > Alright, so manually running builds is going to be crazy and > unmanageable. So what the people who came before me did to manage > this scenario was to fork on thread per build. The threads invoke a > series of calls that look like > > os.syste

Re: How to force a thread to stop

[EMAIL PROTECTED] wrote: > Carl J. Van Arsdall wrote: > >> [EMAIL PROTECTED] wrote: >> >>> Carl J. Van Arsdall wrote: >>> >>> I don't get what threading and Twisted would to do for >>> you. The problem you actually have is that you sometimes >>> need terminate these other process running ot

Re: How to force a thread to stop

Carl J. Van Arsdall wrote: > [EMAIL PROTECTED] wrote: > > Carl J. Van Arsdall wrote: > > > > I don't get what threading and Twisted would to do for > > you. The problem you actually have is that you sometimes > > need terminate these other process running other programs. > > Use spawn, fork/exec*

Re: How to force a thread to stop

Paul Rubin wrote: > "Carl J. Van Arsdall" <[EMAIL PROTECTED]> writes: > >> The problem I have is a large distributed system, that's the reality >> of it. The short summary, I need to use and control 100+ machines in >> a computing farm. They all need to share memory or to actively >> communica

Re: How to force a thread to stop

"Carl J. Van Arsdall" <[EMAIL PROTECTED]> writes: > The problem I have is a large distributed system, that's the reality > of it. The short summary, I need to use and control 100+ machines in > a computing farm. They all need to share memory or to actively > communicate with each other via some o

Re: How to force a thread to stop

[EMAIL PROTECTED] wrote: > Carl J. Van Arsdall wrote: > > I don't get what threading and Twisted would to do for > you. The problem you actually have is that you sometimes > need terminate these other process running other programs. > Use spawn, fork/exec* or maybe one of the popens. > > > I

Re: How to force a thread to stop

Carl J. Van Arsdall wrote: > Unfortunately this is due to the nature of the problem I am tasked with > solving. I have a large computing farm, these os.system calls are often > things like ssh that do work on locations remote from the initial python > task. I suppose eventually I'll end up using

Re: How to force a thread to stop

On 2006-07-25 13:55:39, Carl J. Van Arsdall wrote: > I'd be all for using processes but setting up communication between > processes would be difficult wouldn't it? I mean, threads have shared > memory so making sure all threads know the current system state is an > easy thing. I'm not sure ab

Re: How to force a thread to stop

Carl J. Van Arsdall wrote: > Jean-Paul Calderone wrote: > > On Mon, 24 Jul 2006 11:22:49 -0700, "Carl J. Van Arsdall" <[EMAIL > > PROTECTED]> wrote: > > > >> Steve Holden wrote: > >> > >>> Carl J. Van Arsdall wrote: > >>> [... rant ...] > >>> > >>> > So with this whole "hey mr. nice thread,

Re: How to force a thread to stop

"Carl J. Van Arsdall" <[EMAIL PROTECTED]> writes: > I'd be all for using processes but setting up communication between > processes would be difficult wouldn't it? I mean, threads have > shared memory so making sure all threads know the current system > state is an easy thing. With processes woul

Re: How to force a thread to stop

Gerhard Fiedler wrote: > On 2006-07-25 13:30:22, Carl J. Van Arsdall wrote: > > >>> Running os.system() in multiple threads strikes me as kind of whacked. >>> Won't they all compete to read and write stdin/stdout simultaneously? >>> >>> >> Unfortunately this is due to the nature of the p

Re: How to force a thread to stop

On 2006-07-25 13:30:22, Carl J. Van Arsdall wrote: >> Running os.system() in multiple threads strikes me as kind of whacked. >> Won't they all compete to read and write stdin/stdout simultaneously? >> > Unfortunately this is due to the nature of the problem I am tasked with > solving. I have a

Re: How to force a thread to stop

[EMAIL PROTECTED] wrote: > Carl J. Van Arsdall wrote: > [...] > >> My problem with the fact that python doesn't have some type of "thread >> killer" is that again, the only solution involves some type of polling >> loop. >> > > A polliing loop is neither required nor helpful here. > > [...]

Re: How to force a thread to stop

Dennis Lee Bieber wrote: > On Mon, 24 Jul 2006 10:27:08 -0700, "Carl J. Van Arsdall" > > My problem with the fact that python doesn't have some type of "thread > > killer" is that again, the only solution involves some type of polling > > loop. I.e. "if your thread of execution can be written so

Re: How to force a thread to stop

On 25 Jul 2006 05:51:47 -0700, Paul Rubin <"http://phr.cx"@nospam.invalid> wrote: >[EMAIL PROTECTED] writes: >> Threadicide would not solve the problems you actually have, and it >> tends to create other problems. What is the condition that makes >> you want to kill the thread? Make the victim thr

Re: How to force a thread to stop

[EMAIL PROTECTED] writes: > Threadicide would not solve the problems you actually have, and it > tends to create other problems. What is the condition that makes > you want to kill the thread? Make the victim thread respond to that > condition itself. If the condition is a timeout, one way to noti

Re: How to force a thread to stop

Carl J. Van Arsdall wrote: [...] > My problem with the fact that python doesn't have some type of "thread > killer" is that again, the only solution involves some type of polling > loop. A polliing loop is neither required nor helpful here. [...] > #Just pretend for the sake of arguement that 'o

Re: How to force a thread to stop

"Carl J. Van Arsdall" <[EMAIL PROTECTED]> writes: > > Communications through Queue.Queue objects can help. But if you > > research the history of this design decision in the language you > > should discover there are fairly sound rasons for not allowing > > arbitrary "threadicide". > > > Right, I'm

Re: How to force a thread to stop

On Mon, 24 Jul 2006 13:51:07 -0700, "Carl J. Van Arsdall" <[EMAIL PROTECTED]> wrote: >Jean-Paul Calderone wrote: >> On Mon, 24 Jul 2006 11:22:49 -0700, "Carl J. Van Arsdall" <[EMAIL >> PROTECTED]> wrote: >> >>> Steve Holden wrote: >>> Carl J. Van Arsdall wrote: [... rant ...]

Re: How to force a thread to stop

Steve Holden wrote: > Carl J. Van Arsdall wrote: > > >> >> > I take this to mean you don't want to do the necessary research? ;-) > Well, i've been looking at this on and off for quite some time now, I almost feel like I've seen it all in regards to the "thread killer" scenario. It co

Re: How to force a thread to stop

Carl J. Van Arsdall wrote: > Jean-Paul Calderone wrote: [...] >>This has been discussed many many times in the context of many many >>languages and threading libraries. If you're really interested, do >>the investigation Steve suggested. You'll find plenty of material. >> > > > I've been digg

Re: How to force a thread to stop

Jean-Paul Calderone wrote: > On Mon, 24 Jul 2006 11:22:49 -0700, "Carl J. Van Arsdall" <[EMAIL PROTECTED]> > wrote: > >> Steve Holden wrote: >> >>> Carl J. Van Arsdall wrote: >>> [... rant ...] >>> >>> So with this whole "hey mr. nice thread, please die for me" concept gets >>>

Re: How to force a thread to stop

On Mon, 24 Jul 2006 11:22:49 -0700, "Carl J. Van Arsdall" <[EMAIL PROTECTED]> wrote: >Steve Holden wrote: >> Carl J. Van Arsdall wrote: >> [... rant ...] >> >>> So with this whole "hey mr. nice thread, please die for me" concept gets >>> ugly quickly in complex situations and doesn't scale well at

Re: How to force a thread to stop

Steve Holden wrote: > Carl J. Van Arsdall wrote: > [... rant ...] > >> So with this whole "hey mr. nice thread, please die for me" concept gets >> ugly quickly in complex situations and doesn't scale well at all. >> Furthermore, say you have a complex systems where users can write >> pluggab

Re: How to force a thread to stop

Carl J. Van Arsdall wrote: [... rant ...] > So with this whole "hey mr. nice thread, please die for me" concept gets > ugly quickly in complex situations and doesn't scale well at all. > Furthermore, say you have a complex systems where users can write > pluggable modules. IF a module gets stu

Re: How to force a thread to stop

Dennis Lee Bieber wrote: > On Sat, 22 Jul 2006 14:47:30 +0200, "Hans" <[EMAIL PROTECTED]> declaimed > the following in comp.lang.python: > > >> Hi all, >> >> Is there a way that the program that created and started a thread also stops >> it. >> (My usage is a time-out). >> >> > Hasn'

Re: How to force a thread to stop

Lawrence D'Oliveiro <[EMAIL PROTECTED]> writes: > > Python has no threadicide method, and its absence is not an > > oversight. Threads often have important business left to do, such > > as releasing locks on shared data; killing them at arbitrary times > > tends to leave the system in an inconsiste

Re: How to force a thread to stop

In message <[EMAIL PROTECTED]>, [EMAIL PROTECTED] wrote: > Python has no threadicide method, and its absence is not an > oversight. Threads often have important business left to do, such > as releasing locks on shared data; killing them at arbitrary times > tends to leave the system in an inconsis

Re: How to force a thread to stop

Hi! >>> "threadicide" method I like this word... Michel Claveau -- http://mail.python.org/mailman/listinfo/python-list

Re: How to force a thread to stop

Hans wrote: > Hi all, > > Is there a way that the program that created and started a thread also stops > it. > (My usage is a time-out). > > E.g. > > thread = threading.Thread(target=Loop.testLoop) > thread.start() # This thread is expected to finish within a second > thread.join(2)# Or ti

How to force a thread to stop

Hi all, Is there a way that the program that created and started a thread also stops it. (My usage is a time-out). E.g. thread = threading.Thread(target=Loop.testLoop) thread.start() # This thread is expected to finish within a second thread.join(2)# Or time.sleep(2) ? if thread.isAliv