Using LOM port to start boot solaris 10 Post: 302180554

10 More Discussions You Might Find Interesting

1. Solaris

nfsd won't start at boot up

Hi Inexplicably, nfsd no longer starts automatically on our Sun boxes running Solaris 9, so that 'automount' no longer functions automatically. The problem first manifested itself when we could not access files on any of the nfs automounted directories in our LAN after one of the servers (say...

2. Solaris

SUN SOLARIS boot: start daemons

Hi, I have a problem on a Solaris 9 server! After a restart some daemons don't start and I have to start them manually! I thing that everything is ok in the /sbin/rc3 script! And if I run manually the "/etc/init.d/xxx start" the services start without problem. I didn't find anything in...

3. Solaris

solaris boot problem boot error loading interpreter(misc/krtld)

When I installed the SOLARIS 10 OS first time, the desktop would not start up, this was because of network setup. Reinstalled worked. After a week due to some problem I had to reinstall OS, installation went fine and but when i reboot I get this error. cannot find mis/krtld boot error loading...

4. SuSE

Start Asterisk at boot?

Hello, I am running a SuSe 9.3 server. That have Asterisk. Asterisk are working fine/perfect. But what I want to do is to make it start up at boot. When I have started the computer can I type: sudo /root/Asterisk-1.0.8/Asterisk And it goes of. No problem. But I want it to do that by itself...

5. HP-UX

PXE boot port issue

Hi,all: I want to boot an IA unix box from network, I am sure I set the DHCP and boot server, but it still failed ! It says : Client MAC Address: 00 18 FE 28 91 82 .....- PXE-E16: Valid PXE offer not received. Load of Core LAN Gb A failed: Not Found I use the nettl command to trace the UDP...

6. Infrastructure Monitoring

Solaris 10 - starting snmpdx at boot time on a port other than 161

Hi All, Can we start the snmpdx on another port at boot time on solaris 10 instead of the default 161 port? What is the configuration file to set this? We can make it run in a different port after the system boots up by using snmpdx -p port_number This requirement is because i have an...

7. Solaris

Solaris x86 installation using jumpstart does not local boot ( boot from hdd)

I am trying to install Solaris x86 using the Jumpstart server. I run the add_install_client command with appropriate options, and reboot my x86 Target box. The installation starts fine and unattended. After the installation completes and the target goes for a re-boot, it does not boot from the HDD...

8. Red Hat

NFS does not start during boot process

Hello, I am facing some issues during boot process of rhel 6.2 It takes too long time (~10 min) for the node to come up... The boot process stuck while it trying to start NFS and does not continue until timeout. In the boot.log file i see Starting NFS quotas: Cannot register service:...

9. Red Hat

iptables does not start on boot

Hello, I have an issue with iptables. The rules are already configured in /etc/sysconfig/iptables but when i reboot the node the service is not running or at least i can't see my rules. Below the configuration i did to start the service during boot. # chkconfig --list iptables iptables...

10. AIX

Process on a specified Terminal and Socket Port does not start

Hi, I new to AIX, and I have been using Rocket UniData in it. I had to set up a Process for Data Exchange by assigning a unique Terminal and a Socket Port to that process. I ran the process for the first time and it was successful and after use I stopped the process. Now when I want to run it...

LEARN ABOUT PHP

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)