Han Hartgers wrote:
> Hi Ducan and others,
>
> I have tried last night freevo svn 11342 with kaa svn 3862.
>
> The webserver is indeed started in the background with "freevo
> webserver --daemon". (SOLVED)
>
> One of the problems that still persists is that freevo itself is not
> passing the intro screen.
>
> I try to explain the situation a bit better:
>
> Begin situation: no freevo related process is running.
>
> When I start freevo, "freevo" on the shell prompt. the intro screen
> is displayed but stopped when the progress bar is full. I never get
> to the menu.
> (The main-1001.log file is generated change compared with last time I
> tried the svn.)
> I think that the problem is the way how the webserver is automatically
> started from the freevo process; this is what I see when I do "ps ax
> | grep freevo":
>
> 6731 pts/0 S+ 0:00 /usr/bin/python /usr/bin/freevo
> 6735 pts/0 Sl+ 0:04 python
> /usr/lib/python2.5/site-packages/freevo/main.py
> 6745 pts/0 S+ 0:00 sh -c /usr/bin/freevo webserver start
> 6746 pts/0 S+ 0:00 /usr/bin/python /usr/bin/freevo webserver start
> 6749 pts/0 S+ 0:00 python
> /usr/lib/python2.5/site-packages/freevo/helpers/webserver.py webserver
> start
>
> I believe that the word "start" should have been --daemon for process
> 6745 and/or 6746. The webserver is running and is responsive to
> requests.
> I do get the freevo main menu when I kill process 6746.
I think that this was my fault I hadn't noticed that the freevo script
was being used in unexpected places such as the www plug-in.
If you are using the www plugin (plugin.activate('www')) and starting
the webserver from the command line then remove the plug-in activation
from the local_conf.py. IMHO having the www plug-in causes more problems
than it solves; why do we need to start the plug-in when freevo starts
rather than when the machine starts?
> (I do not have this problem when I start the webserver in advance
> before I start freevo but freevo is complaining a bit on the prompt
> about that situation: "webserver still running, run 'webserver --stop'
> to stop" noting is shown in the log file.)
>
>
> I have one error message (coming from the weather plugin) but I do not
> care too much about that now.
> ERROR: global name 'NetworkException' is not defined
Which weather plug-in?
> But a more inportant item is that the system shutdown functionality
> is not really working.
> Freevo shutdown (the freevo process stops) but the computer not (the
> shutdown/halt command is never issued). This is both true for the menu
> option "shutdown system" as the automatic shutdown timer.
This should be fixed too, another place where the freevo script was
being used.
> I have this in my local_config.py
>
> SYS_SHUTDOWN_CMD = "/home/freevo/bin/sysshutdown.sh halt"
> SYS_RESTART_CMD = "/home/freevo/bin/sysshutdown.sh reboot"
>
> (sysshutdown.sh is a little wrapper script arround "sudo shutdown -h
> now" (or -r now))
> And that worked well with svn release 11227.
>
> Is the variable name changed or is it something more in the internals
> of freevo/kaa?
Duncan
------------------------------------------------------------------------------
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
_______________________________________________
Freevo-users mailing list
Freevo-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/freevo-users
