09-13-2007
First thing to do is work out a strategy for backing your machine up. So if it gets zapped by lightening you can buy another machine and be back up and running within a couple of hours.
6 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Could someone recommend a good book? Regarding Unix and Mac os X? I know the OS is new, but Unix ain't.
I would like to know more about setting up the webserver on my machine. All the HTML works fine, it's just when i try to execute a cgi, php or a pl script.. :( I have tried and tried to... (2 Replies)
Discussion started by: Chojin
2 Replies
2. UNIX Desktop Questions & Answers
ehe may i know what are the difference between Unix & Linux, and what are the advantages of having Unix as well as disadvantages of having Unix or if u dun mind i am dumb do pls tell me what are the advantages as well as the disadvantages of having linux as well. thanks (1 Reply)
Discussion started by: cybertechmkteo
1 Replies
3. UNIX Desktop Questions & Answers
Are the Terminal commands used in Mac OS 10.1.3 the same as those found on a real Unix system? if they are, what book would you recommend as a terminal refferance guide?
I already have 'The Missing Manual' by O'Reilly, but there ain't much in terms of managing the system via the terminal :(
... (9 Replies)
Discussion started by: LAdesign
9 Replies
4. OS X (Apple)
:confused: = :mad: = :eek: = We have the answear ;) (1 Reply)
Discussion started by: i[c]e
1 Replies
5. Shell Programming and Scripting
Hi
What is the syntax for if statement using && and || operator?
if && ] ||
here its giving me an error to this if statement
any suggestion?? (2 Replies)
Discussion started by: Avi
2 Replies
6. UNIX for Dummies Questions & Answers
Hi!
I wanted to simplify my bash prompt, so I edited my etc/bashrc file. I thought this was the file that would override any other env files. When I opened it, I saw that the way it was setup was not what my prompt looked like, although I forget exactly what was there. But i edited it the way I... (1 Reply)
Discussion started by: sudon't
1 Replies
LEARN ABOUT SUNOS
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)