Just a thought. What if you start the daemon as administrator?
IIRC admin is always "on" but that is only poor memory.
Or even better, create a new user that only has permission to do what you need it to do. Like the Apache user is for the Apache webserver.
Sounds like the best and safest way to do things if I knew how to deal with user account already
I am behind on my linux cookbook, which is a book on how to use linux. This motivates me. So is there a programmatic way to create such a user name? I wanted to spend the least time to set up and tweak each unit after my program is ready. If I can run a script or c program to create this account, it will be even more attractive option.
If I just installed the script that calls my daemon with sudo update-rc.d, the daemon will run as root, at system boot, correct? There's no need for anyone to log on for daemons to start, right?
I feel like different linux flavors are equally difficult to me since there is a command for everything and most of which I don't know. Programming on linux is probably not related to ease of use of GUI. I have a pidora image that I have not touched yet. Since raspberry pi recommends the raspbian distribution, I followed along with installing debian on my older laptop. Installation was not bad neither was GUI under KDE. It's relatively responsive on a 2.4GB core 2 duo and seems to run fine with 3GB ram. My main laptop with 4GB ram always fills up easily when windows vista loads up and I felt like it needs 6GB to do "blink"