12-16-2008
Could anyone make sure for me:
database replicates are always occupy a whole slice? (cannot make a filesystem on that slice ?)
always need a database slice for each mirror hard disk?
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Does someone know how Unix or Linux implement
'diff' command ? Any good reference or the
algorithm will be better ?
Thanks (3 Replies)
Discussion started by: harrylong
3 Replies
2. UNIX for Advanced & Expert Users
how can i use a rlogin with out entered a password,
someone tell me about configure the next files
/.rhosts
/etc/hosts.equiv and /etc/hosts
but i not sure about that, or there are not enough
could you tell me how to do that? (3 Replies)
Discussion started by: jav_v
3 Replies
3. Programming
1 . How does va_arg implemented by system? (2 Replies)
Discussion started by: chenhao_no1
2 Replies
4. AIX
anyone can help me how to implement the timer on AIX?
I tried with 'setitimer' and its related functions, but it does not work correctly,the program exited each time.
thanks (2 Replies)
Discussion started by: Frank2004
2 Replies
5. Shell Programming and Scripting
Hi all,
could any of you please help me on my problem..
we are doing FTP (one report out put) from one server to another server through unix shell script program.
Due to the network issues, some times FTP process is hanging.
So we planned to modify the existing program with the following... (2 Replies)
Discussion started by: kishore_jasthi
2 Replies
6. Shell Programming and Scripting
Hi All,
My requirement is if the record is starting with 0, then do some processing.
if starting with 1, some processing
else (not with 0 or 1 ) then do some other processing.
i tried the following
case "$test" in
/^0/) echo "starting with zero ;;
/^1/) echo " with one" ;;
*) echo... (2 Replies)
Discussion started by: ssunda6
2 Replies
7. Shell Programming and Scripting
Hi All,
My requirement is if the record is starting with 0, then do some processing.
if starting with 1, some processing
else (not with 0 or 1 ) then do some other processing.
i tried the following
case "$test" in
/^0/) echo "starting with zero ;;
/^1/) echo " with one" ;;
*) echo... (3 Replies)
Discussion started by: ssunda6
3 Replies
8. Shell Programming and Scripting
Hi all, i'm quite new in the UNIX world. So maybe i'm going to ask simple questions but they are unsolvable for me...
I'm trying to implement the 'more' function or kinda of that, for improving my knowledges. But I encountered some problems that i hope u will help me to solve.
The code i... (0 Replies)
Discussion started by: Cellofan
0 Replies
9. Shell Programming and Scripting
hi
i have a file like
1,"A","B"
2,"C","D"
1,"E","F"
3,"G","H"
in output i need like
3,"G","H"
1,"E","F"
2,"C","D"
1,"A","B" (12 Replies)
Discussion started by: angel12345
12 Replies
10. Shell Programming and Scripting
hi,
i am having three files which is having following data
file1:
field1 field2 field3
1 A B
2 C D
3 E F
file2:
4 G H
1 I J
5 K L
file3:
4 M N (3 Replies)
Discussion started by: angel12345
3 Replies
LEARN ABOUT ULTRIX
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 unit. A slice unit is a concept for hierarchically
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 (primarily scope and service units) may be assigned to a specific slice. For each slice, certain resource limits may
be set that apply to all processes of all units contained in that slice. Slices are organized hierarchically 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.
Note that slice units cannot be templated, nor is possible to add multiple names to a slice unit by creating additional symlinks to its
unit file.
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(5) are allowed.
See the New Control Group Interfaces[1] for an introduction on how to make use of slice units from programs.
IMPLICIT DEPENDENCIES
The following dependencies are implicitly added:
o Slice units automatically gain dependencies of type After= and Requires= on their immediate parent slice unit.
DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set:
o Slice units will automatically 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 late system shutdown should disable DefaultDependencies= option.
SEE ALSO
systemd(1), systemd.unit(5), systemd.resource-control(5), systemd.service(5), systemd.scope(5), systemd.special(7), systemd.directives(7)
NOTES
1. New Control Group Interfaces
https://www.freedesktop.org/wiki/Software/systemd/ControlGroupInterface/
systemd 237 SYSTEMD.SLICE(5)