Here is a message from Lee Hirz, one of the former Mailman developers:
Mailman sends and receives messages locally in 2 ways. One method is to can send and receive messages as soon as the user hits the return on the SEND command. Because MailMan is configured to run according to a standar
The submananagers are the proceses that actually do the work (the
thread pool, if you will). It Taskman goes long enough without any work
to do, th submanagers will shut down anyway. But the manager will
always start submanagers when they are needed. Off the top of my head,
I'm not sure if submanag
OK Nick,
When I use the menu system to call XUTM WAIT, it asks
if submanagers should be shut down (I answered NO).
It then says: Done. I then do option XUTM ZTMON, and
it does not show taskman in a wait state. Perhaps
because I didn't stop the submanagers...
Don't worry about answering this.
The output of D ^ZTMON will show the submanagers as in
waiting state.
Bye
Nick
--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote:
> Nick,
>
> I just played with putting my Taskman into and then
> back out of the wait state.
>
> I couldn't immediately tell that it was in the wait
> state. How did
Nick,
I just played with putting my Taskman into and then
back out of the wait state.
I couldn't immediately tell that it was in the wait
state. How did you tell it was stuck in wait?
Thanks
Kevin
--- Nick James <[EMAIL PROTECTED]> wrote:
> Hi
> Finally I found the culprit.
> Actually the Ta
Hi
Finally I found the culprit.
Actually the Taskman was in WAIT state. As soon as I
changed the state, all the messages reached their
corresponding recipients.
Bye
Nick
--- "Nancy E. Anthracite" <[EMAIL PROTECTED]>
wrote:
> My guess it that you didn't have any problems only
> because you put UCI
My guess it that you didn't have any problems only because you put UCI in all
the places that needed UCI and VOL in all of the places that needed VOL. Had
you called whatever was in UCI in the VistA you started with, and VOL what
was in the VOL, you would have had to have changed it in fewer pl
For what it is worth, it seems that most of the
problems that I have hear people talk about on this
board in regards to taskman, is a problem with the
VOL,UCI etc. issue. Most recommend using the defaults
provided by the system, but it seems that this leads
poeple to problems. I cleared out all t
I have no idea if this will help, but I was looking around trying to find out
what this partition thing is all about, and it looks like it might have to do
with getting a share of processor time and thing sitting in queues waiting to
get that time. It is mentioned in here. Maybe it will give y
Hi
The CPRS problem was due to the change in file access
rights. That has been solved. But the "Waiting for a
partition" problem, does not seem to be over yet.
Nick
--- Kevin Toppenberg <[EMAIL PROTECTED]> wrote:
> Nick,
>
> Do you have a way to make your server accessible on
> the internet for
Nick,
Do you have a way to make your server accessible on
the internet for someone else to poke around on?
I'd be willing to look at it for a couple of minutes
if you want to contact me off-board.
I'm self taught, so no promises as to whether or not I
can get you up.
Kevin
[EMAIL PROTECTED]
--
Hi
I was able to overcome the previous problem with the
command GO^XMKPLQ and GO^XMTDT, to run
the "MOVER" and "TICKLER".
But still I was unable to send and receive messages.
So I just checked to see the tasks
running in TASKMAN, whose screen shot I am giving
below :
510: ^LRCAPPH, COLLECT PH
12 matches
Mail list logo
