Joe_999
Visitor
|
Re: Synology Linux: “shell_exec()” and “exec() pro - 2008/08/04 14:19
Hi Klaas,
thanks for opening this thread, what really addresses my problems as well.
First, you are right, I used the wrong directory for wget, it´s indeed in /usr/syno/bin. Now, I corrected it, but for me it seems that the wget function and background search of media is still not working. In the support.log I never see any media found but just:
[2008.08.04 19:44:33] Page Requested : http://192.168.0.101:8080/config/index.php by client (192.168.0.111)
[2008.08.04 19:44:34] Executing (via wget) URL in the background: media_search.php
[2008.08.04 19:44:35] ------------------------------------------------------------------------------
[2008.08.04 19:44:35] Page Requested : http://192.168.0.101:8080/config/index.php?section=MEDIA&action=PROGRESS&type=MEDIA by client (192.168.0.111)
[2008.08.04 19:44:48] ------------------------------------------------------------------------------
[2008.08.04 19:44:48] Page Requested : http://192.168.0.101:8080/config/index.php?section=MEDIA&action=PROGRESS&type=MEDIA by client (192.168.0.111)
[2008.08.04 19:45:01] ------------------------------------------------------------------------------
[2008.08.04 19:45:01] Page Requested : http://192.168.0.101:8080/config/index.php?section=MEDIA&action=PROGRESS&type=MEDIA by client (192.168.0.111)
[2008.08.04 19:45:14] ------------------------------------------------------------------------------
[2008.08.04 19:45:14] Page Requested : http://192.168.0.101:8080/config/index.php?section=MEDIA&action=PROGRESS&type=MEDIA by client (192.168.0.111)
[2008.08.04 19:45:27] ------------------------------------------------------------------------------
[2008.08.04 19:45:27] Page Requested : http://192.168.0.101:8080/config/index.php?section=MEDIA&action=PROGRESS&type=MEDIA by client (192.168.0.111)
[2008.08.04 19:45:40] ------------------------------------------------------------------------------
[2008.08.04 19:45:40] Page Requested : http://192.168.0.101:8080/config/index.php?section=MEDIA&action=PROGRESS&type=MEDIA by client (192.168.0.111)
[2008.08.04 19:45:52] ------------------------------------------------------------------------------
[2008.08.04 19:45:52] Page Requested : http://192.168.0.101:8080/config/index.php?section=MEDIA&action=PROGRESS&type=MEDIA by client (192.168.0.111)
[2008.08.04 19:46:06] ------------------------------------------------------------------------------
[2008.08.04 19:46:06] Page Requested : http://192.168.0.101:8080/config/index.php?section=MEDIA&action=PROGRESS&type=MEDIA by client (192.168.0.111)
and many more times to come ...
Of course, I don´t know whether the background media refresh with wget writes into support.log. Anybody can comment here, pls.?
Additionally, there is no progress shown on the media refresh page. The percentages fields remain empty or remain at the previous values.
With telnet the "top" commandy does not report any wget process running, I guess that´s not correct neither?
The world looks different with the http://IP-address/media_search, therefore I am in general using this to refresh my media DB:
Immediately scanned files and found files are written into the support.log (with the shellexec() in file.php) and everything seems to run sequentially.
With the exec() instead, multiple media searches run simultaneosly, that means you see photo files detected between music files in the support.log, and the media DB refresh takes in general many hours, e.g. 10 hours (300 GByte of media, 70% of which are movies). It´s easy to detect in the many support.log.old files which are overwritten during that 10 hours interval that several media files have been found many times. Therefore I conclude, that the media_refresh is started more than once. (I have to admit that due to the use of German characters in some of my media file names I don´t know, whether I have a special issue here!).
I also think that the scheduled media refresh (in my case at 3.15 AM) does not work neither, since at least the support.log doesn´t show any actions at that time.
I think we LINUX (or Synology) users have to try to exchange information on what happens (and what doesn´t) if we use the media refresh button on the config pages in order to get closer to the root cause of our problem.
Regards
Joe
|
Forums 
