[SOLVED] Only root can start app... suggestions for non-root xinit
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I use a Bluetooth mouse and may use other Bluetooth devices in the future. Any suggestions on how to make this work? I am using Backtrack 5 (ubuntu) and this is the last thing I need to get working. It has left me stumped.
Yes, bluetoothd is a daemon... not sure if you were telling or asking.
I am trying to avoid, changing the permissions, but I did run chkconfig and it wasn't there. when I tried to add it (`chkconfig -a bluetoothd`) it said it is "an unknown service".
Code:
root@bt$ chkconfig | grep bluetooth
root@bt$
Code:
root@xanlabot# chkconfig
alsa-mixer-save off
apache2 off
apparmor on
apport off
atd off
avahi-daemon off
binfmt-support off
bootlogd off
bridge-network-interface off
console-setup off
cron off
cryptdisks 0
cryptdisks-early 0
cups off
dbus off
decnet off
dmesg off
dns-clean on
etc-setserial on
failsafe-x off
fancontrol on
farpd off
framework-postgres 2345
gpsd off
grub-common on
gssd off
hostname off
hwclock off
hwclock-save off
idmapd off
irqbalance off
killprocs on
lm-sensors on
module-init-tools off
mysql off
nessusd off
network-interface off
network-interface-security off
networking off
ondemand on
openvpn off
pcmciautils on
pcscd off
plymouth off
plymouth-log off
plymouth-splash off
plymouth-stop off
portmap off
portmap-boot off
portmap-wait off
pppd-dns on
procps off
pulseaudio on
rc.local on
rcS off
rinetd off
rpc_pipefs off
rsync on
rsyslog off
screen-cleanup off
sendsigs 0
setserial on
snort off
ssh off
statd off
statd-mounting off
stop-bootlogd off
stop-bootlogd-single off
udev off
udev-finish off
udevmonitor off
udevtrigger off
ufw off
umountfs 0
umountnfs.sh 0
umountroot 0
urandom 0S
wicd on
winbind off
wpa-ifupdown 0
x11-common on
xplico off
daemon once started by root at a particular runlevel
continues to auto start with subsequent boot.
In my fedora core 14 the bluetoothd autostarts at runlevel 3,4, and 5.
If it is not auto started on your system,
you need only start it once as root at runlevels 3,4,5 and
subsequent boot will have the daemon autostart and you do not have to do
anything about it.
chkconfig command to execute as root
chkconfig --level=345 bluetoothd on
see man chkconfig
Hi
Try edit the /etc/rc.local on your machine put the entry to start the bluetoothd by using /usr/sbin/bluetoothd
by next boot it will pick automatically...
That did it! Thank you!
Quote:
Originally Posted by RSridhar
daemon once started by root at a particular runlevel
continues to auto start with subsequent boot.
In my fedora core 14 the bluetoothd autostarts at runlevel 3,4, and 5.
If it is not auto started on your system,
you need only start it once as root at runlevels 3,4,5 and
subsequent boot will have the daemon autostart and you do not have to do
anything about it.
chkconfig command to execute as root
chkconfig --level=345 bluetoothd on
see man chkconfig
I did not try the chkconfig command that you suggested however, this will be helpful for other things in the future. I did not know that about runlevels!
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.