Path: utzoo!utgpu!water!watmath!clyde!rutgers!cmcl2!nrl-cmf!ames!amdcad!sun!pitstop!sundc!seismo!uunet!sdrc!crgabb
From: crgabb@sdrc.UUCP (Rob Gabbard)
Newsgroups: comp.sys.apollo
Subject: Alarm Server and Env variables
Keywords: apollo domain alarm_server env
Message-ID: <191@sdrc.UUCP>
Date: 18 Jan 88 15:14:24 GMT
Organization: Structural Dynamics Research Corp., Cincinnati
Lines: 21

On the DN330 in my office I run the alarm_server from `node_data/startup.19l
instead of when I log in so that I can get notified of problems even when I'm
not logged in, plus if there were any problems during the night, I can see them
in the morning first thing.

The problem I'm having is that it seems that any environment variables set in
`node_data/startup.19l after the cps line that starts the alarm_server are not
set ! For instance, I set UNIXLOGIN and NAMECHARS but they don't get set if
the alarm_server is started. A solution is to move the alarm_server startup
after the variable set, however it is an interesting bug (or feature?).

By the way, if you start the alarm_server upon node startup like I do, you
will get a message like "~user_data/alarm_server.mbx cannot open ....." because
it lookes for a user directory, namely ~. If you create a user_data directory
in /sys the mailbox file will get created there and you won't get the message.

Rob Gabbard                                    UUNET: uunet!sdrc!crgabb
Structural Dynamics Research Corporation

"Why should I worry what happens tommorow ? You know tommorow just might not
    come !" - Gary Rossington