I understand the 'normal' security risks involved but they don't
apply in my case. As an example the last OS update to 10.4.8 took me
five and a half hours to go from computer to computer doing the
routine. I run 'Repair Permissions' prior to and directly after all
updates. This may be overkill, but I look at it as an insurance policy
against things going wrong.
I really didn't think you were running a huge risk, just wanted make
sure you knew there was a possibility of such risks. Running Repair
Permissions has never been overkill in my experience, seeing as you
never seem to know what update will need you to do it.
As for the log out and back in as another user... Seems strange that
there isn't a way to do this. I would think this would be an
administrators greatest tool. I still think it is possible to do
however. How about resetting the plist that exists somewhere that
specifies which account is used at startup. Simply altering the file
and restarting would do this. I was hoping to more or less not restart
the computer but just the user account (not switching, as this does
not log out of the current account. )
Typically there isn't a way to script a shell login on a bsd system,
because there hasn't, so far as I know, been any demand for it. There
may vary well be some Applescript item that could do this on OS X, but I
haven't the foggiest notion of what. What would logging out and back in
as a specific user gain you? Maybe there's a different approach I can
point you towards, assuming you don't find a different way in the meantime.
I still have some bumps to iron out, but I'm just about done with all
35 functions my little RB app is set to do.
Happy Holidays,
Craig
_______________________________________________
Ditto,
Fargo
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
