| |
DK5SG > WAMPES 03.10.99 00:50l 49 Lines 1212 Bytes #-9487 (0) @ WW
BID : DK5SG9910022
Read: DG5MKU DB1RAS GUEST
Subj: Re: cnet: connect: Connection refused
Path: DB0AAB<DB0ZKA<DB0LX<DB0RBS<DB0SAO
Sent: 991002/1756Z @:DB0SAO.#BW.DEU.EU
This is because 2 instances of WAMPES still share the same directory
for communication sockets, eg /tcp/sockets. Starting the second
instance will remove the socket created by the first instance in this
directory, and disable all access by cnet to it.
oe1xya@oe1xab writes:
> From: OE1XYA @ OE1XAB.#OE1.AUT.EU (Afuverein_x)
> To: WAMPES @ WW
> X-Info: No login password
>
>
>
>
> hi all friend of wampes !
>
> if running the "net"-process in background it's possible
> to control with cnet. this works perfect, till running
> a second instance of net, of course with a different
> configuration file ( net.rc )
> the communication goes over the bridge utility.
> after exiting the second instance a start of cnet
> results in the following error message:
>
> # cnet
> connect: Connection refused
>
> the program terminates and shell-prompt appears.
> this can't be eliminated until terminating the
> background net-process and restarting.
>
> do you have the same situation ?
> any solutions ?
>
> environment: solaris 2.5.1 wampes 990710
>
>
> best regards from vienna
> hans
>
> oe1smc
>
>
>
--
Dieter Deyke - deyke@cocreate.fc.hp.com
- deyke@hotpop.com
- dk5sg@db0sao.ampr.org
Read previous mail | Read next mail
| |
