question about autostart.sh [SOLVED]

monty_cantsing · 2010-02-05 04:19:52

hi!
so i'm trying to get my eee-control-daemon to start up at startup . i checked around on some forums and initial reports seemed i should edit a file in init.d called rc.d. i couldn't find that and was nosing about in my home directory and found a file in /home/hey/.config/openbox called autostart.sh .
i put the following line

eee-control-daemon &

thinking that would do it, but the control daemon still doesn't start up until i run the command in the terminal. what am i doing wrong?
best,
monty

Last edited by monty_cantsing (2010-02-07 07:19:24)

pvsage · 2010-02-05 05:05:43

Have you tried wrapping it in a sleep command? Something like

`(sleep 30s && eee-control-daemon) &`

I consider this something of a kludge, but if it works...

Zwopper · 2010-02-05 10:54:14

Have you ran the setup?

sudo eee-control-setup.sh

That got it working for me, and then I put this in my autostart.sh to get the panel gui to start.

#Start Eee PC panel applet
eee-control-tray &

On next boot it worked.

Last edited by Zwopper (2010-02-05 10:56:33)

klanger · 2010-02-05 10:59:46

Installation
Ubuntu packages are available, see the news entries.
There's a guide and ebuild for Gentoo on the web.
'delboy711' at forum.eeeuser.com built a Mandriva RPM.
Note: eee-control is incompatible with most Eee PC ACPI scripts, fan-control scripts, et cetera. Please remove them prior to installing eee-control.
For a manual installation, unpack the source tarball and do, as root:
cd locale && sh update.sh && cd ..
python setup.py install --prefix=/usr
cp data/eee-control /etc/init.d/
eee-control-setup.sh
The last step runs a script which tries to set up auto-loading of the required modules and cleans up /etc/acpi/events from conflicting ACPI scripts.
Note: on Ubuntu Jaunty it is necessary to add --prefix=/usr to the setup.py command, since Python defaults to /usr/local in Jaunty, while sys.prefix, which is used internally by eee-control, still points to /usr.
To have eee-control-daemon automatically start at boot, symbolic links need to be created in /etc/rc?.d/. On Debian/Ubuntu systems this can be achieved with
sudo update-rc.d eee-control defaults
For other distributions, consult the manual.
Usage
Start eee-control-daemon manually with
/etc/init.d/eee-control start
or run it in debug mode in the foreground with
/usr/bin/eee-control-daemon -V
The GUI can be started by typing
eee-control-tray
You can put this into your session startup (Settings -> Session in GNOME). Starting with version 0.9.2, the Ubuntu packages automatically enter eee-control-tray into the session startup.

this is copied from http://greg.geekmind.org/eee-control/#install eee-control web page

Last edited by klanger (2010-02-06 08:53:45)

monty_cantsing · 2010-02-06 08:23:50

pvsage
i tried that sleep command with variable amounts of seconds , and no dice . i still have to type eee-control-daemon in by hand. i have to run it as sudo, is it possible that might be why it doesn't work from the /home/hey/.config/openbox/autostart.sh file ?

zwopper
i ran sudo eee-control-setup.sh and it everything checked out fine . my problem isn't with the eee-control-tray , that starts up for me no prob , but the tray won't connect to the daemon til i run eee-control-daemon manually

klanger
i don't know what half the stuff in your post is , but it looks like it's for a different distro . i'm running crunchbox with openbox as my window manager , so i don't have (Settings -> Session in GNOME) because i'm not running gnome . is /home/hey/.config/openbox/autostart.sh the openbox equivalent?

thanks so much everybody for helping me reach a solution

klanger · 2010-02-06 08:36:42

the manual is from eee-control developer site, it tells how to install&run eee-control (& yes, the last part is for gnome wm not openbox) and the main part is for ubuntu, on which crunchbang is based on.

I know it is silly to ask, but how did you install eee-control?

like this:

For a manual installation, unpack the source tarball and do, as root:
cd locale && sh update.sh && cd ..
python setup.py install --prefix=/usr
cp data/eee-control /etc/init.d/
eee-control-setup.sh

The last step runs a script which tries to set up auto-loading of the required modules and cleans up /etc/acpi/events from conflicting ACPI scripts.
Note: on Ubuntu Jaunty it is necessary to add --prefix=/usr to the setup.py command, since Python defaults to /usr/local in Jaunty, while sys.prefix, which is used internally by eee-control, still points to /usr.

To have eee-control-daemon automatically start at boot, symbolic links need to be created in /etc/rc?.d/. On Debian/Ubuntu systems this can be achieved with
sudo update-rc.d eee-control defaults

using sudo?

ps. sorry for highlighting the wrong part of manual (I've been up for over 20h yesterday) neutral

Last edited by klanger (2010-02-06 08:55:09)

monty_cantsing · 2010-02-07 07:21:12

okay this one is solved . klanger ,

sudo update-rc.d eee-control defaults

did the trick . to answer an earlier question , i followed the instructions on the eeepc 1005ha post on this forum .

thanks again everybody for all your help !
monty

klanger · 2010-02-07 11:39:46

glad I could help smile

GuruX · 2010-02-07 23:09:06

I never had any problems with eee-control.
I just installed the jaunty .deb from here (running karmic). http://greg.geekmind.org/eee-control/
With version 0.9.4 I havenät had any problem. I got the icon in my tint2 tray, without even adding anything to autostart.sh

CrunchBang Linux

SEARCH

#1 2010-02-05 04:19:52

question about autostart.sh [SOLVED]

#2 2010-02-05 05:05:43

Re: question about autostart.sh [SOLVED]

#3 2010-02-05 10:54:14

Re: question about autostart.sh [SOLVED]

#4 2010-02-05 10:59:46

Re: question about autostart.sh [SOLVED]

#5 2010-02-06 08:23:50

Re: question about autostart.sh [SOLVED]

#6 2010-02-06 08:36:42

Re: question about autostart.sh [SOLVED]

#7 2010-02-07 07:21:12

Re: question about autostart.sh [SOLVED]

#8 2010-02-07 11:39:46

Re: question about autostart.sh [SOLVED]

#9 2010-02-07 23:09:06

Re: question about autostart.sh [SOLVED]

Board footer