PiBox » launcher

Once remote logging is enabled by .opkg package, use piboxLoggerSetFlags(LOG_F_SYSLOG) to route logs to remote log host.

This can be used in launcher and any other app that uses libpibox:log. It should be added as an command line option.

There are only 4 PiBox/Ironman apps running that might cause this:

• piboxd
• imrest
• appmgr
• launcher

imrest seems the most likely candidate, but all of them should probably tested for leaks.

I need libleak added as a package (RM #1215), but that can't happen until I finish updating Buildroot to utilize some new features (RM #1217).

Note: UI lockup occurred two days ago as shown by date/time field. Verified ssh does not work either.
Remote logging would need to be enabled manually. There is no opkg for this.

• piboxd: off
• imrest: off
• appmgr: on
• launcher: on

Retesting with appmgr and launcher logging on. Will revisit daily to check on size of logs.

Note:

Logs after boot:

$ ls -l /tmp/
-rw-r--r--    1 root     root           965 Dec 31  1969 appmgr.log
-rw-r--r--    1 nobody   nobody       23065 Nov  3 17:53 launcher.log

Logs after a few minutes:

)$ ls -l /tmp/
-rw-r--r--    1 root     root           965 Dec 31  1969 appmgr.log
-rw-r--r--    1 nobody   nobody       60271 Nov  3 17:55 launcher.log

So launcher could definitely be filling up tmp space.