10-31-2008
Well since I am not an expert on this I find it hard to say exactly what would need to be supported, but yes, Linux Apache Mysql PHP, and all the bells and whistles that keep this all working updated, patched, security holes filled, fully configured proactively to avoid problems. Server monitoring to alert when problems occur, load balancing etc.
Is this called a fully-managed-service ? I want that
7 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I've had a VXFS filesystem get corrupted and now it won't mount.
Can I run a fsck -y on the raw disk device or should something be
done within veritas? Veritas does not see the disk at the moment. (2 Replies)
Discussion started by: ozzmosiz
2 Replies
2. Solaris
Hi Experts,
While playing with smf in my local system ( which is not in production ) i am unable to restart the service svc:/network/nfs/server:default . I tried starting it in different way, however unable to restart the same.
I was checking the dependency for that I disabled the... (11 Replies)
Discussion started by: kumarmani
11 Replies
3. Shell Programming and Scripting
Hello All,
Firstly, the systems involved are Solaris 9/10 x86 and SPARC.
At present, we have an internally written file transfer system that we use to manage incoming transfers and distribute the files to relevant processing systems. This is based on log watching. Over the years its become... (3 Replies)
Discussion started by: dcarrion87
3 Replies
4. AIX
This is a warning because we just went through searching for the error for some weeks.
In many cases the managed systems (respectively their service processors) reside on their own network, together with the HMC(s) managing them. In this setup usually the HMC acts as DHCP server for the service... (0 Replies)
Discussion started by: bakunin
0 Replies
5. AIX
Folks,
Please have a look to the attached screenshot from my managed node's HEA configuration option page. I would like to know - what does "Flow Control Enabled" checkbox help us with if opted for?
Thanks!
-- Souvik (3 Replies)
Discussion started by: thisissouvik
3 Replies
6. AIX
How to find Physical server uptime from HMC/ ASMI.
Server was in standby mode. We have started the Lpar manually. Server rebooted automatically but no information updated in Lpars's errpt, alog.console or HMC prior to the reboot. (1 Reply)
Discussion started by: sunnybee
1 Replies
7. Red Hat
Hello,
We are installing a group of stand-alone RHEL 7.1.3 servers for a new application in our environment. We are new to RHEL and would like to know what is the best way to clone the OS once we have the 1st install in the LAB with all the apps installed and passed all security checks. From... (3 Replies)
Discussion started by: Steve_9999
3 Replies
LEARN ABOUT MOJAVE
systemd-networkd-wait-online.service
SYSTEMD-NETWORKD-WAIT-ONLINE.SERVICE(8) systemd-networkd.service SYSTEMD-NETWORKD-WAIT-ONLINE.SERVICE(8)
NAME
systemd-networkd-wait-online.service, systemd-networkd-wait-online - Wait for network to come online
SYNOPSIS
systemd-networkd-wait-online.service
/lib/systemd/systemd-networkd-wait-online
DESCRIPTION
systemd-networkd-wait-online is a one-shot system service that waits for the network to be configured. By default, it will wait for all
links it is aware of and which are managed by systemd-networkd.service(8) to be fully configured or failed, and for at least one link to
gain a carrier.
OPTIONS
The following options are understood:
-i, --interface=
Network interface to wait for before deciding if the system is online. This is useful when a system has several interfaces which will
be configured, but a particular one is necessary to access some network resources. This option may be used more than once to wait for
multiple network interfaces. When used, all other interfaces are ignored.
--ignore=
Network interfaces to be ignored when deciding if the system is online. By default, only the loopback interface is ignored. This option
may be used more than once to ignore multiple network interfaces.
--timeout=
Fail the service if the network is not online by the time the timeout elapses. A timeout of 0 disables the timeout. Defaults to 120
seconds.
SEE ALSO
systemd(1), systemd-networkd.service(8)
systemd 237 SYSTEMD-NETWORKD-WAIT-ONLINE.SERVICE(8)