02-25-2020
If we can believe that we'll believe anything.
Anyway, what the h*ll does that mean??
An emergency is......e.g. a fire........maintenance is........er!!......should be planned? How do you get a mix of those two???
What is "emergency maintenance"? Answers on a postcard please!!
The only excuse is a power failure and any decent datacenter should have a backup power strategy for that.
All the pro's on here know that systems should be designed clustered, high availability, etc (typical outage 20 seconds). Who are they trying to kid?
This User Gave Thanks to hicksd8 For This Post:
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi
I faced a problem while booting linux which is as follows;-
*************************************************
Inode 146180 has illegal block(s)
xauth:error in locking authority file /home/root/.Xauthority
Fatal Server Error:
Could not create lock file in /tmp/tXo-lock
... (1 Reply)
Discussion started by: Abhishek
1 Replies
2. UNIX for Dummies Questions & Answers
Our SUn Solaris Server has crashed second time in 2 days, reason is not known , we are trying to determine what could have gone wrong, any ideas, the power supply seems to be fine, there is no response from keyboard,monitor etc and we had to do a hot boot yesterday..
Any suggestions what could be... (9 Replies)
Discussion started by: knarayan
9 Replies
3. UNIX for Advanced & Expert Users
We have had a server (Solaris 2.6) hardisk crash. When booting the server we get:
ok> boot -S
Boot Device: /sbus/espdmc@e, 8400000/esp@e,8800000/sd@0,0
short read 0x2000 chars read
disk read error
The only way we can get into the console is to
ok> boot cdrom
whereby everything (e.g.... (3 Replies)
Discussion started by: Breen
3 Replies
4. UNIX for Dummies Questions & Answers
Is it possible for a group of servers to monitor each other and then send an alert if one of them is no longer 'alive'?
Or if its easier have one server that monitors the other five and then sends an alert.
If so how would this be done?
Thanks (3 Replies)
Discussion started by: Sepia
3 Replies
5. Linux
Is it true that you can't have the crash dump server/client on the same server?
I know I've installed Nagios open source before, I though it's only for that kind of thing. I never though that Red hat ent 4 would be like client/server on the crash dump.
if someone is having problem with high... (0 Replies)
Discussion started by: itik
0 Replies
6. Programming
Problem
- Linux Client/Server Socket Application: Preventing Client from quitting on server crash
Hi,
I am writing a Linux socket Server and Client using TCP protocol on Ubuntu 9.04 x64.
I am having problem trying to implement a scenario where the client should keep running even when the... (2 Replies)
Discussion started by: varun.nagpaal
2 Replies
7. SCO
Hi there.
Well i have a really bad problem with my server:
UnixWare Version 5 Release 7
The system crash :wall: and show the error:
Panic: Kernel-mode address fault on user address 0x00000004 :eek:
If anyone knows about the reason of this error please give me a help
Sorry by my english.... (3 Replies)
Discussion started by: danilosevilla
3 Replies
8. Programming
The steps to test the problem
1. Open TCP Server
2. Open TCP Client
3. TCP Client sends data to Server.
4. Close TCP Server and the client also crash without any notification
Second wonderful test:
1. Comment the following statement in Client.c (at line 168) and compile it
Writen(... (1 Reply)
Discussion started by: sehang
1 Replies
9. Red Hat
hi,
i would like to configure netdump, but saving the var/crash in the server itself, not in another server.
could anybody tell me if this is possible?
thanks (4 Replies)
Discussion started by: pabloli150
4 Replies
10. AIX
Hi there
I've bought a used System p 9115-505. When I attach the LAN cable to my router the HMC receives an IP address from my router, but the HMC is unreachable. There are no open ports.
Does anybody know that problem?
Any help greatly appreciated. Greetings from Italy! (2 Replies)
Discussion started by: mediaset23
2 Replies
LEARN ABOUT LINUX
systemd.target
SYSTEMD.TARGET(5) systemd.target SYSTEMD.TARGET(5)
NAME
systemd.target - Target unit configuration
SYNOPSIS
target.target
DESCRIPTION
A unit configuration file whose name ends in ".target" encodes information about a target unit of systemd, which is used for grouping units
and as well-known synchronization points during start-up.
This unit type has no specific options. 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. A separate [Target] section does not exist, since no
target-specific options may be configured.
Target units do not offer any additional functionality on top of the generic functionality provided by units. They exist merely to group
units via dependencies (useful as boot targets), and to establish standardized names for synchronization points used in dependencies
between units. Among other things, target units are a more flexible replacement for SysV runlevels in the classic SysV init system. (And
for compatibility reasons special target units such as runlevel3.target exist which are used by the SysV runlevel compatibility code in
systemd. See systemd.special(7) for details).
IMPLICIT DEPENDENCIES
There are no implicit dependencies for target units.
DEFAULT DEPENDENCIES
The following dependencies are added unless DefaultDependencies=no is set:
o Target units will automatically complement all configured dependencies of type Wants= or Requires= with dependencies of type After=
unless DefaultDependencies=no is set in the specified units. Note that Wants= or Requires= must be defined in the target unit itself --
if you for example define Wants=some.target in some.service, the automatic ordering will not be added.
o Target units automatically gain Conflicts= dependency against shutdown.target.
EXAMPLE
Example 1. Simple standalone target
# emergency-net.target
[Unit]
Description=Emergency Mode with Networking
Requires=emergency.target systemd-networkd.service
After=emergency.target systemd-networkd.service
AllowIsolate=yes
When adding dependencies to other units, it's important to check if they set DefaultDependencies=. Service units, unless they set
DefaultDependencies=no, automatically get a dependency on sysinit.target. In this case, both emergency.target and systemd-networkd.service
have DefaultDependencies=no, so they are suitable for use in this target, and do not pull in sysinit.target.
You can now switch into this emergency mode by running systemctl isolate emergency-net.target or by passing the option
systemd.unit=emergency-net.target on the kernel command line.
Other units can have WantedBy=emergency-net.target in the [Install] section. After they are enabled using systemctl enable, they will be
started before emergency-net.target is started. It is also possible to add arbitrary units as dependencies of emergency.target without
modifying them by using systemctl add-wants.
SEE ALSO
systemd(1), systemctl(1), systemd.unit(5), systemd.special(7), systemd.directives(7)
systemd 237 SYSTEMD.TARGET(5)