Mailinglist Archive: yast-devel (163 mails)

< Previous Next >
Re: [yast-devel] custom log merged
  • From: Martin Vidner <mvidner@xxxxxxx>
  • Date: Thu, 24 Sep 2009 01:36:41 +0200
  • Message-id: <20090923233641.GA4909@xxxxxxxxxxxxxxxxxx>
On Mon, Sep 21, 2009 at 11:03:45AM +0200, Duncan Mac-Vicar Prett wrote:

I have just merged the log monitor into master.

I have tried it, with
# cat /etc/YaST2/vendor/logs.yml (*)
nm:
path: /var/log/NetworkManager
description: Network Manager

The log should be visible in the status plugin:
http://localhost:80/status [RPM]
http://localhost:3000/status [GIT]
http://localhost:56714/status [TODO]

but for me it nicely demonstrates the mentioned bnc#540623, via
Processing LogsController#show to txt (for 127.0.0.1 at 2009-09-24 01:24:01)
[GET]
Parameters: {"format"=>"txt", "lines"=>"5", "action"=>"show", "id"=>"nm",
"controller"=>"logs"}

DBus::Error (org.freedesktop.PolicyKit.Error.NotAuthorized:
org.opensuse.yast.scr.execute.target.bash-outputlang-en.utf-8-usr-lib-yast2-bin-tty-wrapper-tail--n-5-var-log-networkmanager-dev-null
no)
(ARGH!)

The documentation will go here:
http://en.opensuse.org/YaST/Web/VendorCustomization

However the config file format is still on RFC:
http://lists.opensuse.org/yast-devel/2009-09/msg00056.html

(*) Funnily enough, even though the logs have a separate config file
according to the latter proposal in the mail, vendor_setting_test.rb
still tests them in the catch-all vendor.yml Please make the
docs/examples/tests consistent, I suggest the more verbose variant
which is currently implemented.


Known bugs:
- If the service goes down, the ajax update shows infinite errors (
https://bugzilla.novell.com/show_bug.cgi?id=540623 )
--
Martin Vidner, YaST developer
http://en.opensuse.org/User:Mvidner

Kuracke oddeleni v restauraci je jako fekalni oddeleni v bazenu
--
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: yast-devel+help@xxxxxxxxxxxx

< Previous Next >