Hi,
For murphy, if you are interested in the runtime logs associated with some
event you're about to trigger, you can also
pull in the murphy-tests package and use murphy-console to change dynamically
the runtime logging target, for instance to the console you are using:
So zypper install murphy-tests && murphy-console and then eg.
murphy> log target
available log targets:
stdout
stderr (active)
syslog
file
systemd
console/2
murphy> log target console/2
[log] I: changed log target to console/2
changed log target to console/2
...
[log] I: resource-native: client2 connected
[log] I: resource-native: received a message
[log] I: resource-set flags:0 priority:0 class:'player' zone:'driver'
[log] I: resource: name:'audio_playback' mandatory shared
[log] I: attribute role:'music'
[log] W: Can't find resource definition 'audio_playback'. No resource created
[log] E: Can't add resource 'audio_playback' name to resource set 1
[log] I: resource-native: peer closed connection
...
murphy> exit
Exiting from the console will/should redirect logging back to stderr (hence to
journald).
That said, I don't think you will find out from the murphy console/logs any
errors related to access-control restrictions caused by SMACK labels/rules.
Murphy itself is currently not configured to use SMACK for access control so I
think you are more probably rejected from accessing something by SMACK itself,
or the WRT. If that's the case, you can disable SMACK altogether for debugging
by adding security=none the kernel command line as Mikko instructed.
Cheers,
Krisztian
---------------------------------------------------------------------
Intel Finland Oy
Registered Address: PL 281, 00181 Helsinki
Business Identity Code: 0357606 - 4
Domiciled in Helsinki
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
_______________________________________________
IVI mailing list
[email protected]
https://lists.tizen.org/listinfo/ivi
