Sponsored Content
Operating Systems Solaris need help on containers/zones Post 302245275 by upengan78 on Thursday 9th of October 2008 05:43:55 PM
Old 10-09-2008
Quote:
Originally Posted by avronius
What type of maintenance issues do you have?

Moving them into a container might not resolve your issues, instead making your environment more complex...
I do not want to see " can't open boot device" "disk error" kind of messages. I do not want these work stations shock me suddenly going offline due to any hardware failure. it has been happening regularly with these workstations such type of things..in case of such issues every time I have to take out HDD and try it in different machines, if that does not help then mirror another disk put it in these workstations...my space in the room going waste..these machines need keyboard connected to boot them..i do not have spare ones if something goes wrong with existing ones...more important is system is going down anytime causing loss of work to logged in users...

always these systems go out of swap space, there is limited disk space, /var always around 100%, can't patch them, some days back , it was not hard disk issue but I had to move hard disk to other machine , looks like bad memory on original machine...so such issues...

i don't think i should wait for this hardware to die. Also buying 4 separate sparc machines would be costly. what better way is there than using containers ?
 

5 More Discussions You Might Find Interesting

1. Solaris

Clustering Solaris Zones/Containers

Hello everyone. I'm working on a fairly large project at my company and have been looking for some guidance. I just happened to stumble on this forum when looking for help with Solaris, so I'm hoping that you all won't mind me bothering you with my questions. :) Anyway, here goes. Is it... (8 Replies)
Discussion started by: trouphaz
8 Replies

2. Solaris

solaris containers/zones reboot order

Hi, I'm running containers/zones on Solaris 10: SunOS be2900 5.10 Generic_118833-33 sun4u sparc SUNW,Netra-T12 zoneadm list -vc gives: ID NAME STATUS PATH 0 global running / 1 bvsmapp01 running /zones/bvsmapp01 2... (3 Replies)
Discussion started by: jabberwocky
3 Replies

3. Solaris

Solaris 8 Containers

While installing a Solaris 8 zone to a Solaris container I received this message. Anyone have this problem? Patchadd is terminating. Postprocess: Applying p2v module S31_fix_net Postprocess: Applying p2v module S32_fix_nfs Postprocess: Applying p2v module S33_fix_vfstab ... (1 Reply)
Discussion started by: cornsnap
1 Replies

4. Solaris

difference between zones and containers

Hi Expects, Can broadly explain difference between Zones and containers. (4 Replies)
Discussion started by: Rajesh_Apple
4 Replies

5. Red Hat

Looking for equivalent of Solaris containers/zones in RHEL7 Linux

Hi, I come from a legacy Solaris background with lots of experience with Solaris Containers/zones that we use for network and process isolation from each other. Currently we have a RHEL7 Linux VM running on VMWare, but we would like to segment that VM with some form of containers and achieve... (1 Reply)
Discussion started by: ckmehta
1 Replies
SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)			 systemd-machine-id-commit.service		      SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)

NAME
systemd-machine-id-commit.service - Commit a transient machine ID to disk SYNOPSIS
systemd-machine-id-commit.service DESCRIPTION
systemd-machine-id-commit.service is an early boot service responsible for committing transient /etc/machine-id files to a writable disk file system. See machine-id(5) for more information about machine IDs. This service is started after local-fs.target in case /etc/machine-id is a mount point of its own (usually from a memory file system such as "tmpfs") and /etc is writable. The service will invoke systemd-machine-id-setup --commit, which writes the current transient machine ID to disk and unmount the /etc/machine-id file in a race-free manner to ensure that file is always valid and accessible for other processes. See systemd-machine-id-setup(1) for details. The main use case of this service are systems where /etc/machine-id is read-only and initially not initialized. In this case, the system manager will generate a transient machine ID file on a memory file system, and mount it over /etc/machine-id, during the early boot phase. This service is then invoked in a later boot phase, as soon as /etc has been remounted writable and the ID may thus be committed to disk to make it permanent. SEE ALSO
systemd(1), systemd-machine-id-setup(1), machine-id(5), systemd-firstboot(1) systemd 237 SYSTEMD-MACHINE-ID-COMMIT.SERVICE(8)
All times are GMT -4. The time now is 01:24 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy