🚀 go-pugleaf

In article <3pu4r7$g6j@clarknet.clark.net>,
Alex Batson <alexb@clark.net> wrote:
>HI all..
>
>Have a question..
>
>    We have an NLM on our server called NLICLEAR, which clears
>    'not-logged-in' connections on our 3.11 server.  Does anyone
>    know if we can configure that to ignore certain Ethernet
>    addresses, so it won't clear said addresses from the server?
>    We have a Cubix system with 5 processors in it (dial in server),
>    that maintain 5 not-logged-in connections [that is untill
>    someone logs in] on the server; and we don't want those
>    cleared.

I have the same problem, and have come upon a (partial) solution.  It
turns out that if a logged in user runs login again, the original user
is still connected (as seen in Monitor), but can't do anything except
complete, or fail the login program, at which time the connection
changes to the new user, or reverts to NOT-LOGGED-IN.  So, what I intend
to do for my Cubix processors is to have them login as a user with
minimal rights, then immediately execute login again.

To do this on bootup, I need to pass the "junk" account password on the
command line.  I know I've seen how to do this before, but didn't save
any of the posts...could someone pass this info on to me?

Thanks
-- 
Mark Taylor
OSU College of Medicine Division of Computing Services
mtaylor+@osu.edu     mtaylor@magnus.acs.ohio-state.edu
PHONE: (614) 292-6192              FAX: (614) 292-0745