05-10-2015
I just done slice in zone. Now zone can boot up. But ssh service not running. When i run command svcs, it's said command not found. How to add?
I need to mount manually disk. How to add in service so i can mount auto when OS boot up? Just like rc.local in linux.
Last edited by mzainal; 05-10-2015 at 10:31 PM..
Reason: New issue.
9 More Discussions You Might Find Interesting
1. Solaris
Hello,
I am attempting to install a newly configured Solaris 9 zone using the flash archive image provided on the sun website. Each time I run the install I get a failure during the Postprocess: Creating mount points. Following is the log:
Log File: /var/tmp/s9-zone.install.25457.log... (0 Replies)
Discussion started by: brialt1
0 Replies
2. Solaris
1. i read that VxFS (3.x) installed on a solaris 8 will not work on a branded zone. fair enough, but what is the impact of having the packages installed when the flarcreate is done? will the container fail to boot with those packages installed?
2. NTP client and server doesnt work on branded... (11 Replies)
Discussion started by: frustin
11 Replies
3. Solaris
Dear all,
we are trying to install a Solaris10 Branded Zone on a Solaris 11 Express system getting this message:
***The image patch level is downrev for running in a solaris10 branded zone***
The Sparc Solaris 10 system is running Release 11/06 and Patch 119254-70 is installed.
Does the... (0 Replies)
Discussion started by: xunil321
0 Replies
4. Solaris
I have a T5220 running Solaris 10. I have a application that can only run on Solaris 9. I want to build a branded Solaris 9 zone for this application on the Solaris 10 Server.
What steps would I need to accomplish this? (2 Replies)
Discussion started by: soupbone38
2 Replies
5. Solaris
I am trying to create a branded 10 zone on a Solaris 11.1 control domain. I am using a flar image (cpio) from an existing LDOM. Here are the steps taken after flarcreate.
#zonecfg -z <device>
>create -b
>set brand=solaris10
>set zonepath=/zonez/<device>
>set ip-type=exclusive
>add net... (1 Reply)
Discussion started by: aeroforce
1 Replies
6. Solaris
I am trying to get a NFS share on a Solaris 10 branded zone. I have read that this is not possible...but I was hoping someone here could tell me different.
share -F nfs -o ro,anon=0 /dir
This would really surprise me that you cannot do this.
Thanks (2 Replies)
Discussion started by: aeroforce
2 Replies
7. Solaris
All.
I am trying to create a 10 branded zone on a Sol 11.1 T5. The Global is using IPMP...so aggregating is out of the question. Has anyone successfully created a branded zone with IPMP? If they have can you please show me the steps you took to get this to run.
Thanks (4 Replies)
Discussion started by: aeroforce
4 Replies
8. Solaris
I am planning to do solaris 11 global zone patching having solaris 10 branded zone. I have a doubts on step 8 specially
Can someone clear my step 8 doubts or if anything wrong between step 1 to step 9 please correct that also as I have pretty good idea about Step 10 mean patching in solaris 10... (2 Replies)
Discussion started by: amity
2 Replies
9. Solaris
So I started with following the example on the omnios page for bhyve (sorry, I can't provide the link because I'm a post shy of the 5 to give a URL):
And found that in the end I was able to create a running bhyve zone, but accessing it via zlogin results in a blank console. I've tried Debian 9... (14 Replies)
Discussion started by: stratacast1
14 Replies
LEARN ABOUT V7
systemd-machine-id-commit.service
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)