I read some of the posts on SSL and so I put secure = True into /etc/tinyerp-server.conf and then restarted the server but on my Fedora test box I'm having a problem with the init scripts:
> added secure = True to config file then... > [EMAIL PROTECTED] tinyerp-server]# service tinyerp-server start > Starting tinyerp-server: [ OK ] > > # ps aux | grep tiny > tinyerp 21977 11.5 3.3 47340 17328 ? Ssl 10:12 0:01 > /usr/bin/python ./tinyerp-server.py > --pidfile=/var/spool/tinyerp/tinyerp-server.pid > --logfile=/var/log/tinyerp/tinyerp-server.log -c /etc/tinyerp-server.conf > root 21982 0.0 0.1 4008 696 pts/1 R+ 10:12 0:00 grep tiny > > # service tinyerp-server stop > Stopping tinyerp-server: Traceback (most recent call last): > File "./tinyerp-server.py", line 271, in <module> > time.sleep(1) > File "./tinyerp-server.py", line 247, in handler > httpd.stop() > File "/usr/lib/python2.5/site-packages/tinyerp-server/netsvc.py", line 262, > in stop > self.server.socket.sock_shutdown(socket.SHUT_RDWR) > AttributeError: '_socketobject' object has no attribute 'sock_shutdown' > [ OK ] > # Once I start the server in secure mode then no longer can it be controlled by the 'service' (init) scripts. I looked at the init script and it seems there are no targets for 'startssl' or 'stopssl' like there are for instance, for apache startup. I think this script could use an enhancement in order to be able to use it with SSL. Gerry _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
