02-27-2008
Yes Duke,,
After completing the procedure you specified,,i didn't find any file xxx in that directory,,,and also some other files,,,but finally there are some files which i created previously...
After all,,i found that slice and its mount point in the df -kh output...
I understood that manually everytime i have to mount the slice as i didn't specified "yes" at mount at boot options...But should i need to do like this for every slice including root.
Will the files created after mounting the slice lasts after reboot also..
Can u please clear this concept?
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. UNIX for Advanced & Expert Users
Can any one Explain the artichture of Slice on SOLARIS PLATFORM.
OR else
where can i found artical on these topic.
akram shaik OCA
akram_tri_a@yahoo.com (2 Replies)
Discussion started by: smdakram
2 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
First I have to admit that I am not an unix expert, but I do know some basic things about the file systems.
Anywho, one of my users' File Manager is not showing up as it normally does upon login. When I run a "ps -ea" I see "dtfile" in the list, but it does not show up. It's not in any of the... (0 Replies)
Discussion started by: tdpearson
0 Replies
5. UNIX for Dummies Questions & Answers
I hope this question isn't too vague...
i recently switched from RedHat to Solaris 10, and found that the parts of a script that copy files between directories no longer work because escape sequences are appearing at the start and end of the filenames being read
#!/usr/bin/bash
cd... (1 Reply)
Discussion started by: jwm-wm
1 Replies
6. Shell Programming and Scripting
Is there a way in a shell script to make an user input appears as * (like a password) ?? (2 Replies)
Discussion started by: ce9888
2 Replies
7. Shell Programming and Scripting
I am having trouble finding the process, or subsystem, sendmail running on our client's server. They are runnning AIX version 5.3.9.0. When I run "ps -ef | grep sendmail" I only get my current ps process as a match. Running "ps -ef | more" and wading through the results also does not show sendmail... (2 Replies)
Discussion started by: moviedude
2 Replies
8. AIX
Hi everyone,
this strange error suddenly popped up out of no where
when I do a directory listing , the date part doesn't appear
root@oradb:/backup>ls -la
total 58069304
drwxr-xr-x 3 root system 4096 23 ▒▒▒ 21:56 .
drwxr-xr-x 44 root system 1536 23 ▒▒▒ 21:47... (4 Replies)
Discussion started by: filosophizer
4 Replies
9. Linux
hi i know this is irrelevant to the question above but i was wondering how to pt a restriction in the filename in linux. I want that it is impossible to add numbers into the filename, help will be rely great , thanx!
This posting was initially given as a reply to an unrelated thread. It has been... (2 Replies)
Discussion started by: samirboss
2 Replies
10. UNIX for Advanced & Expert Users
Gurus
I am running an AIX 7.1 system and have come across a strange issue.
I am trying to delete files from a folder using standard 'rm' syntax. After i delete the files , files re-appear again.
File renaming or editing does not help. Files re-appear with 0 bytes again. They are always 0... (5 Replies)
Discussion started by: abhijeet
5 Replies
LEARN ABOUT SUNOS
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)