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!
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 building a dedicated network appliance that need to automatically login into a KDE session as part of the bootup process. I am using Fedora Core 1 ( stock kernel ) and KDE is set as the default desktop manager, and I have went into the KDE control center->logon->convenience and checked "automatic login" and selected an account for it to automatically login after KDE startes up.
However, when it boots up, it stops at at the pre-KDE session logon screen no matter which account I choose for it to automatically log into. In addition, I have also enabled "password-less login" for the auto-login account to no avail. What am I missing here? Any ideas?
That makes sense, I will do some more searching and see if the new info helps me find the answer. I was thinking the logon screen was a basic X11 interface, but you are most likely right ( that it is GDM ). Thanks.
That was it. I started a Gnome session instead of the default KDE, then went to Fedora -> System Settings -> Login Screen->General and enabled automatic login, and it worked! Thankks for your help. Plus I have wake on lan WoL working, I just wish there was a sleep on lan SoL standard out there to remotely shutdown the Linux boxen.
What I am doing with all the Wake On Lan / Autologin stuff is making a linux box act like an appliance ( say, a Television ), with added features that are available because the appliance is actually a computer. The prototype wakes me up in the morning by receiving a WoL packet, then it boots up, logs in, and wakes me up ( right now it plays some tunes that are guaranteed to wake me up in the morning ). That part is good, I can even tell it to fire up certain playists and power it off with my TV remote control ( thanks LIRC! ), but if I forget to turn it off, I would like to have the same system that woke it up, tell it to shutdown/poweroff.
Now, scripting an SSH session/login then having it send the "shutdown -h now" command is an idea, but I would rather have something more elegant that did not include having to hardcode a username/password into a scheduled script ( via CRON ). Let me know if you have any ideas. The solution would have to account for the fact that the target system may already be off, but figure a ping check should be sufficient for that.
i doubt you will find a solution that causes a remote machine to shutdown without obtaining any kind of authentcation.
its just too much of a security risk.
maybe you could write a program that runs with root privilages (in /etr/rc.d/rc.local)
and listens for a UDP packet to a certain port.... (set your firewall to only allow UDP to that port that comes from a local ip address (yes i know that can be spoofed, but its bettr than nothing)
and then have your program look for a certian string like "go to sleep" in the UDP packets it recivs on the port, and puts the machine to sleep (or shutdown) if and when it recievs the packet.
it seems to be the only solution.
it will be quite easy provided you have a good knolege of network progrramming,