Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
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.
Im after some advice on running a server. I currently have one running at home, which stays in gnome, offering services like ftp, apache, samba and custom deamons.
Now i figure running a gui on a server isnt very good, performance wise. But, one of the services running is a MUD driver. I can boot the machine into text mode and run the driver there, but once its running nothing else can be done on the machine until you 'ctrl+c' and quit the driver to get the prompt back.
Is this normal behaviour for a server to be running, or should you always have access to the prompt. I suppose there may be another way to fire up the driver without losing the control, but i havent looked too much yet.
Hehe, fear no more. Help is here.
Once you run the service, you can do it by adding the & character in the end, which tells it to run in the background. Or if you have already run the service and forgot the & character, press CTRL+z and when you are put back in a command line, type bg and press enter.
This second way does the following. CTRL+Z stops the current command. And then the bg command puts it into backgroud. But it is easier to add the & character at the end of the command. However if you forget to do that, use the second way. Pretty handy trick
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.