Path: utzoo!attcan!uunet!decwrl!ucbvax!TRANSARC.COM!Craig_Everhart From: Craig_Everhart@TRANSARC.COM Newsgroups: comp.soft-sys.andrew Subject: Re: ?S directive in preferences (systype) Message-ID: Date: 9 Nov 90 18:10:45 GMT References: Sender: daemon@ucbvax.BERKELEY.EDU Organization: The Internet Lines: 18 The directive that's being checked in the version of Andrew that you have is ?C, not ?S. ?C is mnemonic for the ``cputype'' program that predated ``sys''. I believe that the next Andrew patch will make this ?S to conform to the documentation, or else will change the documentation to use ?C to conform to the implementation. The systype value is the one selected at compile time, generally from the installed system.h file. It could be overridden (with a compiler warning) only if that file ({andrew}/overhead/util/lib/config.c) includes any AFS .h files that override the SYS_NAME or OPSYSNAME definitions. As it happens, config.c never includes any such files. The malloc(2) call on line 144 of config.c (storing into ``envar'') represents a storage leak: the space allocated is never freed or reused. There should be a simple ``free(envar)'' after the call to getenv(envar). Craig