Hi,
I'm working with an E450 server and it has one network card configured with 2 local and internet IP addresses.
Presently, the local IP is set as the primary address while teh Internet IP is set as the secondary address. I wish to change this and make the local IP secondary and the... (2 Replies)
how can i check that a variable is between 0-100, like if i ask a user to input a number between 1-100 and i want to excute commands WHILE that number is between that range or else i will keep asking the user to make another input
here's what i got
#!/bin/bash
echo "Guess my secret number... (2 Replies)
I want to print between the range two patterns if a particular pattern is present in between the two patterns. I am new to Unix. Any help would be greatly appreciated.
e.g.
Pattern1
Bombay
Calcutta
Delhi
Pattern2
Pattern1
Patna
Madras
Gwalior
Delhi
Pattern2
Pattern1... (2 Replies)
Hi
Can someone give me a shell script that can ping a range of IPs and return IPs which are not pingable.
Range for example say 192.168.0.1 to 192.168.0.50 and whichever are not pingable then return the IP.
Thanks for your help (3 Replies)
Hi All
dhcpd.conf has a range of IPs sa for example( 192.168.1.201 192.168.1.220)
So this is the range of IP addresses the server will issue to DHCP enabled PC clients booting up on the network
How do i know which IPs are being used or which IPs from the range are assigned to dhcp enabled... (11 Replies)
Hi..
Anyone can help me..I have setup my linux fedora server and i want to restrict access to my server.Basically i control using iptables.I'm not sure how to write an iptables rules to control drop all connection to port 8080 and allow only certain ip can access the instance on port 8080 example... (0 Replies)
Hi, (i'm sorry for my english)
I'm a problem on boot sco unix 5.0.5 open server.
this stop at "Checking protected password and checking subsystem databases"
(See this image )
I'm try this:
1) http://www.digipedia.pl/usenet/thread/50/37093/#post37094
2) SCO: SCO Unix - Server hangs... (9 Replies)
Hi experts,
I have an X86 as my IPS server running ( uname -a SunOS 5.11 11.1 i86pc i386 i86pc). the IPS has the following package version:
prdb01b:~# pkg list -fa entire
NAME (PUBLISHER) VERSION IFO
entire ... (0 Replies)
I have installed WL on Solaris 11 and have to create IPS packaging for following directories so that
/local/apps/wl/wls12.x
/local/apps/wl/oraInventory
/local/apps/wl/jdk/jdk1.x
Can someone provide the steps for creating IPS or point to the website where I can get help.
Thanks,... (2 Replies)
Hi guys, I'm creating custom package for deploying a bunch of public keys for some root servers we have. I have created script and it works but my problem is how to call this script when I want deploy package with puppet on server?
Oracle documentation provided only example for first boot script... (0 Replies)
Discussion started by: solaris_user
0 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 237SYSTEMD.SLICE(5)