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 using Debian 7.0 GNU/Linux distro on armv7l processor. There are four Workspaces on Xfce4 desktop. I want to keep active Workspace 2 while denying access of all user to it.
Is it possible to do so?
Actucally I have to start a java application on startup which must be run into a terminal. So if any user accidently kills terminal then java application also gets killed, I don't want so. Currently what I have done is, I started the applicaton in terminal on startup and shifted the terminal on Workspace 2 while keeping the main Java Application GUI on Workspace 1. So I want to deny access to currently running terminal from being killed.
Sounds like you want to just lock the screen, or do other users need to be able to log in? If the latter, look into something like nohup to run your program in the background so you can log off and let other users login.
Letting other users have access to your account is not a good idea!
The Java Application is based on GUI but it also requires terminal to run, I have tried to run the application without terminal also but when the Application was started it was becoming unresponsive so I ran the application in terminal, in current scenario terminal starts on system start-up and starts the Java Application with GUI. So if any person kills the terminal Java Application also gets killed. I want that if any user clicks on "cross" of terminal it should not get killed whereas the application should be terminated to end the process not the terminal.
Yes Mr. btmiller you are right I want to do the same thing because this Java Application displays the current running status of a loom machine.
Mr. frankbell it is possible because the Debian Image that I am using has default root account and no any other account is there. I am using A20-Olinuxino-Micro board from Olimex.
Ah, you didn't give this context before; what you're trying to do makes a bit more sense now.
Let me ask, does the Java app only display the status of the machine, or do users need to interact with it to control the machine? If it only displays status, you could lock the machine away and just have the display in a publicly accessible place (or use something like an X-terminal that only displays but does not accept input).
If users need to interact with this, though, maybe a technical solution is not the right way to go. If this is in a professional work environment that only trusted people can access, you could just post a sign that says "please don't close the loom control application" and people should accept it. If they try to get cute and do it anyone, sounds like their supervisor needs to have a chat with them.
Yes sometimes users need to interact with the Loom during certain situations e.g. when the threads are being changed (during alteration), when any sudden stoppage occours (Knock Off Input is detected from Loom) etc.
The Loom operators i.e. weavers are not that intelligent, they don't care about any messages being displayed.
In current sitiation the Java Application requires terminal to be run without which it gets hang and becomes unresponsive and requires whole system reboot.
If accidently someone closes the terminal the Java Application also get closed as it is dependent on terminal.
What I want is that user can only be able to close the Java Application from its close button and not from terminal means if someone clicks on close button of termianl then it should not get killed.
So for that I have created a shell script which I added in system startup options, this shell script starts the Java Application with terminal and after 2 seconds shifts the terminal on Workspace 2 so only Java Application is visible to users on workspace 1.
Last edited by gauravpathak129; 01-05-2014 at 11:42 PM.