11-06-2008
Quote:
Originally Posted by
incredible
slice 1 is used for swap space. actually you can use any slice for your metadb ..Don't ask me why -->
... but its a standard practise to use the last slice for your metadb
Thanks incredible...
In My cenario also we use slice 7 only, I myself use slice 7 only, without knowing the reson and thought may be there be some......
Last edited by Reboot; 11-06-2008 at 02:00 PM..
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi, iam learning MySql. Iam trieing to create a table in the database "guestbook"
at the command line in mysql heres what i type but i get a error
mysql>create table guestbook
->(
-> name varchar(40) null.
-> url varchar(40) null.
-> comments ... (3 Replies)
Discussion started by: perleo
3 Replies
2. Programming
Hi ,
While trying to compile a PRO*C code on unix using makefile i get the following errors. i am now working on a 10g migration (from 8i) ...
these makefile perfectly work in previous version.
ld: fatal: file... (7 Replies)
Discussion started by: sivalives
7 Replies
3. HP-UX
Hi
I have locally compiled and installed gcc-4.1.2 in directory /usr/local/pkg/gcc/4.1.2/bin/gcc
I want to compile beecrypt using this new compiler , So i have done
setenv CC usr/local/pkg/gcc/4.1.2/bin/gcc ( Note this configuration is running properly with older version of... (1 Reply)
Discussion started by: vasanthan
1 Replies
4. Solaris
on 2 node x86-cluster, I 'm trying to configure Mysql with failover zfs,
I could create resource group and logicalhostname for mysql but resource creation fails, probably because the same Zpool was used for creating another HAstorageplus storage resource.
the zfs which mysql is going to use... (0 Replies)
Discussion started by: upengan78
0 Replies
5. UNIX for Dummies Questions & Answers
Hi,
I'm facing problem compiling proc on Solaris 10, with proc version 9.2.
I'm not able to create .o
This is how it looks:
$make
. . . Making linkable xxx.o
proc sqlcheck=full user=/ include=../include include=/aa/bb/include iname=xxx.pcx
Pro*C/C++: Release 9.2.0.1.0 - Production on Thu... (1 Reply)
Discussion started by: suhaswallur
1 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I'm facing problem compiling proc on Solaris 10, with proc version 9.2.
I'm not able to create .o
This is how it looks:
$ make
. . . Making linkable rim_grd_main.o
proc sqlcheck=full user=/ include=../include include=/rims/prod/include iname=rim_grd_main.pcx
Pro*C/C++: Release... (1 Reply)
Discussion started by: suhaswallur
1 Replies
7. Solaris
Hi,
I'm facing problem compiling proc on Solaris 10, with proc version 9.2.
I'm not able to create .o
This is how it looks:
$make
. . . Making linkable xxx.o
proc sqlcheck=full user=/ include=../include include=/aa/bb/include iname=xxx.pcx
Pro*C/C++: Release 9.2.0.1.0 - Production on... (2 Replies)
Discussion started by: suhaswallur
2 Replies
8. UNIX for Dummies Questions & Answers
Hi Guys,
Good day ULF! Can you assist me in creating a script that will email once an error has occurred. It's like this, I have script that is used for monitoring, distinct keywords on the status are OK and Error respectively. Then I created another script that will call for the monitoring... (2 Replies)
Discussion started by: rymnd_12345
2 Replies
9. Shell Programming and Scripting
Hi. My name is Mirko
I have two file.
File 1:
mio@mio.it
tst@test.com
bye@bye.fr
File 2:
error 08 ffff mio@mio.it test
error 05 ffff bye@bye.fr test
error 11 ffff tst@test.com test
error 65 ffff mio@mio.it test
error 55 ffff bye@bye.fr test
Examples
I would like to send a mail... (2 Replies)
Discussion started by: Gionfalco01
2 Replies
10. Solaris
I issue the following command to create a boot instance from an active boot instance on solaris 11.1.
beadm create -a -d "Oracle x86 64 BIT Solaris SunOS Rel 5.11 Ver 11.1 10/2012 Enable SSH " OraSolBcp
I get the following error below;-
be_mount_callback: failed to mount dataset... (5 Replies)
Discussion started by: Tenyhwa
5 Replies
LEARN ABOUT OPENSOLARIS
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)