Scribd
Upload
4 views

Process Priority

Uploaded by

Balamurugan Subramaniyan
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
4 views

Process Priority

Uploaded by

Balamurugan Subramaniyan
Copyright
© © All Rights Reserved
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
You are on page 1/ 2

Question: How To Change Priority Of A Processes

In Linux?
On the Linux system, all active processes have a priority and certain nice value.
Processes
with higher priority will normally get more CPU time than lower priority processes.
However, a system user with root privileges can influence this with
the nice and renice commands.
From the output of the top command, the NI shows the process nice value:
$ top
List Linux Running Processes
Use the nice command to set a nice value for a process. Keep in mind that normal
users
can attribute a nice value from zero to 20 to processes they own. Only the root
user can
use negative nice values.
To renice the priority of a process, use the renice command as follows:
$ renice +8 2687
$ renice +8 2103
GIT DevOps Interview Questions
Question: What is Git?
35/71
Git is a version control system for tracking changes in computer files and
coordinating work
on those files among multiple people.
It is primarily used for source code management in software development but it can
be
used to keep track of changes in any set of files.
As a distributed revision control system it is aimed at speed, data integrity, and
support for
distributed, non-linear workflows.
By far, the most widely used modern version control system in the world today is
Git. Git is
a mature, actively maintained open source project originally developed in 2005 by
Linus
Torvald. Git is an example of a Distributed Version Control System, In Git, every
developer's working copy of the code is also a repository that can contain the full
history of
all changes.
Question: What Are Benefits Of GIT?
Here are some of the advantages of using Git
Ease of use
Data redundancy and replication
High availability
Superior disk utilization and network performance
Only one .git directory per repository
Collaboration friendly
Any kind of projects from large to small scale can use GIT
Question: What Is Repository In GIT?
The purpose of Git is to manage a project, or a set of files, as they change over
time. Git
stores this information in a data structure called a repository. A git repository
contains,
among other things, the following:
A set of commit objects.
A set of references to commit objects, called heads.
The Git repository is stored in the same directory as the project itself, in a
subdirectory
called .git. Note differences from central-repository systems like CVS or
Subversion:
There is only one .git directory, in the root directory of the project.
The repository is stored in files alongside the project. There is no central server
repository.
Question: What Is Staging Area In GIT?
36/71
Staging is a step before the commit process in git. That is, a commit in git is
performed in
two steps:
-Staging and
-Actual commit
As long as a change set is in the staging area, git allows you to edit it as you
like
(replace staged files with other versions of staged files, remove changes from
staging, etc.)
Question: What Is GIT STASH?
Often, when you’ve been working on part of your project, things are in a messy
state and
you want to switch branches for a bit to work on something else.
The problem is, you don’t want to do a commit of half-done work just so you can get
back to
this point later. The answer to this issue is the git stash command. Stashing takes
the
dirty state of your working directory — that is, your modified tracked files and
staged
changes — and saves it on a stack of unfinished changes that you can reapply at any
time.

You might also like