SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I am running the latest slackware-current, a fresh install from a custom ISO.
I haven't been able to get cups to work since it was moved from /extra...
I have rc.cups set executable. It starts up at init. When I go to 'localhost:631' to configure it, I can log in, but when I try to do anything I lose the connection to 'localhost:631', and cupsd crashes. I can restart it, but the same thing keeps happening.
I was wondering where I could look ( a log file?) to see the error message when the cupsd dies?
I'm afraid that doesn't ring any bells for me, i didn't use the slackware released version. However, the log file you want is /var/log/cups/error_log or something similar, and if that isn't showing much, you may want to adjust the debug level cups.conf or cupsd.conf or whatever its called which i believe lives in /etc/. Sorry I can't check for you, i'm at my parents' house. Hope that helps anyway, and let us know how this turns out, very intriguing.
Just checked the current changelog...looks like I wasn't the only one to notice this problem. There's a new sysvinit package that fixes the way cups is run. Apparently it needs to be run in a 'subshell', but I have no idea what that is.
Hi, just a note, 'man bash', running a program or a command, script in a subshell would be enclosing in '(command)' parenthesis.
One more thing, if i'm not mistaken, if you use slack, it's good to keep it as a BSD style init, i heard it's easy to debug in case thing's go wrong, mabey there's something available for that, or you could just edit one of the script's in '/etc/rc.d' , i think i may be over stepping my bound's because lack of true understanding of these, i know there are some sysvinit script's in there, but i don't think any of them execute(almost default system), someone correct me if i'm wrong.