Stefan de Konink wrote: > Alvaro Lopez Ortega schreef: >> Miguel Angel Ajo Pelayo wrote: >> >>> About the "cannot bind error": It seems like if you closed >>> (CTRL+C/Kill?) the cherokee-admin and python is >>> running already in the background with the cherokee-admin interface, >>> please do a ps aux |grep python to check it. >> Well, that seems to be the main issue. >> >> I would not run cherokee-admin on a embedded device, actually.. and if I >> did, I would launch it "on-demand": you launch cherokee-admin, then you >> do the configuration changes you wish, and finally you kill it. >> >> The cherokee-admin application logic is implemented in Python, so it >> takes a little bit of memory to run it. It was not designed to be run by >> default on embedded. > > What is advised in such situation? I read about the Remote Adminstration > handler, would it be possible to create a system that a 'local' > Cherokee-admin can connect to a remote server?
That would be an interesting nice-to-have, although implementing something similar is currently out of the radar. I would personally use cherokee-admin on my PC to configure the Cherokee server that I want the embedded to run. For instance: $ cherokee-admin -d ~/cherokee-embedded.conf $ firefox http://localhost:9090/ $ scp ~/cherokee-embedded.conf embedded:/etc/cherokee/cherokee.conf $ ssh embedded "killall -HUP cherokee-guardian" In that way you have all the advantages of Cherokee-admin while to save resources in the embedded device. -- Greetings, alo http://www.alobbs.com/ _______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
