login script maps more drives than commands

[bodmin]

Hello

I am operating Novell 5.x on multiple workstation OS's and I am having troubles with the login script. The script that was being used was mapping more drives than I was requesting. To attempt to troubleshoot this I removed all login scripts, both the context and the profile login script and I was still left with a script that mapped two drives.

Can anyone shed any light on where these mappings are being called from??

Cheers

 

[LawnBoy]

You must be getting the script from further up the tree. You can inherit scripts all the way up until .root.

 

[Lou0686]

If you do not use a user defined script, the default script will be in play.

Lou

 

[marvhuffaker]

I just want to add some detail to what was already said..

Your Container and Profile scripts always run before the user script. Then the User script runs. If there is no user script (IE: It is blank), then the default script will run (Giving you your 2 extra letters).

So if you have a container script and no user script, the end result will be whatever is in your container script PLUS a mapping to SYS (usually F) and a search drive mapping to SYSUBLIC (Z.

The best way to remedy this is to put the following command in your container scripts.

NO_DEFAULT

You can put it anywhere any the script but I like to have it at the top. I put it in every container script in every tree I ever work on just so I don't have the default scripts running (Since I avoid user scripts at all cost)

Once you do this, you will only get the commands that actually exist in your container or profile scripts.


Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting

http://www.redjuju.com