- SYSTEMRESCUECD INSTALL FILEZILLA HOW TO
- SYSTEMRESCUECD INSTALL FILEZILLA FULL
- SYSTEMRESCUECD INSTALL FILEZILLA SOFTWARE
The Sercomm software uses "/dev/null0" and "/dev/null1" as shell strings in /etc/passwd to indicate whether the selected user can/cannot use the admin part of the web GUI. In fact because of the way Sercomm uses the /etc/passwd file it's only ever possible to have an account that can either log in through ssh or an account that can log in to the web GUI, you can't create an account that can do both. "root" can only be used for ssh, not for the web GUI, and the accounts that can be used for the web GUI (including admin) can only be used for the web GUI and not for ssh.
SYSTEMRESCUECD INSTALL FILEZILLA HOW TO
So any ideas on how to get the admin working again for the website? Nothing but I can still login as the other users and everything is working fine I can still write new files and read old ones and it's even keeping those through reboots. But I still can't login as an admin to the page, I try my root login, every way possible, I've tried the default admin login for the nas. For a while there the Shell root password had defaulted back to root, and every time i would change it and then reboot, it would come back as root, but today it stopped doing that. The odd problem I'm having now is that now I can't log in to the website with my admin (root) log in. So most of the time when this happens I have to unplug it over night turn it back on and it will load up. Periodically it will turn off all the lights but the ethernet, it will still respond to ping but nothing else not even the power button to turn it back on. So I have this odd problem, so my NAS I think it's has an over heating problem but I might be wrong.
You'll have to edit the file in your config partition and copy it to /etc, or restart the NAS so it copies it automatically.
You should edit the file using a Unix-compatible editor (WinSCP has one built-in, I don't know about FileZilla), or with vi from the command line. If my script can't find your twonky server (you can tell by using the ps command: you should see a bunch of processes running in /harddisk/volume_3/data/rc.d/twonky, if they run from /etc it means it's using the old one), you may have to modify the scriptdirs.txt in the config partition (/harddisk/volume_3/config/scriptdirs.txt in your case) to contain only one line that says: /harddisk/volume_3/data/rc.d.
SYSTEMRESCUECD INSTALL FILEZILLA FULL
If you want to start the program from the command line, you can simply type /harddisk/volume_3/data/rc.d/twonky/twonkymedia (optionally followed by -D you have to start the program with a full path or it won't work) or you should start the script that's stored in the flash ROM: /etc/rc.d/twonkymedia.sh You shouldn't use the script that comes with the Twonky download anyway: it contains some commands that don't work on the NAS (like ps -no-headers -o "%c" -p $PID). The Linux (Busybox?) program loader is telling you that there's a problem on line 1 of the script because it's trying to start "/bin/sh" to read the script, and it doesn't exist of course. The most common cause of this error is that you copied the startup script to your PC in ASCII mode and copied it back in BINARY mode, and now it contains a Carriage Return character at the end of each line, which is wrong in Linux.
0 kommentar(er)
