[Prev][Next][Index][Thread]
Re: Problems with registering executor?
> The exiting after registering is normal, but the crashing is not. Are
> you running executor under gdb? Is more than one Executor active on
> your network or machine at any given time?
Not running under gdb. Don't know if anyone else on the network is running
Executor (I'm on a dorm network).
> You can now purchase site licenses for Executor for a fixed number of
> simultaneous users on your network. People who buy a copy for
> personal use are really purchasing a site license for one user. When
> you run Executor, it checks the local network for other Executors to
> make sure you aren't using more copies simultaneously than your
> license allows. We have seen the SIGIO from the broadcast packet kill
> Executor under gdb (looks like a gdb bug), but not elsewhere.
This all makes sense. BTW, does it consider multiple instances of executor
running under one username on one machine to be one license or multiple
licenses? I'm still getting the error. Unfortunately, as I know next to
nothing about TCP/IP programming under Linux, I don't know how to check if
my broadcast address is working properly. If someone could pass along a
quick bit of C to do a test broadcast, I would be grateful. In case it
makes any difference, I'm running Slackware 2.0 upgraded to kernel 1.1.75
and XF 3.1.1. Everything else is fairly vanilla. Do I need to update my
netutils or anything like that?
> You can turn off the site license check with:
>
> executor -checknet 0
This solves the problem. The next question, of course, is what is futzed
with my system that makes the net checks a problem.
--Toby Everett
References: