RE: Permissions problems with conserver 8.11

Thank you for the prompt response.

I am afraid I don't know what you mean about access.c entries showing
up.  Where will they show up?  Should I run conserver in daemon mode,
try to connect with console, then run conserver -D a second time?  I
tried just that, and found no access.c entries.

I also tried console -v unixlab2 but that did not show anything useful.
Then I recalled that the console command has many of the same switches
as conserver, so I ran this:

{unixlab2}/usr/local/etc> console -D -D -D unixlab2

There were many lines created of course but this one seems to be the
only relevant (or at least the most salient):

console: DEBUG: [console.c:465] GetPort: hostname=XXXXX.genesyslab.com
(console), ip=199.XX.XXX.XXX, port=782 

*X'ed out the hostname & IP for security reasons.  

This confirms my initial fears:  We have an extensive pre-existing
conserver network in our production environment using 7.1.3.  unixlab2
is not mentioned anywhere in the config of the production network, yet
somehow it attempts to reference one of the other conserver servers.
This raises new questions:
1.  Can I integrate an 8.1.1 server with the pre-existing 7.1.3 network?
(eventually we will upgrade the whole network)

2.  How can I separate this test environment from the production
environment?

Thanks again for your attention to this matter.  Your efforts are
greatly appreciated.

Phillip Pacheco
WIS-UNIX

-----Original Message-----
From: Bryan Stansell [mailto:bryan@conserver.com] 
Sent: Monday, September 19, 2005 2:10 PM
To: Phillip Pacheco
Cc: Bryan Stansell; users@conserver.com
Subject: Re: Permissions problems with conserver 8.11

On Mon, Sep 19, 2005 at 12:02:39PM -0700, Phillip Pacheco wrote:
> I ran conserver -D as you suggest, but there are no access.c entries.
I
> can see the readcfg entries which deal with the access section, see
> below.  Could there be something wrong with my config file which
causes
> conserver not to properly recognize the access section, or to not
> properly translate it into access.c commands?

the access.c entries will show up once you try and connect with the
client.  unless you're connecting to another conserver daemon, it'll
show something.

running 'console -v <console>' might show interesting things as well.
the combination of those should show something.

Bryan