Novell Home

Best Login Practices - Part 4

Novell Cool Solutions: Tip
By Paul Gear

Digg This - Slashdot This

Posted: 15 Feb 2006
 

Problem

We had a lot of problems in older client versions with workstations holding the login script open, locking it from changes. (I'm not sure whether newer clients have the same problem.)

Solution

We got around this by keeping our top-level O's login script very simple:

;Login Script For O - Must be Included by all user containers

write "Login script modified: Name YYYY-MM-DD HH:MM"
no_default

if member of ".ProfileDevel.O" then
   rem profile .2005-017.LoginScript.O
   profile .2006-001.LoginScript.O
   write "*** ProfileDevel.O ***"
else
   if member of ".ProfileTest.O" then
       rem profile .2005-017.LoginScript.O
       profile .2006-001.LoginScript.O
       write "*** ProfileTest.O ***"
   else
       rem profile .2005-015.LoginScript.O
       profile .2005-016.LoginScript.O
   end
end

Then the serious work work is done in the profiles inside LoginScript.O. We never modify an existing login script object. We just copy it to a new one with the next higher version number, and edit that one before activating it.

This gets us around the locking issue. It also enables us to control the version of development, test, and production users separately.


Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com

© 2014 Novell