Path: utzoo!attcan!uunet!samsung!zaphod.mps.ohio-state.edu!wuarchive!udel!udccvax1!sun.acs.udel.edu!stabosz
From: stabosz@sun.acs.udel.edu (Rae D. Stabosz)
Newsgroups: comp.dcom.lans
Subject: system login script problem
Message-ID: <9691@sun.acs.udel.edu>
Date: 2 Apr 90 14:04:09 GMT
Reply-To: stabosz@sun.acs.udel.edu (Rae D. Stabosz)
Organization: University of Delaware
Lines: 26

This is driving me nuts.  I am running Novell NetWare 256 ELS Level II
on a brand new LAN.  The documentation mentions a default system login
script which the system uses if the supervisor doesn't provide one.  

As supervisor I've written a system login script but it DOES NOT get
rid of the default one.  There
seems to be an integration of the two.  The most obvious example of this
is the fact that if I include in my script the line

write   "Good %GREETING_TIME, %LOGIN_NAME this is a test"  

I'll get a double greeting at login time, one with "this is a test"
appended.  The other one must be coming from the default script that
NetWare provides.

It's only a nuisance with the greeting messages, but it is causing havoc
with my mappings.  It will do my mappings first, then the default
mappings, which means that in order to get what I want I have to provide
map space for Novell's mappings.  A pain in the ass.  

It looks buggy to me.  I've written system login scripts for other
networks without such problems.  AM I overlooking something obvious?
-- 
Rae D. Stabosz
University of Delaware
stabosz@sun.acs.udel.edu