We're back! (IN POG FORM)
Like you said, the problem is that "/usr/share/amule/amuled_home_wrapper.sh" is not there. Have you tried searching for it?Maybe "locate amuled_home_wrapper.sh" or "find / -name amuled_home_wrapper.sh" can help you. Unfortunately I don't know where this file comes from.
Like the init-script and the /etc/default file, the wrapper comes from officisal repo and isn't included in my packages. Would in the first post be mentioned that he uses my pkg's, this all would be clear. I think I bump the init-script up to the top of my todo-list. The wrapper is just there, because the one that wrote the init script wasn't able to read the help of amuled. start-stop-daemontdoesn't set the env correctly at the point amuled needs it, so this is why I implemented --config-dir switch
The init script and /etc/default don't get deleted on update because they are config files. The wrapper get's deleted. So you have to start the daemon manually.
Quote from: Vollstrecker on January 25, 2010, 11:22:00 AMThe init script and /etc/default don't get deleted on update because they are config files. The wrapper get's deleted. So you have to start the daemon manually.How ?
Quote from: Yionel on January 25, 2010, 01:41:14 PMQuote from: Vollstrecker on January 25, 2010, 11:22:00 AMThe init script and /etc/default don't get deleted on update because they are config files. The wrapper get's deleted. So you have to start the daemon manually.How ? This is a case for the amuled FAQ. I am sure you will find what you need in there.
