Hello Boud, I checked every permissions which are set by the package wims at post-install, from revision 3.62-9, they should match with the requirements you list there.
I shall try to have this new revision uploaded soon. Boud Roukema a écrit : > On Mon, 22 Oct 2007, Georges Khaznadar wrote: > >> Boud Roukema a écrit : >>> ANALYSIS: >>>> From the command line: >>> >>> as user wims: >>> cd /var/lib/wims/public_html/ && ./wims >>> outputs a correct html page. >>> >>> as user www-data, same command: >>> >>> cd /var/lib/wims/public_html/ && ./wims >>> outputs: >>> >>>> Status: 500 WIMS Internal Error >> >> The command ./wims, in this context, should be executed with the >> identity of the user wims, since the post-installation package is >> supposed to set the permission bit as stated below: > > salut Georges and the bug-tracker, > > i found some more chmod commands sufficient to make wims work > sufficiently correctly for me to copy/paste old classes, do some > appropriate mkdir/chown/chmod/cp operations on them and satisfy students' > needs. :) > > However, i suspect that the setup of user/group/suid and so on that i > have is not the one intended. Regarding the wims web-based management > functions, i'll reply independently to bug 447896 in order to not mess > up the bug tracking structure. > > > Here are the commands i found sufficient (in addition to my previous > comments): > > > chmod g+rx public_html/scripts/adm/ > > chmod g+rx bin chmod g+rx public_html/bin public_html/msg/ > chmod g+rx public_html/bases/d[io]c public_html/bases/sheet/ > public_html/bases/site/ public_html/bases/sys/ > > chmod g-x log/classes/.[hiw]* > > chmod g+w tmp/forall/ tmp/sessions/ > > # This was needed since otherwise the exercises have key information in.... > italian! > chmod g+rx public_html/modules/adm/sheet.??/ > chmod g+rx public_html/modules/adm/* > > > The group in each case is wims, which includes both wims and www-data. > > i hope this helps. i guess for testing (sorry, i'm unlikely to have much > time on any short time scale, but at least i'd like my feedback here to be > available), the best solution would be to create a chroot jail and install > etch from scratch there, then test the installation from aptitude. i'm not > a debian developer, so i'm only guessing here what would be best. > > > As to whether or not the bug is closed, it's hard to say. For me > personally, > the above and my previous list of chmod/chown commands are a hack, which is > not enough to close the bug. Maybe the bug severity could just be > downgraded. > > > In a moment i'll reply to the other bug report. > > bon courage > boud -- Georges KHAZNADAR et Jocelyne FOURNIER 22 rue des mouettes, 59240 Dunkerque France. Téléphone +33 (0)3 28 29 17 70
signature.asc
Description: Digital signature
