Linux - Security This forum is for all security related questions.
Questions, tips, system compromises, firewalls, etc. are all included here. |
| 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
 |
GNU/Linux Basic Guide
This 255-page guide will provide you with the keys to understand the philosophy of free software, teach you how to use and handle it, and give you the tools required to move easily in the world of GNU/Linux. Many users and administrators will be taking their first steps with this GNU/Linux Basic guide and it will show you how to approach and solve the problems you encounter.
Click Here to receive this Complete Guide absolutely free. |
|
 |
08-30-2005, 02:20 PM
|
#1
|
|
LQ Newbie
Registered: Aug 2005
Location: Cullowhee, NC
Posts: 19
Rep:
|
Security Risk
I am new to ubuntu and just installed Firestarter and I have to login in to root before I can run it, i created a launcher with the command "sudu firestarter" in the terminal and i have to leave the terminal open if i want firestarter to keep runnin. I was wondering since the terminal is in root and is still running, if it was a security risk and if so, how do i fix it?? Any suggestions are appreciated!
|
|
|
|
08-30-2005, 02:24 PM
|
#2
|
|
Senior Member
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 4,554
|
Usually a program like that is defined as a service, or daemon. (On my system, startup-scripts for these are found in /etc/init.d and you can look to these as examples.)
In any case, daemon processes stay logged-on all the time. You can also launch command-line programs into the background by ending the command-line with '&' and you can also look at the command nohup. No matter how you do it, you don't have to keep a console-session running just to keep the process running.
|
|
|
|
08-30-2005, 02:32 PM
|
#3
|
|
LQ Newbie
Registered: Aug 2005
Location: Cullowhee, NC
Posts: 19
Original Poster
Rep:
|
Thanx
Thanks alot, I just added the & in the launcher and have no problems, Thanx alot.
|
|
|
|
08-31-2005, 02:25 PM
|
#4
|
|
Senior Member
Registered: Nov 2000
Location: Seattle, WA USA
Distribution: Ubuntu @ Home, RHEL @ Work
Posts: 3,892
Rep:
|
Moved: This thread is more suitable in Linux - Security and has been moved accordingly to help your thread/question get the exposure it deserves.
|
|
|
|
| Thread Tools |
Search this Thread |
|
|
|
Posting Rules
|
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
HTML code is Off
|
|
|
All times are GMT -5. The time now is 07:23 PM.
|
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|