Hello, On Wed, Mar 16, 2005 at 08:15:48AM +0100, [EMAIL PROTECTED] wrote: > >Hello, > > > >On Tue, Mar 15, 2005 at 08:11:00PM -0500, elias humbolt wrote: > >> Package: mldonkey-server > >> Version: 2.5.28-2 > >> Severity: grave > >> Justification: renders package unusable > >> > >> > >> > >> -- System Information: > >> Debian Release: 3.1 > >> APT prefers testing > >> APT policy: (990, 'testing'), (600, 'unstable') > >> Architecture: i386 (i686) > >> Kernel: Linux 2.6.10-1-686 > >> Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1) > >> > >> Versions of packages mldonkey-server depends on: > >> ii adduser 3.63 Add and remove users and > >> groups > >> ii debconf [debconf-2.0] 1.4.30.11 Debian configuration > >> management sy > >> ii libc6 2.3.2.ds1-20 GNU C Library: Shared > >> libraries an > >> ii mime-support 3.28-1 MIME files 'mime.types' & > >> 'mailcap > >> ii ucf 1.14 Update Configuration File: > >> preserv > >> ii zlib1g 1:1.2.2-3 compression library - runtime > >> > >> -- debconf information: > >> Several people in other bug reports have mentioned that > >> /etc/init.d/mldonkey-server start does actually fail to start the > >> server. > >> > >> Part of the problem might be that /var/lib/mldonkey is not actually > >> generated on install, eventhough this dir is selected via dpkg. > >> > >> However, what sure is the case is the fact that /var/run/mldonkey is > >> owned by root on install and the mldonkey-server init script simply is > >> not able to write to it for some reason. I guess that might be because > >> of chroot or running mldonkey by the mldonkey user. > >> > >> However, it is absolutely certain, that it starts after I set the > >> ownership of the /var/run/mldonkey DIR to mldonkey user! Setting the > >> group instead of the user to mldonkey might help as well. > >> > >> The other problems I still have are described in other bug reports, like > >> the one that whatever I enter in debconf never makes it to the > >> /etc/defaults/mldonkey-server file. > >> > >> I am not sure if /var/lib/mldonkey + files is actually created on first > >> startup when set in defaults accordingly since I first thought it > >> mldonkey does not start up for the reason of the dir + files not being > >> there and therefore copied a working set over from another machine. I > >> never removed it afterwards since I was so happy that it finally worked > >> and fed up with dealing with it. > >> > >> I hope this bug report makes mldonkey-server usable again out of the > >> box. (At least as soon as the startup value users set via debconf on > >> install really makes it into the defaults file). > >> > > > >We already talk about this issue, as far as i remember ( but it was not > >on a bug report ). > > > >I don't remenber if you answer my question : with which user do you > >launch the init script ? > > > >Concerning your options, i see that you have set up launch_at_startup to > >false ( see your debconf information ). It could explain why your script > >doesn't start. > > > >Regard > >Sylvain Le Gall > > > > > The debconf information is not what is actually in > /etc/defaults/mldonkey-server! Since debconf does not do what anybody would > expect it to do, I had to edit everything by hand anyway. > > I start init as root, just like it would be started on init either. mldonkey > however ist running as mldonkey users, as far as I remember. I found that > behavior strange as well, but it is like that! If all config is right, the > dir rights on /var/run/mldonkey still prevent the service from start!! I have > investigated that very carefully. However, I did not investigate any code, > since I was satisfied when it was finally running. > > It is not that strange actually. How could an mldonkey user write into a dir, > that he has no rights for, well that does not even belong to its group. By > the way, as it seems, mldonkey does not seem to run as mldonkey group either, > since all files saved belong to group users!!! >
Just a question for my personnal information : is there already a mldonkey user ? ( because it could explain that mldonkey is running as mldonkey:user ). If so, i think the error in the debconf comes from the fact that no mldonkey user can be created ( in fact, we cannot create a mldonkey user with primary group mldonkey ). This could stop the debconf process. Regard Sylvain Le Gall ps : could you send me the output of "getent passwd mldonkey" command. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
