... that's actually the problem. You are frustrated (and I am being genuine) because for the first time in your life you're using a real computer !loopylee wrote:
Im not new to computers, ive been a windows user since windows 3.1.
I haven't tried this but it is likely to leave various files with the wrong permissions, at least I would watch for that.loopylee wrote:This is just what i was looking for.kusti8 wrote: gksu pcmanfm
Will give you a sudo file browser.
I would avoid videos unless I was generally kicking back and trying to learn around a topic. You are unlikely to learn what you need though for some specific problem by watching a lecture and especially from watching a video you randomly found on youtube. This is more true with programming than it is with changing a wheel cylinder in your car since the latter does involve physicality that is often useful to see done. But it's also very smart to read about that too.loopylee wrote:several peole tell me i need to set up a cron job to do this. That would be great if i could just get something to work.
Ive followed lots of youtube vids on how to get cron working but for
Programming can certainly involve frustration, try writing things in bash. First they tell you to put quotes around everything and then they tell you, well, not around that.me it does nothing. no files are writen, no text is is entered and no processes are started. like i said, so frusatrating.
Especially given that the Windows permissions scheme is very capable and extensive, e.g https://msdn.microsoft.com/en-us/library/bb727008.aspx . The fact that many people have essentially run their computers as root all the time does diminish effectiveness in practice, of course.Douglas6 wrote:I agree that LINUX file permissions should be understood, not ignored. But that analogy is a hoot, and the gratuitous Windows bashing a bit disingenuous.
We all agree it is frustrating to learn something new. I know I struggled to do the most basic thing with the pi when I first got it - I'm sure many others did too. But you need to help us to help you - we can only guess the hardware you have, the software you are trying to use and the object of the exercise. Only in this post do you mention what you are trying to achieve. There are lots of tutorials and projects that are raspberry pi based that measure and log temperatures. Whats your set-up? Are you using a guide to get this working and if so do you have a link?loopylee wrote:thanks for all your replies.
Some im sure will be usefull.
The only reason i bought a pi3 was to log the temperature in a greenhouse.
i have a usb thermometer which i have working fine from terminal.
all i have to do is type sudo temperv14 and im presented with the date, time and temperature.
im told that i can get this output writen to a file by writing a shell script and creating a crontab to run the script every 30 minutes.
if only the box would give me permission to run the script and let cron create and write the file.
i realy dont care that this little box can do other stuff or that i might break something im never going to use if i go poking around.
if it was easier to use it would be sat in the greenhouse doing its job untill the end of its days.
with windows i just have to load a cd, click the icon and i have a fully working thermometer thats recording temperatures.
at the moment owning a linux based maching seems like ordering a new car and being delivered 20000 pieces and 40000 oppinions on how to put it together.
I solved the rights problem by having temperv14 run as root and allow anyone to run it. That seemed the simplest solution.
sudo chown root temperv14
sudo chmod +s temperv14
This is what i get when i folow the instructions above.dasmanul wrote:Please type the following at a command prompt and post the output here, preferably in Code-tags:
Code: Select all
cd /home/pi/temperv14 ls -l ls -ld . which temperv14 ls -l $(which temperv14) crontab -l sudo crontab -l