|
Post by peterfu on Jan 27, 2007 19:20:02 GMT 7
you're absolutely right, d**n, too stupid, in the module.rc start/stop script I unconditionally reset the sys password instead of only checking if the sys user is present and if not setting up the sys user with the default password. I'm almost finished with the fix..... Andreas P.S. Even without the IMGDUP module you can always access the module preferences page by writing the right URL yourself.... in your posting you were just telling this to gideon007.... Glad to help You to improve your modules. Yep, I know the manual possibility with the URL - just to lazy and its easier to do it in the shell. br Peter
|
|
|
Post by gideon007 on Jan 27, 2007 20:55:32 GMT 7
Thanks Peterfu, makes one rethink the idea of doing anything late at night... As others already reported I couldn't enable the IMGDUP module as well. It didn't give me an install error at least But it did do its work and created the INGDUP dir and I was able to edit the getform.html so I could access the module pages without manually editing the links every time. Edit: other problems: I can not chnage the password of sys, reboot, shutdown either on the sys module page nor on the shutdown module page: It does work when sshed with sys and the passwd command. And for reboot and shutdown the password seems to keep at least oh, btw, both reboot and shutdown work fine here. Edit: another question: On the main logon page of the Thecus you can logon with the users sys/reboot/shutdown as well, regardless of what you type in the password field.
|
|
|
Post by omega on Jan 27, 2007 22:03:38 GMT 7
Hi gideon007, As others already reported I couldn't enable the IMGDUP module as well. It didn't give me an install error at least But it did do its work and created the INGDUP dir and I was able to edit the getform.html so I could access the module pages without manually editing the links every time. Ok, found the bug why enabling the module was not possible! Indeed when enabling the module everything is done (you'll see the symbolic link /img -> /raid/data/module/IMGDUP/...) but only the return code of one script was wrong. Will create a new version soon.... Found the bug here too. There was abug in the avusertool.php PHP library file that prevented calling the usertool script at all. As you wrote: changing the passwords using passwd in the shell is always possible. You'll still have the problem that everytime when the SYSUSER module gets started, the sysuser password is reset to sys. In the upcoming bug-fix release this will be fixed. Happy to hear this. The shutdown module was really hard work because it may not run on /raid/data otherwise the shutdown procedure would stop because it cannot unmount /raid/data. Yes, that's not a bug that's a feature..... ;D No, Thecus decided that only users registered with SAMBA is allowed to login via CIFS, NFS, FTP and HTTP login. So all users you add locally to /etc/passwd are ignored by that facilities. Andreas
|
|
|
Post by gideon007 on Jan 27, 2007 23:13:37 GMT 7
Thanks for looking at that all and already finding the bugs! I see
|
|
|
Post by omega on Jan 29, 2007 23:27:08 GMT 7
Hi everybody, I've tried to fix all known bugs and created a new version 2.00.01 for five modules: INFO, IMGDUP, FIREFLY, SHUTDOWN and SYSUSER. As always they are available at the Unofficial Thecus Wiki..... Please report your findings! Enjoy it! Andreas
|
|
|
Post by gideon007 on Jan 30, 2007 5:18:13 GMT 7
many thanks as always, will try later when I'm more tired and prone to make another mistake (would you be able to make a module that makes the module page accessible without manual editing or manually changing the url, or is that something that might get fixed by Thecus in the "final"? It's not a big deal right now because I've already done it now and am easily able to edit the getform.html again)
|
|
|
Post by omega on Jan 30, 2007 6:44:31 GMT 7
would you be able to make a module that makes the module page accessible without manual editing or manually changing the url, or is that something that might get fixed by Thecus in the "final"? It's not a big deal right now because I've already done it now and am easily able to edit the getform.html again) 1) the getform.html will be fixed in the final release (Thecus indicated this somehow) 2) Why do you think you have to do the modification again? When you uninstall the IMGDUP module, all files which have changed until then are saved to persistent storage. When you install the new version of IMGDUP, these files are restored during installation. So your changed getform.html script should be there again. It took me some time to create this feature..... Andreas
|
|
|
Post by peterfu on Jan 31, 2007 5:43:46 GMT 7
omega: Hi andreas, the SYSUSER 2.00.01 is still resetting after booting - I assume this is caused by the module.rc which deletes the user if it is called with stop - actually I think that on stop it should be do nothing, cause during shutdown the module receives the stop and cause there is no process running no action should be done. If it reboots it checks then in the start branch if the user exists - of course not cause the user was deleted and so the user sys is again created with the default password. I have tested it with modifying the module.rc and the new password is still valid after booting. br Peter PS : You see, I start analyzing Your framework
|
|
|
Post by omega on Jan 31, 2007 16:15:47 GMT 7
@peter You're right Although this are only minor problems, I've found even some more corrections needed in order to preserve the sys password when enabling/disabling or even reinstalling the module. I've already done the fix but this time I really want to test it before I'll give it away... Andreas P.S. Happy that you almost became a module writer! Now check the wishlist and do one yourself
|
|
|
Post by gideon007 on Jan 31, 2007 16:34:55 GMT 7
ok, strange things happening here after the module upgrade. 1. module shutdown is not working. When I ssh with either reboot or shutdown I get to the normal root prompt. 2. I can no longer shutdown from the webinterface. It says it will shutdown but all it does is that it seems to shutdown the modules (I get the above discussed almost blank page "no name given" when clicking on the module names). 3. When I select restart on the webinterface I *think* it doesn*t really restart since the sys user password does not reset here But it restarts the modules since I can get to the module settings again when clicking on the module names. Installed are: sshd, firefly, info, Imgdup, sysuser and shutdown Edit: that I can't reboot/shutdown from the webinterface seems to have been caused by imgdup, uninstalling it helped with that. But the shutdown module still doesn't work, so that is most likely not caused by imgdup
|
|
|
Post by peterfu on Jan 31, 2007 21:33:43 GMT 7
Hi gideon007, I had similar effects with IMGDUP installing/deinstalling - the solution for me was after I had deinstalled imgdup, I have deinstalled all other modules and then installed them again - then everything works as expected - of course the small issue in the sysuser as described above was still there. br Peter
|
|
|
Post by omega on Jan 31, 2007 22:47:41 GMT 7
@gideon did I already mention the sysuser issue is fixed and working.... I checked again the shutdown issue: the problem is that I know why it fails sometimes and that I can reproduce it sometimes ... but only sometimes. The reason why it fails is very unclear though. The Thecus shutdown script kills all processes accessing /raid/data on shutdown so I created a shutdown daemon running from /tmp without even looking at /raid/data. But even then, sometimes the shutdown script from Thecus thinks that my script is still accessing /raid/data in some way and kills it effectively stopping the complete shutdown in the middle. I've done some modifications and I'm not able to reproduce the above scenario any more. I'll prepare the next version. Please give it a chance. peterfuI think your IMGDUP effects (what is it again) are not related. Please give the new version (when they are available) another try. I'm using the IMGDUP all the time without problems.
|
|
|
Post by peterfu on Feb 1, 2007 0:36:24 GMT 7
@gideon peterfuI think your IMGDUP effects (what is it again) are not related. Please give the new version (when they are available) another try. I'm using the IMGDUP all the time without problems. Of course I will try them - the modules you write and publish are a GREAT improvement of the N5200 - and as I started SW Development about 25 years ago, although I do almost nothing nowadays - I know how hard it is to do this - and this with no documentation of the N5200 br Peter
|
|
|
Post by omega on Feb 1, 2007 1:55:05 GMT 7
OK, here it is..... On the Thecus Wiki, the updated modules SYSUSER_2.00.02 and SHUTDOWN_2.00.02 are available. Hopefully they are now doing what I told them to do...... Keep me updated if they are working.... Andreas
|
|
|
Post by gideon007 on Feb 1, 2007 3:49:37 GMT 7
They are working for me. Curiosly, sys did keep the password I had set for it (it was shut down before I turned it on, uninstalled the previous version and then installed the new one). Shutdown lost its password between uninstalling .01 and installing .02.
I still have the problem that the device won't shut down from the webinterface if IMGDUP is installed and enabled.
|
|