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.
Where is the correct/default place in which artsd is run at startup? As far back as I can remember, it was always running without me having to do anything. After upgrading from Slack 10.1 to 10.2 (or something else I've done recently and not realized), it's not starting anymore, requiring a manual "artsd &". I'd stick it in rc.local or something, but I know it's started automatically in the past, and was wondering where that's done in Slack.
/etc/rc.d/rc.local can call it, if it's not called by something else (like a custom rc.artsd script). The upgrade to 10.2 may have disabled the execute flag on it. If you see an rc.artsd file in your /etc/rc.d, a little chmod +x will do the trick upon next boot.
No rc.artsd file in /etc/rc.d, and none there before as far as I know. "grep -R *artsd* *" in /etc shows nothing. Maybe it used to be run from a file somewhere that got replaced by a foo.new from the upgrade? It was always running from startup before and I never remember having to do anything to get that to happen. Anyone with pre-10.2 willing to grep around (that is, assuming it was the upgrade that changed it)?
Silly me, found it in my .xinitrc and never remembered putting it there. Thanks anyway for the help. Is it something that can/should be put in rc.local to be running all the time? I always thought of it as more of something X programs would be using.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.