macgetty(1M) macgetty(1M)NAME macgetty - handles the running of Login and related programs SYNOPSIS macgetty [-iscsi-id]... ARGUMENTS -iscsi-id Specifies the SCSI ID of drives containing a Macintosh file system that the Finder in A/UX ignores. It does not place a disk icon of the specified disk on the desktop, making it inaccessible. DESCRIPTION macgetty creates the Macintosh environment that supports a graphical interface during the log-in process and sets up a work session based on the session type selected in Login. The /etc/loginrc script is normally responsible for overall login support as described in loginrc(1M). It turns control over to macgetty to do most of the work. The macgetty program initializes a Macintosh environment, launching the Login program as a temporary Finder replacement. When a user has provided correct log-in information and dismissed the dialog box, Login shuts down the Macintosh environment so that macgetty can restart it according to the user's desired session type. Normally that is a 32-bit session type, which supports the Macintosh desktop and Macintosh applications. To allow a shell script to dispatch Macintosh session types, macgetty runs a shell in a special way by giving it the one-command option (-c) and a file argument that is a shell script. The type of shell run is obtained from /etc/passwd for a particular account. In turn, that determines which one of the shell setup files are run to customize a particular user environment, either the .login or the .profile file in the home directory for a particular user. So that the work session being started can be accounted for correctly - and so that the customizations a user may have put in place for their own environment are honored (such as the use of their own session-configuring script, the use of a personalized system folder, and so forth) - the macgetty programs runs this script under the user ID passed to it from Login. Note: Do not place commands in your shell setup files that launch Macintosh programs. At the time those setup files are run, the Macintosh Toolbox environment is not initialized. To work around that restriction, you can launch Macintosh applications through a March 1993 1
macgetty(1M) macgetty(1M)subshell that has an associated delay (see sleep(1)); More preferably, you should place the desired Macintosh documents or applications in the Startup Items folder in a System Folder dedicated to you (see systemfolder(1)). The user indicates the session type in the ``Session Types'' menu item, available through the ``Options'' menu of the Login program. Based upon the user's choice, macgetty runs a session-configuring script, as indicated for the following session types: Console Emulator This is the exception. No session-configuring script is run for the Console Emulator session type. A/UX Finder (24-bit) Causes macgetty to run the /mac/bin/mac24 script, unless a .mac24 override script is found in the user's home directory. A/UX Finder (32-bit) Causes macgetty to run the /mac/bin/mac32 script, unless a mac32 override script is found in the user's home directory. X11 Causes macgetty to run the /usr/bin/X11/X script, unless a .X11 override script is found in the user's home directory. This alternative session type is present only if the X Window software packages have been installed from the system software installer CD- ROM. Normally, a user selects an A/UX Finder session type, which causes an appropriate session-configuring script to be run. However, if a user chooses a Console Emulator session type, the macgetty program does not run a session-configuring script. Instead, it sets up a conventional UNIX operating environment (command interface) by running the shell program associated with the user's account in /etc/passwd. But first macgetty runs screenrestore to display the bitmap image for the Console Emulation window frame and an otherwise white screen. If the ``command interpreter'' field in the password file is empty, macgetty runs the default command interpreter, the Bourne shell (/bin/sh). If macgetty program detects that the program specified in the passwd file failed to run and the account that has been logged in to is root, the Bourne shell is run. If a shell was the program specified to run at login time, the selected 2 March 1993
macgetty(1M) macgetty(1M)shell runs its customary setup files such as .profile and .login (neither of which should contain commands that launch Macintosh applications). The shell or other program that was started in this way continues to run until a user enters logout, exit, or equivalent command for the program selected to run at login time. The environmental variables are initialized as listed following. General information about values passed to the process environment is provided in environ(5). These values are used by a shell to help customize its own operation. Besides FINDER_EDITOR, many other environmental values affect the Finder and other Macintosh programs in A/UX. However, they are not given default values by macgetty (refer to startmac(1M)). HOME=login-directory PATH=/bin:/usr/bin:/usr/ucb:/mac/bin LOGNAME=login-name TERM=mac2 SHELL=last-field-of-passwd-entry MAIL=/usr/mail/login-name FINDER_EDITOR=/mac/bin/TextEditor EDITOR=/usr/bin/vi DISPLAY=host-name:0.0 SESSION_TYPE=session-name Most of these variables establish preference settings that customize the command-interpretation process (see csh(1), ksh(1), sh(1)). An exception is FINDER_EDITOR. It contains the pathname of the editing application that is launched when you open an A/UX text document icon from within the Finder. Because the Finder does not automatically run in Console Emulator mode, you would have to launch it yourself by running one of the session-configuring scripts, such as /mac/bin/mac32. FILES $HOME/.cshrc Personal startup file for csh $HOME/.login Personal startup file interpreted at login time for csh $HOME/.profile Personal startup file interpreted at login time for sh and ksh /etc/cshrc Systemwide startup file interpreted upon initial running of csh /etc/macgetty Executable file March 1993 3
macgetty(1M) macgetty(1M)/etc/motd Text file containing the "message of the day," which is typically used for system identification /etc/passwd Password file /etc/profile Systemwide startup file interpreted upon initial running of sh and ksh /etc/shells Text file specifying the shell programs that are capable of supporting all session types /mac/bin/mac24 Session-configuring executable file /mac/bin/mac32 Session-configuring executable file /usr/bin/X11 Session-configuring executable file SEE ALSO getty(1M), init(1M), loginrc(1M) autologin(4) in A/UX Programmer's Reference 4 March 1993