"Andreas Schulze" <b79xan@gmx.de> wrote in message news:<coerje$a63$1@tgx093.str.allianz.de>...
> "christian" <ik_in_black@gmx.de> schrieb im Newsbeitrag
> news:7a5002bb.0411240146.5e1982af@posting.google.c om...
> > "Andreas Schulze" <b79xan@gmx.de> wrote in message
> news:<cnkqa1$lq6$1@tgx093.str.allianz.de>...
> > > > "Andreas Schulze" <b79xan@gmx.de> wrote in message
> news:<cnhr4k$s1l$1@tgx093.str.allianz.de>...
> > > > > "christian" <ik_in_black@gmx.de> schrieb im Newsbeitrag
> > > > > news:7a5002bb.0411170119.5a39c553@posting.google.c om...
> > > > > > hello
> > > > > >
> > > > > > i try to give a user the rigths to assign a pid to a wlm class
> ...
> > > > > >
> > > > > > in the class the assig rights are set to the user.
> > > > > >
> > > > > > but if i try as the user to assign the pid ... aix say permission
> > > denied
> > > ..?
> > > > > >
> > > > > > any ideas??
> > > > >
> > > > > Hallo Christian,
> > > > >
> > > > > wlmassign is restricted to the root user. Use sudo, that will work.
> > > > >
> > > > > HTH,
> > > > > Andreas
> > > "christian" <ik_in_black@gmx.de> schrieb im Newsbeitrag
> > > news:7a5002bb.0411190115.37718bc1@posting.google.c om...
> > > > but in the workloadmanager readbook (sg 245977) in chapter 5 "manuali
> > > > assignment" ...
> > > >
> > > > "In order to assign a process to a class or cancel a prior manual
> > > > assignment,
> > > > the user must have authority both on the process and on the target
> > > > class.
> > > > These constraints translate into the following:
> > > > . The root user can assign any process to any class.
> > > > . A user with administration privileges on the subclasses of a given
> > > > superclass (that is, the user or group name matches the attributes,
> > > > adminuser or admingroup, of the superclass) can manually reassign any
> > > > process from one of the subclasses of this superclass to another
> > > > subclass
> > > > of the superclass.
> > > > . An user can manually assign his/her own processes (same real or
> > > > effective user ID) to a superclass and/or a subclass for which he or
> > > > she
> > > > has manual assignment privileges (that is, the user or group name
> > > > matches the attributes, authuser, or authgroup of the superclass or
> > > > subclass)."
> > > >
> > > > is ther a bug in aix 5.2 ML2?? ...
> > > >
> > >
> > > Hallo Christian,
> > >
> > > If you are using wlm with AIX 5.1 or later you can delegate
> administration
> > > to users by defining them properly. I have figured out so far that you
> are
> > > not using AIX 4.3.3 but what exactly your problem ist can hardly be
> deduced
> > > from redbook quotes. Can you tell us what you actually configured (and
> in
> > > which file)? No doubt this would improve your chance of getting the
> > > information you need.
> > >
> > > Regards,
> > > Andreas
> > >
> > > I could write a lot of why you should not top post and why you better
> don't
> > > shout 'Bug'. You might find the following faq usefull:
> > > http://www.catb.org/~esr/faqs/smart-questions.html ;-)
> >
> > so ..
> >
> > i have configured some classes ... and i have a script to manualy
> > assign pid ( java processes) in these classes ..
> >
> > in the class definition you can enter a username or/and a group to
> > "administrate" the class or the superclass ...
> >
> > but if i try to use this feature ... it does not work!... the class
> > directorys in /etc/wlm/current are owned by the user .. but he can
> > not assign pid with the wlmassign command to the classes ...
>
> I am still not sure that I understand completely what your problem is. It
> may be twofold. First we need to distinguish between adminuser and authuser.
> Adminuser is used to grant the administration of a superclass to a user.
> However to assign a certain process to a certain (sub-)class the authuser is
> needed. So first the owner of your java processes should be authuser for the
> class(es) to which the processes should be assigned. Secondly the user needs
> to be allowed to work with the process either by being it's owner or
> belonging to it's group or some other means of rights management. So maybe
> your problem lies somewhere between unix authentication and wlm
> configuration.
>
> To give an example for a sample stanza of the classes file for an sample
> class named BURPS:
> BURPS:
> tier = 0
> inheritance = yes
> authuser = johndoe
> Now, if there is a java process owned by user johndoe like in
> # ps -fujohndoe |grep -i java
> johndoe 3522616 1 0 09:51:25 - 0:03
> /usr/java131/jre/bin/java -Xms32m [...]
> he could manually assign this process to the BURPS class by the following
> command
> $ wlmassign BURPS 3522616
> $
> As johndoe both owns process and has the rights to assign processes to class
> BURPS the process moves to that particular class.
> Let's now assume that johndoe tries to assign a process to BURPS he does not
> own:
> $ ps -ef |grep -i java
> susiwong 4758923 1 0 09:34:10 - 0:43
> /usr/java131/jre/bin/java -Xms64m [...]
> $ whoami
> $ johndoe
> $ wlmassign BURPS 4758923
> 1495-579 Permission denied
>
> HTH,
> Andreas
ah .. the authuser ( for administrating the wlm class) must be user of
the process to add oder remove the proces into the wlmclass ...
thatīs my prob ... the processes are owned by root .. and we could
not start it under a other user ..
thanx ..
christian ...