Anton,
I tried your suggestion but ran into the following:
DING! rsunsu-is-sr01: / {14} # /etc/init.d/utstorage stop
11:01 rsunsu-is-sr01: / {15} # /etc/init.d/utsvc stop
11:01 rsunsu-is-sr01: / {16} # /opt/SUNWkio/bin/kioskuseradm delete
Cannot delete kiosk user configuration: there are active sessions.
"utwho -ca" shows nothing. There are no active sessions, as far as I can tell.
Perhaps it can't delete the accounts because certain daemons are still running?
This server is part of a 2-server FOG; the other is accepting connections while
I work on this one. Could it be that the database holds session info that is
common to all members of the FOG? Would all members of the FOG have to be down
for the "delete" command to work?
TIA
Scott
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Anton Floor
Sent: Monday, August 16, 2010 12:57 AM
To: 'SunRay-Users mailing list'
Subject: EXTERNAL:Re: [SunRay-Users] kioskuseradm extend: caveat
It might be simpler to use modify BUT,
actually modify is delete+create and if some error occurs when modify is
deleting users you will receive bunch of errors and it fails.
So use delete and then create. I've done this dozen times.
Cheers,
Anton
> -----Original Message-----
> From: [email protected] [mailto:sunray-users-
> [email protected]] On Behalf Of Jörg Barfurth
> Sent: 16. elokuuta 2010 10:50
> To: SunRay-Users mailing list
> Subject: Re: [SunRay-Users] kioskuseradm extend: caveat
>
> Anton Floor schrieb:
> > Hi Scott,
> >
> > use this:
> > -----------------------------------
> > # /etc/init.d/utstorage stop
> >
> > # /etc/init.d/utsvc stop
> >
> > # /opt/SUNWkio/bin/kioskuseradm delete
> >
> > # /opt/SUNWkio/bin/kioskuseradm create -l utku -g utkiosk -i 88002 \
> > -u 200000 -c 25
> >
>
> Instead of delete+create, it is simpler to use
>
> # /opt/SUNWkio/bin/kioskuseradm modify -u 200000 -c 25
>
>
> It should even work to replace your entire procedure with
>
> # /opt/SUNWkio/bin/kioskuseradm modify -f -u 200000 -c 25
>
> (The -f will terminate running kiosk sessions.)
>
> If kiosk sessions don't come back properly after this, you can still
> perform a cold restart (utrestart -c).
>
>
> > This is documented in vdi wiki
>
> I'll see, if I can get this simplified.
>
> > and I have also reported this issue to VDI dev team.
> > Problem is that install script creates vdadbadmin user after
> kioskusers....
> >
>
> I hope we can get this fixed soon.
>
> - Jörg
>
> --
> Jörg Barfurth http://blogs.sun.com/joergb
>
> Disclaimer: I am employed by Oracle. The statements and opinions
> expressed here are my own and do not necessarily represent those
> of Oracle Corporation.
> _______________________________________________
> SunRay-Users mailing list
> [email protected]
> http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
_______________________________________________
SunRay-Users mailing list
[email protected]
http://www.filibeto.org/mailman/listinfo/sunray-users
