Hi,
I am struggling with the installation of RT (12 hours… :)) and it
almost works (ver. 1.0.4).
Apart from some problems I will solve myself when my brain restarts I
have some I will not be able to get through.
Problem 1: NIS authentication.
I saw in the ‘contrib’ dir ns_authentication but the patch there did not
went through properely (I am trying to apply it to
…/rt/lib/rt/ui/web/manipulate.pm). It fails at the 1st and 3rd hunk
and successes at the 2nd.
Has anyone had this problem?
Problem 2: What users see in the queue
Is it possible to have users see only THEIR requests and not the whole
queue? I managed to have them see either the whole queue or nothing.
Problem 3: Updating queue managers
I am probably still lost in the nomenclature of the names but I would
like tobe able to have RT send an email to the people involved in
solving problems when a new problem appears in any queue?
To put it clear: I have users A, B, C and D and I would like A and B to
get an email stating that there is something new in the queue (and only
to them).
Thanks in advance for any help!
Thank you also for copying me on a potential answer - I did not get any
confirmation after subscribing to the list. Thank you
Wojtek
Hi,
Hi,
I am struggling with the installation of RT (12 hours… :)) and it
almost works (ver. 1.0.4).
Apart from some problems I will solve myself when my brain restarts I
have some I will not be able to get through.
Problem 1: NIS authentication.
I saw in the ‘contrib’ dir ns_authentication but the patch there did not
went through properely (I am trying to apply it to
…/rt/lib/rt/ui/web/manipulate.pm). It fails at the 1st and 3rd hunk
and successes at the 2nd.
Has anyone had this problem?
Yes, more or less just hink 3 failed. This patch is definitely not for
rt 1.0.4 but for a much older version. hunk 3 must now be applied to
support.pm in the same directory. But it still doesn’t work properly, as
the patch uses the clear text password to compare with the NIS password
but the webinterface of rt now supplies just a hash of the password. AS
I’m far from being a perl god, I was not able to change this.
Problem 2: What users see in the queue
Is it possible to have users see only THEIR requests and not the whole
queue? I managed to have them see either the whole queue or nothing.
The ns-authentication patch does this for you, if it works 
and if the
rt-username is identical with his e-mail address.
Problem 3: Updating queue managers
I am probably still lost in the nomenclature of the names but I would
like tobe able to have RT send an email to the people involved in
solving problems when a new problem appears in any queue?
To put it clear: I have users A, B, C and D and I would like A and B to
get an email stating that there is something new in the queue (and only
to them).
Thanks in advance for any help!
Thank you also for copying me on a potential answer - I did not get any
confirmation after subscribing to the list. Thank you
Wojtek
rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users
Bye Rainer
Rainer Weigle - MPI fuer Meteorologie
weigle@dkrz.de
040 / 41173 - 373
Rainer Weigle wrote:
Yes, more or less just hink 3 failed. This patch is definitely not for
rt 1.0.4 but for a much older version. hunk 3 must now be applied to
support.pm in the same directory. But it still doesn’t work properly, as
the patch uses the clear text password to compare with the NIS password
but the webinterface of rt now supplies just a hash of the password. AS
I’m far from being a perl god, I was not able to change this.
Problem 2: What users see in the queue
Is it possible to have users see only THEIR requests and not the whole
queue? I managed to have them see either the whole queue or nothing.
The ns-authentication patch does this for you, if it works and if the
rt-username is identical with his e-mail address.
Thanks for your email - looks just too good to be true
Has anyone maybe gone through this?
THANKS!
Wojtek
PS. and the usual plea for a cc: to my email address