Hi,
I do not know...
The normal way to set the communication socket is via ARSetServerPort, or
the env variable ARTCPPORT.
It is there in 6.3, and may stem from a time where you went to different
TCP-sockets depending on your RPC-number. Correct me if I am wrong, but I
think that everything now always goes through a single TCP-port.
Best Regards - Misi, RRR AB, http://www.rrr.se
Products from RRR Scandinavia (Best R.O.I. Award at WWRUG10):
* RRR|License - Not enough Remedy licenses? Save money by optimizing.
* RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs.
Find these products, and many free tools and utilities, at http://rrr.se.
> Hi all,
>
> Does anyone know what the session configuration variable
> AR_SESS_LOCK_TO_SOCKET_NUMBER does?
>
> Its name would imply something to do with using a specific socket
> descriptor
> for..something, but its not clear what. The docs don't say much either.
>
> Setting it to various values (valid and non-valid socket descriptors)
> results in errors, so, empirically, it seems unrelated to that.
>
> For what its worth, I'm using the 7.0 C libraries.
>
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
>
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
