RuneAudio 0.5-beta for most Raspberry Pi models

[cmh714]

@janui, I dont use cifs/smb.....only the nfs

root@runeaudio(rw):~# cat /etc/fstab | grep -i -v 'cifs|nfs'
#
# /etc/fstab: static file system information
#
# <file system> <dir> <type> <options> <dump> <pass>
/dev/mmcblk0p1 /boot vfat defaults 0 0
var-tmp /var/tmp tmpfs nodev,nosuid,noatime,mode=1777,size=5M 0 0
logs /var/log tmpfs nodev,nosuid,noatime,mode=1777,size=5M 0 0
rune-logs /var/log/runeaudio tmpfs nodev,nosuid,noatime,mode=1777,size=5M 0 0
http-tmp /srv/http/tmp tmpfs nodev,nosuid,noatime,mode=1777,size=5M,uid=http,gid=http 0 0

[janui]

[cmh714]

[janui]

[cmh714]

very odd, I still am not see it....would love it to come up faster but I can live as is..s
root@runeaudio(rw):~# systemd-analyze blame
8.916s mpd.service
2.201s logrotate.service
1.523s dev-mmcblk0p2.device
1.281s netctl-auto@wlan0.service
578ms avahi-daemon.service
534ms winbindd.service
476ms systemd-timesyncd.service
463ms systemd-resolved.service
435ms php-fpm.service
415ms bootsplash.service
392ms boot.mount
371ms smbd.service
352ms systemd-udev-trigger.service
342ms nmbd.service
289ms nginx.service
238ms rpcbind.service
201ms tmp.mount
197ms sys-kernel-debug.mount
195ms systemd-udevd.service
189ms dev-mqueue.mount
179ms rpc-statd.service
176ms systemd-journald.service
158ms alsa-restore.service
135ms systemd-tmpfiles-setup-dev.service
111ms systemd-modules-load.service
109ms kmod-static-nodes.service
101ms systemd-tmpfiles-setup.service
99ms systemd-random-seed.service
78ms systemd-sysctl.service
74ms systemd-rfkill.service
67ms systemd-update-utmp.service
56ms systemd-tmpfiles-clean.service
53ms systemd-user-sessions.service
47ms systemd-remount-fs.service
39ms srv-http-tmp.mount
38ms var-log.mount
34ms sys-kernel-config.mount
33ms redis.service
25ms var-log-runeaudio.mount
19ms var-tmp.mount
17ms shairport-sync.service
root@runeaudio(rw):~# systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.

graphical.target @4.917s
└─multi-user.target @4.916s
└─nginx.service @4.626s +289ms
└─network.target @4.602s
└─netctl-auto@wlan0.service @3.320s +1.281s
└─basic.target @3.261s
└─sockets.target @3.261s
└─dbus.socket @3.260s
└─sysinit.target @3.245s
└─systemd-timesyncd.service @2.768s +476ms
└─systemd-tmpfiles-setup.service @2.648s +101ms
└─local-fs.target @2.643s
└─boot.mount @2.250s +392ms
└─dev-mmcblk0p1.device @2.238s

[R101]

Hi Janui,

Is there any news about 0.5 support for m3u8 streams? I am still using 0.4b to listen to these, but I assume that support for earlier versions of Rune will discontinue at some point.

If I disable ffmpeg in 0.4b, it behaves the same as 0.5 does. I don't know if that could be a clue to the problem.

[janui]

[Vhond]

Still sometimes the mounting problem after rebooting the RPI. Removing the mount and adding it again 'solves' the problem but that mustn't be the way...

[janui]

[Vhond]

What kind of diagnostics do you prefer?