I'm having trouble with running uzbl browser under matchbox-window-manager on a raspberry pi. I'm using it with a 22' lcd screen to display some info (temperatures, graphs, VPS server stats...).
What I actually did is: Set up the raspberry pi to start X at startup (raspi-config). Created /home/pi/.xsession with the following contents:
kiosk-browser &
exec matchbox-window-manager -use_cursor no -use_titlebar no
kiosk-browser contents:
#! /bin/bash
while true
do
if [ $(pidof -x uzbl-core | wc -l | tr -s "\n") -eq 0 ]
then
uzbl -u http://localhost/ -n kiosk &
fi
memFree=$(grep MemFree /proc/meminfo | awk '{print $2}')
if [ $memFree -lt 30000 ]
then
echo 'reload_ign_cache' > /tmp/uzbl_fifo_kiosk
fi
sleep 20
done
So you now see what I'm trying to achieve. I'm updating some divs contents and images using jQuery, and didn't find a better way not to freeze the pi after consuming all available RAM, as each browser I tested does this (after some significant ammount of time).
The problem I'm having with this setup is it sometimes doesn't reload the browser properly, but freezes instead. Sometimes with a black screen (as when the pi starts), sometimes it's white screen (uzbl loading html), and sometimes even sooner, before dismissing the old html contents.
So basically what I'm trying to ask is, is this setup ok? Is this how it's done, or am I missing something? :)
THANK YOU!
uzbl_is_running() { ... pidof ...; }, making the purpose of each section easier to guess. – Mar 16 '13 at 11:43execunless there's a reason for that. Note that you don't have to run a window-manager; if all you want is the browser, just leave it at that. – goldilocks Mar 16 '13 at 15:09exec), but it would if you moved that line, etc.execreplaces the shell with the command, as opposed to executing it within the shell, meaning the script will be defunct at that point. – goldilocks Mar 16 '13 at 16:03