Raspberry Pi - $35 Linux computer

  • Thread starter Thread starter daz
  • Start date Start date
And if you want to check what transmission is running as try something like:

Code: 
ps -ef | grep transmission

Replace "transmission" with whatever the process is called or try a fragment like "trans" if you're not sure. Should show you the PID as well as what user it is running as
 
uncle_rufus said:
And if you want to check what transmission is running as try something like:

Code: 
ps -ef | grep transmission

Replace "transmission" with whatever the process is called or try a fragment like "trans" if you're not sure. Should show you the PID as well as what user it is running as
Click to expand...

This is what I get:



I can download to the SD card now but not the USB.
 
Last edited:
elrasho said:
This is what I get:



I can download to the SD card now but not the USB.
Click to expand...

Glad you got it sorted but in the name of learning here's what you're seeing above - the command you're running is "ps -ef", which if you try running on its own you'll see it lists all running processes (there will be lots). You're "piping" ( | )that command into "grep transmission" (or whatever) which is a command that searches lines of text for the phrase "transmission" and only prints lines that contain it. So by combining the two you're printing just the running processes that happen to contain that phrase.

That's why each time you ran it the third result was a "grep ..." command - this is the same grep you're running to get the results, and it shows up because it contains the pattern you are searching for (fun fact: if you add another pipe to the end of the command like so " | grep -v grep" that will run grep on the output again but this time the "-v" inverts the matching so it will only return lines which *don't* contain the phrase "grep", this way it'll hide those lines)

The remainder of each line of output means (I may get some of these wrong as I probably only know the ones useful to me), the first bit tells you what user is running the process, "pi" in this case for everything. The next two are the process IDs of the process and then the process ID of its parent (the process that launched it). In the case of transmission the parent is process 1 because they must have been launched by the system on startup, whereas the "grep" commands parent will be the process ID of the terminal you are running the command from. (if you ever have a hung process you can try to terminate it by running "kill XXX" and replace XXX with the process ID)

Off the top of my head I forget what the other columns mean, the final one before the command tells you how long the command has been running for and I believe the other part that looks like a time tells you what time the process launched.

Well anyway I've crapped on enough - apologies if you knew all this already I wasn't trying to patronise, I hope something above might be helpful for someone :p
 
I keep meaning to buy one of theses a guy at my old work had one, just not 100% sure what i would use it for i like the sounds of the pi cast stuff but i want it to be simple.
 
I just ordered one. Going to use it for some wake on LAN/ssh magic for an "always accessible" remote development environment. So excite.
 
Is anyone running OpenELEC on their Pi with the Storage mounted on a USB drive at all?

I've been told it makes XBMC faster to boot, but I've tried it with a Class 10 Kinston SD Card and a Kingston 32GB USB3 pen drive, and get boot times of 55 seconds - 1 minute, but when booting just off the SD Card, I get averages of about 40 secs to boot.

Am I doing something wrong or has the new version improved the boot times?

Thanks.
 
I'm running OpenElec off USB too. I'd ignore boot times the reason for using USB is to improve the speed of the xbmc menus and it certainly does by a good margin. Running the library from a mysql database on my server also seems to help a small margin
 
That would make more sense than just the boot up times, I'm planning on popping the Pi into a car so boot up times are a bit more critical, though 10-15 seconds shouldn't be too much if it means a smoother UI.

I've reverted it back to running off a 32GB USB3 stick with an 8GB EXT4 partition, and the rest as an NTFS partition so I can drop my music straight onto it from Windows.

It's not going to have any network connectivity so I'm thinking of turning off all the network services, and reducing the amount of graphics memory (it's not going to be playing any major video files considering the low resolution of the screen in the car).
 
You must log in or register to reply here.
Back
Top Bottom