Mailinglist Archive: yast-devel (81 mails)

< Previous Next >
Re: [yast-devel] About catching exceptions
  • From: Klaus Kaempf <kkaempf@xxxxxxx>
  • Date: Thu, 22 Apr 2010 16:35:31 +0200
  • Message-id: <20100422143531.GC25600@xxxxxxxxxxxxx>
* Josef Reidinger <jreidinger@xxxxxxx> [Apr 22. 2010 16:26]:
Klaus Kaempf write:

So we still have a policykit problem hidden somewhere ?!

No, it is well known issue if you run webyast as other user then
yastws. I hardcoded yastws user if policyKit throw missing permission,
because only yastws run it in production.

Ah, this defeats the purpose of allowing developers to run WebYaST
locally ;-)

What about replacing hardcoded 'yastws' with Etc.getlogin ?

I check rest-service code of groups and I find different code when
DBus::Error occure so I report it.

I fixed GroupsController and ApplicationController meanwhile to catch
and report DBus::Error once.

But I cannot find why your problem is not at least logged.

Yeah, thats actually the core of bnc#598794

If it him global exception catch, then it must be logged. So something
between catch it and return response without logging content.

I'm currently trying to come up with a test case.

SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG N├╝rnberg)

To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >
Follow Ups