Sponsored Content
Top Forums UNIX for Beginners Questions & Answers BMW GT1 DIS - SCO 5.0 and Oracle 7 Root HDD Clone - IBM T30 Post 303032070 by bmw635 on Sunday 10th of March 2019 06:16:20 PM
Old 03-10-2019
Thanks VBE for the quick reply . The issue is there is no way to get to command line during the startup or shutdown process. To startup all you do is power the IBM T30 laptop with all interface connected and it goes thru the SCO and Oracle 7 startup and the BMW GT1 menu appears. To shutdown all you do is once you end all diagnostic back to Main menu , you enter Ctrl+Alt+F1 and type "shut" at the logon promot. It then goes thru the shutdown process and powers off the T30.

Is there a way to safely interrupt the startup and go into single user mode and do a DD command. There is no time the system even goes to command line .

rgds
 

8 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

SCO UNIX HDD full backup

HI ALL, I need to backup HDD with SCO UNIX. I need to have a full functionaly backup of this hard disk. Does anybody have any tool or subsription how to do it. I tried some SW, but after when I tried to use this copy of my original disk "can not find a root directory". Thanks in advance. (1 Reply)
Discussion started by: jardas
1 Replies

2. SCO

SCO 5.0.7 and Serial ATA HDD question

Hi guys, I have this quick question , is it posible to isntall SCO 5.0.7 on a serial ATA and if it is can you tell me how or maybe a website that has some info about this. I'm not using any raid, just one HDD. Thanks a lot (0 Replies)
Discussion started by: josramon
0 Replies

3. UNIX for Advanced & Expert Users

SCO 5.0.5 installation on 80GB HDD

Hello, I have a P4, 2.4GHz, 256MB ASROCK mainboard: I am trying to install sco 5.0.5 on an 80gb hdd IDE . I have tried the following techniques: 1. using the updated wd btld image- no success 2. defbootstr biosgeom 3. use interactive divvy, make adjustments using dkinit/dparam during... (0 Replies)
Discussion started by: pude
0 Replies

4. SCO

Sco 5.06 How To Mount A 2nd Hdd Help Help!!!!

Hi guys, I have this problem , One of our client's hdd went down and we cannot boot up the machine , I've installed a new hdd with a fresh copy of SCO 5.0.6 same as the one in the old HDD, i think the data still good in the old HDD. My question!!! How can i access the data from the fresh... (4 Replies)
Discussion started by: josramon
4 Replies

5. Ubuntu

Can't successfully clone an HDD in Ubuntu, please help

Hi guys, I am total newbie to Linux / Ubuntu but trying it to solve the problem I have. I have an OKI printer with bad HDD and trying to clone one from the same HDD from working printer. Board it goes on has a Fiery chipset and system used is Linux based / related - to the best of my knowlege. I... (12 Replies)
Discussion started by: Unlimitedbt
12 Replies

6. HP-UX

How to clone a 382-workstations hdd?

Hi there, I got a pretty old HP 382 workstation, and the hdd is pretty LOUD ... ;) So I thought I clone it to an much quiter one. I tried this: - removed the loud hdd - connected it to an system running knoppix 7.0.4 (hdd is recognized with UFS filesystem; Clonezilla couldn't handle the... (9 Replies)
Discussion started by: pelegrine
9 Replies

7. SCO

Dd (raw) image of SCO 5.0.6 mount as second hdd

Hi all I have read about mounting crashed HDD from a sco system in this forum. However this I received an image on raw format of the crashed system that was using an IDE HDD. Which method should I mount my image? IDE scsi or USB? The image is stores in an external connected through USB . Also... (4 Replies)
Discussion started by: OrangeKenny
4 Replies

8. AIX

IBM AIX Internal HDD vs SAN HDD and Oracle

Hi Folks, I am facing an issue with the performance. P4 with 1 processor and 16 GB RAM and SAN HDD = Oracle report takes 25 minutes P5 with 2 processors and 16 GB RAM internall HDD with LPAR = Oracle Report takes 1 hour 15 minutes ( please note I have assigned all the max processors and... (7 Replies)
Discussion started by: filosophizer
7 Replies
esmd(1M)																  esmd(1M)

NAME
esmd - Essential Services Monitor (ESM) Daemon SYNOPSIS
retry_seconds] DESCRIPTION
The Essential Services Monitor (ESM) daemon, maintains the availability of essential system daemons by automatically restarting them if they terminate. The ESM daemon monitors the Event Manager daemon, The ESM daemon is started by the init process when the system is ini- tialized to run level 2 and continues to run until the system is shut down or returned to single user mode. Only one instance of can run at a time. Configuration information is sent to the ESM daemon by a control program, which is run at key points in the startup and shutdown proce- dures. As startup or shutdown progresses, the control program updates the ESM state file, The control program then signals the daemon to reconfigure itself. On startup, state transitions occur after has started. On shutdown, transitions occur after each of these monitored daemons has termi- nated. After each transition, the ESM daemon determines which of the monitored daemons should be running and adjusts its monitoring activ- ities accordingly. The ESM daemon reports all state change information, including notice of failures and restarts, through the system logging daemon, syslogd. Messages are displayed on the system console during periods when syslogd is not running. See syslogd(1M) for more information. If the ESM daemon fails to restart a monitored daemon, it reports the error by posting a high priority message through syslogd, and makes no further restart attempts. The system administrator should investigate the problem and restart the failed daemon. The ESM daemon peri- odically attempts to resume monitoring of the daemon, and posts an informational message when it succeeds. If the monitored daemon fails again once monitoring has resumed, the ESM daemon again attempts to restart it. The ESM daemon can be forced to restart a failed daemon by sending a SIGHUP signal to the process. If there is a need to temporarily disable the ESM daemon for test purposes, in order to prevent the monitored daemons from being restarted automatically, send a SIGSTOP signal to the process. To reactivate the ESM daemon, send a SIGCONT signal to the process. The ESM daemon should never be disabled on a production system. If the ESM daemon is terminated unexpectedly, it is restarted automatically by init. Options The command recognizes the following options: Limit the priority of any syslog messages posted by the ESM daemon to "alert." If this option is not specified, posts an "emergency" message if it cannot restart a failed daemon. A message may be sent to all users currently logged in to the system. The option should only be used if the system administrator is actively monitoring syslogd messages. Specify the interval between attempts to begin monitoring a daemon that has failed, and which has been unable to restart automatically. The default period is 30 seconds. Specifying a period of zero disables retrying. Notes To use the start options, you must add them to the startup command in the file. The daemon reports any invalid start options with a single generic message through syslogd. Restrictions The daemon terminates with an error message if it is started by any process other than init. The /sbin/init.d/esm program is intended to be run by the system startup and shutdown process and should not be run from the command line. Only one instance of can run at a time. RETURN VALUE
The following exit values are returned: 0 (Zero) Successful completion. not 0 An error occurred. FILES
Executable file Configuration control script Initialization process control file dispatched by boot init Monitoring state file Receives esmd status messages AUTHOR
was developed by Hewlett Packard Company. SEE ALSO
Commands kill(1), evmd(1M), init(1M), syslogd(1M). Files inittab(4). esmd(1M)
All times are GMT -4. The time now is 03:02 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy