Opened 3 years ago

Last modified 19 months ago

#18364 new defect

r43238 / empty output of 'ubus call log read'

Reported by: bittorf@… Owned by: developers
Priority: normal Milestone:
Component: packages Version: Trunk
Keywords: Cc:


at least with r38993 it was possible to get JSON with

ubus call log read


ubus call log read "{\"lines\":"1"}"

now the output is always empty but the command
returns success / exit-status 0

when asking for the methods, it seems to be the correct way:

root@box:~ ubus -v list log
'log' @d4f9c2d0

Attachments (0)

Change History (3)

comment:1 Changed 2 years ago by rmilecki

This is caused by a change of used API in ubox project:;a=commitdiff;h=12728c38621c6271dd2102d3e11cf95ff42eeff8

I'm not sure how to (or if we should) handle it. Maybe some option would be to extend ubus command to know/use FD API as well?

John, any ideas?

Last edited 2 years ago by rmilecki (previous) (diff)

comment:2 Changed 2 years ago by rmilecki

We can extend ubus command to support streams and then you could use e.g.

ubus stream log read { lines:1 }

Not sure if we can add some auto-detection of API to ubus.

Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.