Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!rutgers!ames!ucbcad!ucbvax!apollo.UUCP!nelson_r From: nelson_r@apollo.UUCP (Rolf Nelson) Newsgroups: comp.sys.apollo Subject: Re: SR9.5 bug (or am I mistaken)? Message-ID: <8708201821.AA09080@apollo.UUCP> Date: Thu, 20-Aug-87 14:24:54 EDT Article-I.D.: apollo.8708201821.AA09080 Posted: Thu Aug 20 14:24:54 1987 Date-Received: Sat, 22-Aug-87 14:20:14 EDT Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 39 ---> It seems that under SR9.5, the shell background process symbol "&" is ineffective (I've only tried it in "/com/sh", don't know about the unix shells). Is this a bug? It ("&") works fine on SR9.5 here in all three shell environments. $ /systest/lst / >/tmp/disk_space & $ Oh, and while I'm at it, does anyone know if there is a startup file for SPM logins originating from an SIO line analagous to the "/sys/node_data/startup.spm" DM script? /sys/node_data/startup.spm is only read when the Server Process Manager first comes up to initialize things like SYSTYPE and UNIXLOGIN and to start servers/daemons like netman when the node boots. When you "crp" on a node it inherits a set of environment variables from the Server Process Manager including those intialized in the startup.spm file. So the startup.spm file for the SPM is analagous to the /sys/node_data/startup.19l{1280bw, etc...} files in that it is read only once when the DM and/or SPM is first started. If you are looking for a per login startup file for serial line logins equivalent to /sys/dm/startup_login.19l{1280bw} for per user login from the DM then that would be, `node_data/siologin/startup_sio.sh Every time siologin starts it read this file passing it the number of the SIO line as the first argument. See page 9-7 of the BSD4.2 admin guide for more info about this file and its use for UUCP. -- Rolf Nelson UUCP: {mit-erl,yale,uw-beaver}!apollo!nelson_r Apollo Computer ARPA: apollo!nelson_r@mit-eddie.arpa -------