05-08-2004
check this one, I am not sure!
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
Hi,
I'd like to add two new disk (mirrored each other) in a machine still on line.
The machine is mirrored with SDS. the idea is to add two new disk and mirroring them in order to add a new mount point like "/produit" with only half of the new disk.
who could send me exemples or tell me how to... (1 Reply)
Discussion started by: guillaume35
1 Replies
2. AIX
if the system pegs at 100%, can I reserve .2cpu to allow for logins and such? the oracle rman/other activities take up some resources on occassion ... 3.8 procs for the system and .2 reserved?
I'm not sure how to tackle this issue ... is this a good use for WLM?
any thoughts? (1 Reply)
Discussion started by: A Stewart
1 Replies
3. Solaris
Hi there
I am about to mirror a Solaris 10 x86 box (SunFire X4100) onto a secondary disk using svm (current system is one disk). My question is this, on X86 boxes there is a slice 8 defined as boot partition (and also a slice 9, dunno what its used for tho). Do I need to mirror this boot slice... (0 Replies)
Discussion started by: hcclnoodles
0 Replies
4. Solaris
Hey guys,
This is how I originally had my drive setup... This is on a solaris 10 box
***BEFORE***
Current Disk = c0t1d0
Current partition table (original):
Total disk cylinders available: 7506 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks... (2 Replies)
Discussion started by: kingdbag
2 Replies
5. Solaris
Hi, i encounter problem during middle progress of mirroring. i trying create a mirror (metainit) to my slice 7. Who's have any experience, can you please help me?
i tried create a state database replica "metadb -afc1 /dev/dsk/cxtxdxs7" but at it show it cannot create caused /dev/dsk/cxtxdxs7... (2 Replies)
Discussion started by: webster5u
2 Replies
6. IP Networking
I new to linux and am setting up a slice server. I actually made it to installing Apache but some how I messed up the ip tables. I cant access the server by sftp or putty. Im using the web interface at slice. I am logged in as a super user but cant do certain funtions. I guess i need to be logged... (0 Replies)
Discussion started by: DigitalExtreme
0 Replies
7. Linux
Hi all
I am testing backupPC as a backup solution for machines, as far as i knew, backuppc cannot combine more than storage from different slices so it have to be in one slice my question is, what is the easy way to offer a virtual logical drive expanded/expandable to backuppc, i mean i want to... (1 Reply)
Discussion started by: XP_2600
1 Replies
8. Solaris
is there a command that would zero swap slice? I found these instructions: but hoping there is some swap-specific command (3 Replies)
Discussion started by: orange47
3 Replies
9. Solaris
Part Tag Flag Cylinders Size Blocks
0 root wm 259 - 2666 4.70GB (2408/0/0) 9863168
1 swap wu 3 - 258 512.00MB (256/0/0) 1048576
2 backup wm 0 - 4091 7.99GB (4092/0/0) 16760832
3... (4 Replies)
Discussion started by: chidori
4 Replies
10. Solaris
we have a ZFS file system that was created as a pool of just one disk (raid on a SAN) when this was created it was done as a whole disk, and so EFI label.
now we want to mount this file system into an LDOM.
my understanding of how ldom's and disk works this is that we can only do this as a... (1 Reply)
Discussion started by: robsonde
1 Replies
LEARN ABOUT POSIX
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)