08-22-2014
The tnsping is not currently available in the machine, I wonder if we are allowed to use it.
5 More Discussions You Might Find Interesting
1. IP Networking
Ok, here at work, we have Windows computers which login into a MS domain server.
Some of us also have Linux boxes which get a ip address
from the dhcp server. We can see other boxes and see the internet until about 1 week ago.
Now, we still get a ip address but can't see anything within our... (3 Replies)
Discussion started by: natter
3 Replies
2. UNIX for Dummies Questions & Answers
what is the difference in running oracle database on solaris and linux operating system (3 Replies)
Discussion started by: ganga
3 Replies
3. IP Networking
We have set-up a FTP server on a Linux machine, which sits behind a firewall. Most users outside our firewall can access it, but one user in particular cannot. I assume it has something to do with their firewall rules. It appears that they can connect with no problem but the server does not grant... (1 Reply)
Discussion started by: Breen
1 Replies
4. AIX
What are we doing ?
1) We ftp a PDF file to Oracle Directory which is on AIX server, using Business Object Server. The ftp account we use is prmtftdv. The oracle directory is owned by "oracle" account on aix. The default file permission is 640.
2) We are trying to read the PDF file using oracle... (1 Reply)
Discussion started by: ssatyaranga
1 Replies
5. Shell Programming and Scripting
Hello, I am very new to Scripting. I am having a Kornshell Script below for connecting to Oracle database. But getting an error while executing it.
#!/bin/ksh
ssh -X root@192.168.2.127 <perimuka>
sleep 5
su - oracle
sqlplus <mraghunandanan>/<peri123> <<eof
Can anyone tell what is wrong... (3 Replies)
Discussion started by: mraghunandanan
3 Replies
LEARN ABOUT X11R4
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)