Closed Vacilando closed 14 years ago
Well, I have a solution now.
There is a known bug in fileconveyor; see http://github.com/wimleers/fileconveyor/issues#issue/16 Because of this, databases and probably other files were written to whatever the current directory was, but not in fileconveyor's directory.
Solved by changing directory to fileconveyor before launching it.
So I put these 2 lines to /etc/rc.local:
cd /mnt/data-store/fileconveyor/code /usr/bin/python /mnt/data-store/fileconveyor/code/arbitrator.py
Probably not the most elegant solution, but it works!
Your crude solution should work indeed. But I simply need to fix it. Sorry for taking so long. If you'd post patches, I'd commit them right away (hint hint ;) :P)!
I am trying to figure out how to run the daemon at (re)boot of (Ubuntu) Linux.
I put this line to /etc/rc.local:
/usr/bin/python /mnt/data-store/fileconveyor/code/arbitrator.py
After reboot, I can see the python script running, but /admin/reports/status claims "The daemon is currently not running."
When I start the daemon via terminal (python /mnt/data-store/fileconveyor/code/arbitrator.py) then it works OK.
Could you please advise the best way of running fileconveyor at (Ubuntu) Linux boot?
Thanks.