09-07-2009
It is a bad and risky practice, better to create another slice, say s0, and grant it all the available space. That said, on SPARC, newfs on slice 2 should be harmless assuming no other slices are used.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Does anyone have any advice on what print servers to use with Solaris I used to use intel but they dicontinued the model we used. I would just use lpadmin to set them up . Any advice on this would be very helpful. (2 Replies)
Discussion started by: xmildx
2 Replies
2. UNIX for Dummies Questions & Answers
Hello all,
I'm ufs file system, how can u use the same disk in another machine with the data in tact? to make it clear, I've an ufs FS in a mount point /file1 ( 8GB). now they decide to reintall the OS. After the reinstall, how can i get the same data as it is? will mounting the disk as /file1... (3 Replies)
Discussion started by: i2admin
3 Replies
3. Solaris
Hi,
Please can someone recommend me a cheap PCI Network card for Solaris 9 (9/05) for an Intel based PC (x86).
I currently have a US Robotics NIC installed, but Solaris does not recognise it and its been too much hassle to find drivers for it etc, so have decided to purchase another NIC that... (3 Replies)
Discussion started by: wajidc
3 Replies
4. BSD
Hi, I'm new to BSD and would like to create a dual-boot between Solaris Express Community Edition and FreeBSD.
I would just like to know if the Solaris UFS file system can be written to by BSD?
I know that BSD uses UFS2, but I'm hoping that it is backwards compatible with UFS1 provided that... (0 Replies)
Discussion started by: Johnny SSH
0 Replies
5. UNIX for Advanced & Expert Users
Hello,
For a company I have to check if it is possible to migrate there environment from a solaris 8 to solaris 10.
Is there a tool with which I can check if the libraries running now on the 8 are compatible with the 10?
Kind regards (3 Replies)
Discussion started by: chelle007
3 Replies
6. Shell Programming and Scripting
Hi folks
There are about 200 csh scripts (I didn't wrote them). Do all those scripts run with tcsh without modification? Is tcsh 100% compatible with the plain-old csh?
$ which csh
/usr/bin/csh
$ which tcsh
/usr/bin/tcsh
$ uname -a
SunOS purzelse 5.9 Generic_117171-07 sun4u sparc... (2 Replies)
Discussion started by: slashdotweenie
2 Replies
7. Solaris
how do you get start and end sector of a UFS slice? (2 Replies)
Discussion started by: orange47
2 Replies
8. Solaris
i heard some where veritas volume manager wont work on solaris x86. i have installed vmware into my 32bit xp machine. i am planning to learn veritas..
is there an veritas volume manager version compatible with solaris x86 machine? (2 Replies)
Discussion started by: chidori
2 Replies
9. Solaris
I'm prompted to start this thread following my attempt to help on this thread here (see my posts).
I was proposing the OP deep checked a Solaris ufs filesystem using:
# fsck -o full <filesystem node>
however this option does not appear to be valid on Solaris 10.
I've used... (8 Replies)
Discussion started by: hicksd8
8 Replies
10. Solaris
I have a Solaris 10 LDOM installed with UFS and another Solaris 11 LDOM with ZFS. I want to mount a folder on Solaris 10 to Solaris 11. I used the following:
sudo mount -F ufs 10.1.1.44:/export/home/amandeep/workspace /home/amandeep/workspace/mounts/ldom5
and it errors out with:
mount:... (7 Replies)
Discussion started by: amandeepgautam
7 Replies
LEARN ABOUT X11R4
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)