---------- Forwarded message ----------
Date: Tue, 4 Mar 1997 13:47:52 -0800 (PST)
From: majordomo@livingston.com
To: oldman@mitec.net
Subject: Majordomo results: Re: Simultaneous logins
-->>>> On Tue, 4 Mar 1997, Gary E. Miller wrote: **** Command 'on' not recognized. >>>> > > Can't one address the race conditions by waiting five minutes **** Command '>' not recognized. >>>> > > and checking to see if the one user is still logged into the **** Command '>' not recognized. >>>> > > same two ports? Or better yet, wait five minutes and then **** Command '>' not recognized. >>>> > > telnet into the PM's and show sessions; that will eliminate **** Command '>' not recognized. >>>> > > the lost-logoff problem. Since duplicates will be rare, **** Command '>' not recognized. >>>> > > the extra overhead of the telnet should be small (once per hour or so). **** Command '>' not recognized. >>>> > I have found that sometimes the PM2 thinks a user is still connected **** Command '>' not recognized. >>>> > but that is not so. Before kicking someone off I always ping the **** Command '>' not recognized. >>>> > connection to check that it is up. **** Command '>' not recognized. >>>> > That is why bpmtools only sends warning mail to duplicate users. **** Command '>' not recognized. >>>> > BTW, bpmtools uses the "secret" portmaster protocol to check who is **** Command '>' not recognized. >>>> > on. It seems much faster, and more reliable than running a psuedo **** Command '>' not recognized. >>>> > telnet session. **** Command '>' not recognized. >>>> >>>> Are you sure about the speed, I have two versions of "pmwho", the only **** Command 'are' not recognized. >>>> using telnet is much faster than the one using bpmtools. **** Command 'using' not recognized. >>>> >>>> Also, I have never seen a user that has been shown as logged in on the **** Command 'also,' not recognized. >>>> portmaster when he/she was actually not. **** Command 'portmaster' not recognized. >>>> >>>> Sincerely, **** Command 'sincerely,' not recognized. >>>> Lee Kuo **** Command 'lee' not recognized. >>>> >>>> **** No valid commands found. **** Commands must be in message BODY, not in HEADER.
**** Help for majordomo:
This is Brent Chapman's "Majordomo" mailing list manager, version 1.93.
In the description below items contained in []'s are optional. When providing the item, do not include the []'s around it.
It understands the following commands:
subscribe [<list>] [<address>] Subscribe yourself (or <address> if specified) to the named <list>.
unsubscribe [<list>] [<address>] Unsubscribe yourself (or <address> if specified) from the named <list>.
get [<list>] <filename> Get a file related to <list>.
index [<list>] Return an index of files you can "get" for <list>.
which [<address>] Find out which lists you (or <address> if specified) are on.
who [<list>] Find out who is on the named <list>.
info [<list>] Retrieve the general introductory information for the named <list>.
lists Show the lists served by this Majordomo server.
help Retrieve this message.
end Stop processing commands (useful if your mailer adds a signature).
Commands should be sent in the body of an email message to "majordomo"or to "<list>-request".
The <list> parameter is only optional if the message is sent to an address of the form "<list>-request".
Commands in the "Subject:" line NOT processed.
If you have any questions or problems, please contact "majordomo-owner".