rescrog(1) [debian man page]

RESCROG(1)						      General Commands Manual							RESCROG(1)

NAME

       rescrog -- change something, make it different

SYNOPSIS

       /etc/rescrog [system|service] [direction]

DESCRIPTION

       rescrog assumes the future basis of a system or service is dependent on the analysis of bit patterns found on the system device.  It deter-
       mines the logical next-best bit pattern to yield the new system or service.  This avoids the necessity of distribution tapes.

       Alterations are made by slight pseudo-random permutations by recursive approximation based on the theory of the Towers of Saigon, where the
       Oriental Guard could never play Ring-toss twice on the same day.

       rescrog's  default  direction  is  future  (except for DoD-installed systems, where the default is past).  The first argument tells rescrog
       whether to perform its actions on the specified system or network service.  It is best to rescrog servers before clients in order to  avoid
       out-of-phase recovery errors.

FILES

       /eunuchs
       /dev/javu
       /etc/etc

SEE ALSO

       punt(1), spewtab(5), rescrogd(8)

BUGS

       rescrog cannot distinguish between bugs and features.

       Interruption while rescrogging can cause diddle-damage.

       Repeated rescrogs done too quickly will lead to advanced technology beyond our comprehension.

																	RESCROG(1)

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)