In the development process, it is often necessary to show something to someone, to demonstrate functionality. Sometimes an additional server is deployed for this purpose, but it is expensive, troublesome, and sometimes inexpedient. What else can be done in such a case?
In this part, we will talk about how to configure the autorun of the user service in the loginctl utility. Earlier we have already talked about the syntax of the program, how to switch sessions and terminate processes
Preparing the server implies that you create it (if you have not done it before), specify a ready image of the Windows operating system and bind the license to the server. The result is the ability to work with Windows Server. Preparing the server means that you create it (if you haven't done so before), specify a ready-made Windows operating system image, and bind the license to the server. The result is the ability to work with Windows Server and connect to it via RDP (Remote Desktop Protocol) for remote access.
We have looked at the syntax and other important features of the loginctl program, now let's talk about how to switch between sessions and terminate processes. It is very easy to do this and you don't need to have any specific knowledge. Next we will tell you how to implement it in practice.
In past articles, we've talked about what the loginctl utility is, as well as how you can find out information about a process. In this article, let's look at how you can view user information and, if necessary, switch the process.
MS IIS (Internet Information Services) is a set of services from the developer Microsoft, designed to run a web server and / or other services. MS IIS installs on the server to work with most known protocols.
We have already covered what loginctl is and its syntax. Now let's look at how to view session information. This task is accomplished with one simple command. It should not be difficult for you to view all active sessions. It allows you to view all active sessions at a given time. As you can see from the screenshot above, there are two active sessions. The first one is responsible for automatically logging into the GUI when Gnome is running, the second session is the console session in TTY3.