How To Debug Login Script and Mapping Issues Using the Novell Client for Linux Products
Novell Cool Solutions: Feature
By Joe Harmon
|
Digg This -
Slashdot This
Posted: 13 Oct 2005 |
Applies To:
- Novell Client 1.0 for Linux
- SUSE Linux Professional 9.3
- Novell Linux Desktop 9
Introduction
There are a couple of ways to debug the
login script itself. One is using a DEBUG command inside the login
script itself and the other is using a custom debug file. Debugging
mapping issues can only be done using a custom debug file.
Debugging Within the Login Script
- There are different levels of debugging that can be used with in a login script. The debug levels range from 0 - 9, with 0 turning the debug off and 9 being the most verbose. In most scenarios you would typically use a debug level of 6 and 0.
- There are two options available for debugging a login script. One is to debug the the script as a whole and two is to debug just a specific section of the script. Depending on the size of your login script and the verbosity level of your debug, you will probably be better off using the second option.
- To debug the whole login script, place the word DEBUG at the top
of the login script with a space and then the desired debug level.
DEBUG 6 - To debug a section of a login script that fails to execute
properly you can encircle the section of login script using the DEBUG
command. In other words you can turn the debug on right before the
command and then turn it off right after the command.
DEBUG 6
map g:=\\myserver.whereever.com\sys:\public
DEBUG 0 - The debug output will be displayed in the login script results screen.
Global Debugging of the Login Script and Map Process
If the issue is not with your login
script, then it may be a problem with the map command itself. There is
a way to debug the map command, but it is on a global basis. There is
also a way to debug the login script on a global basis. This may come
in handy if you have multiple login scripts (profile, container, user)
and you want to debug all of them at once. This may also come in handy
because the DEBUG command used above is not recognized as a valid
command in a windows environment. Therefore if you are going to be
debugging a user that logs into both a Linux and Windows then you
should probably debug outside the login script.
- To enable debugging outside the login script, you need to create a file on the local workstation. The file name must be nclscript.conf and it must reside in the /etc/opt/novell directory.
- To enable global debugging for the login script process you need to put the DEBUG_LEVEL= parameter in the nclscript.conf
file, along with the appropriate debug level. The debug levels are the
same as the procedure outlined for debugging within the login
script. The debug levels range from 0 - 9 with 0 turning the debug
off and 9
being the most verbose. In most scenarios you would typically use a
debug level of 6.
DEBUG_LEVEL=6 - To enable global debugging for the map process you need to put the MAP_DEBUG_LEVEL= parameter in the nclscript.conf file, along with the
appropriate debug level. The debug levels are the same as the procedure
outlined for debugging within the login script. The debug levels range from 0 - 9 with 0 turning the debug off and 9
being the most verbose. In most scenarios you would typically use a
debug level of 6.
MAP_DEBUG_LEVEL=6 - The debug output will be displayed in the login script results screen.
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com