SlackwareThis Forum is for the discussion of Slackware Linux.
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 have a bluetooth mouse and keyboard which I would like to start up when my slack machine boots. I chmod +x to /etc/rc.d/rc.bluetooth and started hcid, sdpd, and hidd. The others, rfcomm, pand and dund I left off (as I have no use for them).
The problem is rc.bluetooth start spits out an error: Can't listen on HID control channel: Address already in use. If I restart it after boot (or use rc.local to do it) it works fine. If I start it and then start it again, the same error is displayed.
Does anyone know how I can fix this, without having to start, stop, then restart my bluetooth control?
When you make rc.bluetooth executable it will start up during bootup, ff you then login and try to start it manually, you will get an error (because it is already running).
If you need to restart the service to get your hardware working for some reason, then you could put a restart command in rc.local. But if memory serves, BlueTooth is started pretty close to rc.local anyway, so it might not give things enough time to settle down.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.