[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

The Terminal Program - File Server Init File - Thank

    Date: Wed, 26 Feb 1992 07:10 EST
    From: rm@ki2.informatik.uni-hamburg.de (Ralf Moeller)

    Thank you again for the replies.

    Filer Server Init File:

    My misconception was that the File Server is started automatically when
    (some) services are enabled as is the case with the Store-and-Forward
    Mailer. Logging in as user File-Server might be useful when there is a
    Symbolics that serves as a File Server only. Since I configured our
    site to use UNIX machines as servers together with NFS, this is not
    relevant for me. Thus, one solution is to write appropriate forms
    to start the File Server into my init file and enable (network) services
    after logging in.

Your misconception is correct.  When services are enabled, all servers
are enabled, including the file server.  This happens on all Lisp
Machines; there is no special way of designating a machine as a
dedicated File Server.

Services are normally enabled automatically whenever a machine boots,
unless it has "Server Machine: Yes" in its namespace entry; you
shouldn't need to put (net:enable-services) in your init file.  The
assumption is that on dedicated servers you might want to run some
special configuration programs before allowing clients to access it; for
example, a file server might need to turn on access control.  You would
create a special login name for the server, and put the configuration
routines in its init file, and have the init file end with a call to

    The Telnet Program:

    I never experienced any problems with Emacs and the X-Server as Phil has
    reported. However, using the X-Server is really no Fahrvergn"ugen on a
    3640 :-). So I resorted to the Terminal Program (with meta now working).

True, the X server is a snail on a 3640.  It's written in C, and 3640's
don't have the byte addressing microcode that C depends on to get any
reasonable kind of speed.