openelec.tv - Useful Terminal Commands

Useful Terminal Commands | OpenELEC Mediacenter

Openelec.tv Spined HTML

Useful Terminal Commands | OpenELEC Mediacenter Home FAQ OpenELEC FAQ Raspberry Pi FAQ Kodi FAQ (external) Community FAQ Privacy FAQ Documentation Supported Platforms Intel x86 Raspberry Pi 1 & 2 WeTek Play Cubox-i Installing OpenELECVitalInstall Guide Manual Installation Dual Boot Network Boot - NFS Network Boot - iSCSI User guide Adding Media Sources Configuring Screen Resolutions Configuring Audio Accessing Samba Server Useful Terminal Commands Kodi Wiki (external) Kodi Addons (external) Configuration Updating OpenELEC Compile from source Development workflow Downloads Forum Donate Home Documentation User guide Useful Terminal Commands Table of contents: Introduction Putty Useful commandsWideusage Introduction SSH provides secure remote wangle to your OpenELEC install. This guide shows some vital SSH commands you may need. SSH or Secure Shell is a vital secured network protocol that enables a secured remote tenancy of a device that has SSH enabled. And considering this is a tutorial for people who never worked with it, it doesn't need a worthier description. You don't have to be an expert so I'm only going to tell what you can do with it for use with OpenELEC's XBMC. The main function we are using SSH now for OpenELEC's XBMC is editing the configuration files that enable or pinpoint functions like network access, SAMBA, audio, etc. Maybe in the future it will help you with increasingly wide functions, but then this tutorial will be updated to.Moreoverthey're working on terminal support from within OpenELEC's XBMC, which will have the same function as SSH. Only with terminal support, there's no need for a second computer to log in to OpenELEC's XBMC. You just unshut a terminal for putting in commands. As this is not an option yet, I'll write this tutorial only with SSH usage for now. Putty To make a connection with OpenELEC's XBMC through SSH, we need a program that supports such connections on the computer that is going to make the connection. I unchangingly use the program Putty, which is self-ruling and easy to use. All other programs that can work with SSH connections will do the job also, so please finger self-ruling to download flipside program. Putty can be downloaded here: https://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html (for Windows users, download putty.exe). Once downloaded, store the program in a place where you can find next time. It isn't a installer so you don't going to see it in your Programs list. Double click the icon: And the pursuit screen will pop up: The only info we have to requite to this program is the IP write which has been given to OpenELEC's XBMC, everything else is default at start-up. You can find your IP write within XBMC under system > system info > network.Withoutthat you hit theUnshutbutton and you'll be directly asked for your login name, which is root, then requite an Enter and the screen asks for your password, which is openelec. The password in OpenELEC cannot be reverted by the user. Only by waffly the OpenELEC source lawmaking and recompiling a new build will it be possible to use a variegated password. When typing a password on a Linux commandline, you won't see anything transpiration while typing. It's okay, now just hit Enter again: It's just like a terminal from Linux, or a writ window from Windows, only now you can wangle the files and put in commands for OpenELEC's XBMC. Useful commands Now that you know how to wangle OpenELEC's XBMC through SSH, here are some useful commands. These commands can be copied inside the terminal, only you have to right click and paste them instead of Ctrl + V (which will not work). The most important writ while OpenELEC is developing is how to restart XBMC without a reboot. To restart XBMC, simply type systemctl restart kodi To see what files and maps there are in the current directory, you can requite the pursuit command: ls -all This will exhibit all files and maps, just like you see them in any operating system, but than without the fancy GUI (displaying pictures of the files) If you want to go into a map (the purple names), type: cd <map name> for example, to go into the videos map, type: cd videos. You can moreover directly go to a specific map from the root, if you know the word-for-word map names. Ex.: If you want to go to the map movies inside the map videos, just type the pursuit command: cd videos/movies where the / marks the whence of the name of that specific map inside the first map. This you can do unlimited, as long as the maps exists. Between every map you place a / To go when one step, for example from /videos/movies to /videos use the pursuit command: cd .. To go when to the root (where you started when you logged in), use the writ cd To view a file (white colored) in the terminal (don't try this with video-, audio- and music files, as it will load an enormous value of characters) type the pursuit command: cat <file name> To edit a file in a specific map that you have loaded, you can use the pursuit command: nano <file name> This opens the file and let you edit the lines you want to. It is very basic. To go to a specific line, use the arrows on your keyboard. When washed-up editing and you want to unscratched the file, printing Ctrl + X and type Y, without that it will ask you which name the file must have and without putting in the right name printing Enter. If you unwittingly edited the file, you can say N to the question if you want to unscratched the file and all changes will be discarded. To make a new (empty) file in a current directory, use the pursuit command: touch <file name> Note that most files need an extension for the system to know what it is. For example a configuration file needs the extension .conf (like file.conf). To make a new directory, you can use the pursuit writ to make a new (sub)directory in the current directory: mkdir <map name> If you are in the root directory, and want to make a specific sub-directory in a map, the pursuit writ is needed: mkdir /<existing map>/<new to make map name>Moreoverhere you can add as much existing map names as you want, by separating them with a "/" Removing a directory is the same as making a directory, but instead of mkdir you use rmdir in the whilom commands. If a directory contains lot's of unwanted data, and you'll want to delete the whole directory, you may segregate to use the pursuit command. It forces a removal of a directory or file. Please use this only when you're very sure. The pursuit writ is based on a current directory that contains the file or directory that will be removed. If you want to use this writ from the root directory, just add all the map names to the file or directory (ex. /<directory1>/<directory2>/ etc.) surpassing the <directory or file name> without a space. rm -rf <directory or file name> To remove a separate file, use the pursuit command: rm <file name> To reprinting a file to a specific place on the same computer, use the pursuit command: This writ will reprinting <file name> in the current directory to <directory2>, which is in <directory1>, which is in the root directory. The tilde ~ in this writ tells SSH to go first to the root directory, from there you have given the navigation to the file. cp <file name> ~/<directory1>/<directory2>/ If you want to reprinting a file to a directory that is within the same directory as the goal directory (ex. you want to reprinting from /videos/ to /videos/drama/foreign/), you can moreover use the whilom lawmaking without the ~. Please note that <directory1> will now be the map /drama/ and <directory2> will be /foreign/, considering we don't go when to the root directory. The whilom lawmaking can moreover be used for moving a file, just replace cp in mv. If you want to exhibit your current TCP/IP configuration (such as you IP address, used network device, etc.) (just like ipconfig on Windows), type the pursuit command: ifconfigWideusage Now we're going to show you some increasingly wide commands, most of them you only need when you're facing some problems and want to find out what it causes. Displaying CPU and memory usage by the system can be washed-up with the pursuit command: top You'll get the pursuit screen: To sort the list by memory usage, use the pursuit key combination: SHIFT + M To sort the list by CPU usage, use the pursuit key combination: SHIFT + P To exit this screen, use the pursuit key combination: SHIFT + Q I know most of you will not know what everything in this screen will tell, but most of you know when you have a very upper percentage CPU or memory usage, that that particular process is not working well. So when you report a bug or ask for help, you'll have detailed info which you can requite for a solution! To print a whole list of zippy processes, can be displayed with the pursuit command: ps -ef Add |more without -ef, the list will pause when the terminal window is full.Printingany key to resume (if the list is too long, it will pause then when the terminal window is full). Add |grep <name> without -ef to filter the list. This will show only the processes containing the word <name>. Add |grep -v <name> without -ef to filter the list. This will show only the processes that not contain the word <name>. A list of Kernel messages can be displayed with the pursuit command: dmesg To unscratched this Kernel messages to a file, use the pursuit command: dmesg >> dmesg.txt This file will be saved in the current directory, it can be wise to go to a specific directory (that is for example wieldy by SAMBA) to unscratched this file. To view worldwide log-files of the system, use the pursuit writ to enter the directory that's containing them: cd /var/log For a live-view of an existing log-file (new widow data will be shown directly and automatically scroll down), type: tail -f <log-file> Notice that the whilom writ will only work in the current directory of the log-file. To use this writ from root, requite moreover the containing directories as described before. To exit the live view, use the pursuit combination CTRL + C. We've implemented an will-less way of uploading troubleshooting logs to the pastebin website. This can be achieved in the pursuit way. Example 1. we ask you you to upload the message file: paste /var/log/messagesWhilomwrit will return with an URL to the pastebin website and your message file can be seen there. Example 2. We ask for the dmesg output : dmesg |pasteWhilomwill not show anything in your console, but will rather paste the output of your dmesg to the pastebin site.Thenit will return with a URL which can be shared with developpers or in the forum for others to troubleshoot issues. These commands will terminate your connection and turn of / reboot your system poweroff reboot Copyright © 2009-2018 OpenELEC . All Rights Reserved. Home FAQ OpenELEC FAQ Raspberry Pi FAQ Kodi FAQ (external) Community FAQ Privacy FAQ Documentation Supported Platforms Intel x86 Raspberry Pi 1 & 2 WeTek Play Cubox-i Installing OpenELECVitalInstall Guide Manual Installation Dual Boot Network Boot - NFS Network Boot - iSCSI User guide Adding Media Sources Configuring Screen Resolutions Configuring Audio Accessing Samba Server Useful Terminal Commands Kodi Wiki (external) Kodi Addons (external) Configuration Updating OpenELEC Compile from source Development workflow Downloads Forum Donate