04-13-2009
What is your specific question here?
Why don't you search and get the answers yourself?
7 More Discussions You Might Find Interesting
1. Solaris
hi everybody,
my name is samir, i m from delhi,india. i m a student in solaris. just few days ago i had completed my course. can anybody tell me the possible interview questions in solaris. (1 Reply)
Discussion started by: samir_sinu
1 Replies
2. UNIX for Dummies Questions & Answers
Please please if anyone has time to answer them, this noob would highly appreciate it. Thanks in advance.
1. whats $# in a shell script
2. whats a $* in shell script
3. Explain nohup with an example
4. If $1 is the first parameter, whats $0
5. How do you see the return code of... (1 Reply)
Discussion started by: foxmulder123
1 Replies
3. Solaris
Hey,
My company is looking to bring on a Sr. UNIX Admin with Solaris 10 experience.
What are some solid interview questions I could ask about UNIX and Solaris 10 that would weed a good guy out from a bad?
Questions that don't involve long command lines would be the best.
Thanks (1 Reply)
Discussion started by: mikepatton21
1 Replies
4. Solaris
Hi,
Can anyone tell me which is the good site for solaris interview questions. Let me know if anyone has some material on the same. Thanks in advance. (1 Reply)
Discussion started by: amult
1 Replies
5. Red Hat
hello,
I have some doubts .plz help
if i try to ping from a server, it doesnt ping & gives different ip address, and in nslookup i get different ip address, what is the problem ?
if u cant ssh to a server what will be ur steps ?
give full iptables command to open port 22
... (1 Reply)
Discussion started by: abhigrkist
1 Replies
6. UNIX for Dummies Questions & Answers
Can anyone list the interview questions on Linux Internals?
Any link for the same will also be helpful.
In a job requirement of say C, linux internals what is expected about linux internals? (0 Replies)
Discussion started by: rupeshkp728
0 Replies
7. UNIX for Dummies Questions & Answers
Hi Unix experts,
I require interview questions on UNIX. Tomorrow I have to interview a guy of 2yrs experienced. So I require the Q&A's.
Please provide the questions in a manner from Basics to Advanced with grading. We mostly use that guy for Unix shell scripting (support, maintenance).
... (1 Reply)
Discussion started by: karumudi7
1 Replies
LEARN ABOUT CENTOS
systemd.slice
SYSTEMD.SLICE(5) systemd.slice SYSTEMD.SLICE(5)
NAME
systemd.slice - Slice unit configuration
SYNOPSIS
slice.slice
DESCRIPTION
A unit configuration file whose name ends in ".slice" encodes information about a slice which is a concept for hierarchially managing
resources of a group of processes. This management is performed by creating a node in the Linux Control Group (cgroup) tree. Units that
manage processes (primarilly scope and service units) may be assigned to a specific slice. For each slice, certain resource limits may the
be set that apply to all processes of all units contained in that slice. Slices are organized hierarchially in a tree. The name of the
slice encodes the location in the tree. The name consists of a dash-separated series of names, which describes the path to the slice from
the root slice. The root slice is named, -.slice. Example: foo-bar.slice is a slice that is located within foo.slice, which in turn is
located in the root slice -.slice.
By default, service and scope units are placed in system.slice, virtual machines and containers registered with systemd-machined(1) are
found in machine.slice, and user sessions handled by systemd-logind(1) in user.slice. See systemd.special(5) for more information.
See systemd.unit(5) for the common options of all unit configuration files. The common configuration items are configured in the generic
[Unit] and [Install] sections. The slice specific configuration options are configured in the [Slice] section. Currently, only generic
resource control settings as described in systemd.resource-control(7) are allowed.
Unless DefaultDependencies=false is used, slice units will implicitly have dependencies of type Conflicts= and Before= on shutdown.target.
These ensure that slice units are removed prior to system shutdown. Only slice units involved with early boot or late system shutdown
should disable this option.
SEE ALSO
systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7)
systemd 208 SYSTEMD.SLICE(5)