![]() ![]() When pressing Apply it starts the TwonkeyMediaServer. In the official media page, you have to click the Apply button if the media page only shows ‘Restart Server’. ![]() It is not the TwonkeyMediaServer itself that triggers entries in crontab, but it is somehow related. In my previous answer I told you that the TwonkyMediaServer didn’t need to be running. Now click the SET CRONTAB button and after a few seconds you should end up at the administrator media page with the autoscan checkbox selected. Change the “HOUR” string to the current hour and change the “MINUTE” string to the next minute plus 2 minutes or so (leaving existing spaces intact), assuming the time on your NAS is correctly set (if not, make it correct by using the admin panel). Open the HTML file with your favorite browser and fill the current hour in the hour input field and fill the minute input field with the value below.Copy utelnetd to \\YOURDEVICE\openshare\utelnetd.Change the YOURDEVICE in the HTML-file to use the right IP-address or hostname of the NAS.Save the content below to a HTML page, as it allows you to send commands that allow you to abuse cron for executing the tasks you want:.If you do anything wrong, it can break your device. You should only proceed when you understand what you are doing. Luckily you don’t have to, at least not when your device is running firmware 1.1.8, as I found out thanks to a post from user ‘hardel09′ (read here). However I didn’t want to physically open the device and void the warrant. I decided I didn’t want to submit the device for RMA again and wanted to get root access to the device and repair it (read: make it more stable) myself. I expect this might be caused by the autoscan feature that indexes the media on the device, or maybe the device just doesn’t have enough memory to cope with the continuous transfer of big files. The system log showed a kernel that was randomly killing processes. Therefore I sent the device for RMA to Lacie’s service desk where it was repaired.Īt least I thought it was, because after copying those large files again, the device broke again, but this time I was luckily still able to reboot and keep the device up a little while before it required a new reboot. ![]() This broke my device in such a way that it would become unusable (no admin panel, though still pingable). My problem with the NAS is that the kernel running on the device starts killing processes when I copy very large (2 GB ) files to the NAS via file -and print-sharing (using the samba server). The NAS has an ARM926EJ-S processor, a 1TB hard disk, 16MB of memory, an USB port and no fan (which makes it pretty quiet). Very handy, if it works as you expect it to. This device, also called Network Attached Storage (NAS), enables you to hook it onto your (local) network and access files via file -and print sharing, ftp and other protocols. ![]()
0 Comments
Leave a Reply. |