stabosz@sun.acs.udel.edu (Rae D. Stabosz) (04/02/90)
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
crowed@guille.ECE.ORST.EDU (David Crowe Jr.) (04/14/90)
In article <9691@sun.acs.udel.edu> you write: >.... >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. The Novell login sequence goes through two login scripts - the SYSTEM login script as you have created and then goes on to the USER login script. As you have noticed with LOGIN performing your mappings and then it's default. The SYSTEM login script can be made to be the only script read at all by giving the "exit [command]" in the SYSTEM script when all mappings and setups are finished. Otherwise you will have to make a login script for each user; not particularly tough but, depending upon the sophistication of your clientele, it is more flexible and responsive to their tastes. I believe each user should have their own login script anyway, with at least: map display on map in it to prevent others from putting a script in someones MAIL directory. This is a security issue since group EVERYONE has write and create rights in SYS:MAIL\[userid] (where individual login scripts are kept under the coded userid subdirectory). > >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 The Netware default script isn't buggy, just brain dead. They, unfortunately, don't INSERT search drives, instead they overwrite the first two in the current path. There isn't currently a way to change the default script except to copy it to each users MAIL directory. You aren't (weren't) the only one to have trouble with this aspect of the Netware baptism. It isn't very clear in the documentation that this is what happens in the LOGIN procedure. If you continue to have trouble, send me a note. Cheers, David Crowe, Jr. Network Manager, College of Engr. Oregon State University email: crowed@ece.orst.edu voice: 503 737-4525 (9-5 PDT) 737-3019 other times