On Nov 15, 2016, at 12:09 AM, J. Cameron Cooper <jccoo...@gmail.com> wrote:
>
> after reinstalling [crtmpserver] today I don't see the issue anymore.
It could have been a firewall issue, then, with the package’s post-install
script restoring the proper port 8080 firewall rule, which also allows Fossil
through as a side-benefit.
I’d suggest that if you’re going to use “fossil server” on a permanent basis
that you select a much less troublesome port number and use the -P option to
force it.
Here’s my wrapper script for starting Fossil as a server, which deals with that
and several other common issues:
#!/bin/sh
OLDPID=`pgrep fossil`
if [ -n "$OLDPID" ]
then
echo "Killing old Fossil instance (PID $OLDPID) first..."
kill $OLDPID
typeset -i i=1
while kill -0 $OLDPID > /dev/null 2>&1 && [ $i -lt 30 ]
do
if [ $i -eq 1 ]
then
echo -n "Waiting for it to die..."
else
echo -n .
fi
sleep '0.1s'
i=i+1
done
echo
fi
fossil server -P 3691 --repolist /museum > /dev/null &
echo Fossil server running, PID $!.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
