> If pmwho works like pmdial, pmcommand and pmreset than it uses TCP port
> 1643. Yes, the same one used by PM Console. By default, only one
> connection at a time is allowed on 1643. Simply increase the number of
> sessions by typing: "set max pmconsole X", where X is between 1 & 10.
> This shouldtake care of your problem.
pmwho uses the telnet port that you've configured on your Portmaster,
not the Portmaster protocol port (1643) - to be more accurate, some versions
of pmwho even open a literal telnet (via a pipe) to the portmaster.
The portmasters are set up to allow four administrative telnet sessions
in to the box - this value is hardcoded or stuffed in a variable that
Livingston hasn't released for public eating. :> The "set max pmconsole"
command will not change this value and has little to do with the operation
of pmwho, pmcom, and other remote portmaster management programs (mostly
written by Johan).
If you're experiencing a slew of "connection to host failed" messages,
it's likely that you're running several pmwho or pmcom-based scripts.
The best way to avoid this - and speed up your operation at the same
time - is to set up your monitoring/whatever programs around a central
file which contains the online users, and have that file updated at need
by pmwho - thereby eliminating several unnecessary pmwhos.
Mmm. Happy New Years, everyone. :)
-Dave