Sponsored Content
Full Discussion: Automatic system recovery?
Operating Systems HP-UX Automatic system recovery? Post 74152 by blowtorch on Wednesday 8th of June 2005 05:50:35 AM
Old 06-08-2005
I seriously doubt if any automated process will be doing this. Looks like someone else prefers HP's make. Smilie
 

8 More Discussions You Might Find Interesting

1. AIX

make a recovery CD/DVD - system has no writable devices

Hi, Has anyone please got some advise as to how I can make a CD/DVD on an AIX 5.3 system so that it can be fully recoverd just by inserting the backed up system. The system that I need to recover has no writable devices, not even a tape drive (it wasn't specified by me btw). I am trying to... (0 Replies)
Discussion started by: stevek007
0 Replies

2. AIX

System recovery

Hi everyone I'm green AIX user or rather beginner (light green). Unfortunately I have to restore my system + data from scratch (things happen) and make it up and running. I've never done it before. Can someone of you provide me with link/procedure/instruction how to do it? Now I know only:... (3 Replies)
Discussion started by: fraydey
3 Replies

3. UNIX for Advanced & Expert Users

Data Recovery from file system overwritten with LVM.

Hey peeps, Here is somethin u might find interestin.... Is it possible to recover data from a partition which used to be an ext3 file sytem with some nice forgotten backups, which now is an lvm partion containg root partition of another OS. :) I couldn't create any mess better than this, can... (2 Replies)
Discussion started by: squid04
2 Replies

4. UNIX for Advanced & Expert Users

linux system recovery after overriding connect() by "ld.so.preload"

dear fellows; i have used ld.so.preload file to override connect() function, dynamic library overriding, it did worked really fine ...... but i went on to struck in a situation ... within the overrided connect() i have used printf once to see IP and Port to whom the connect request is being... (1 Reply)
Discussion started by: mzeeshan
1 Replies

5. UNIX for Advanced & Expert Users

fsck.gfs2 outputs "RG recovery impossible; I can't fix this file system"

I have a CentOS release 5.2 (Final)host running kernel 2.6.18-92.el5 with at raid 10 that had two mirrored drives fail. The drives were re-inserted and now the raid shows healthy (for now). I tried to mount but got an Input/output error. I then attempted a fsck: fsck.gfs2 -y /dev/vg_01/uss_vol... (0 Replies)
Discussion started by: king_hippo
0 Replies

6. Shell Programming and Scripting

Script for Automatic Backup System

Hi Guys/ULF, Good day! Can anyone help me on how to create a program which will be used for our backup process and that will run automatically say every 30th day of the Month. Below is the given command to perform a backup process among all nodes/servers within the same cluster. ns cluster... (2 Replies)
Discussion started by: rymnd_12345
2 Replies

7. HP-UX

System not responding and Automatic process kill

Hi All, One of our servers stopped responding , unable to take any logins into it, the response is almost nil...later it resumed Also during this time one of our application processes which was costly on memory got killed..is it an OOM kill? Would like to know to know how to avoid such... (4 Replies)
Discussion started by: baanprog
4 Replies

8. SCO

Need Help With System Recovery After HD Errors

Last week our legacy SCO OpenServer 5.0.6 server started showing "panic" errors about bad blocks/sectors on hard drive. I ran the badtrack command which fully checked the disk, and it identified 2 LBA sectors as bad, and it was unable to recover some of the data. Apparently the lost data had... (29 Replies)
Discussion started by: spock9458
29 Replies
make(3erl)						     Erlang Module Definition							make(3erl)

NAME
make - A Make Utility for Erlang DESCRIPTION
The module make provides a set of functions similar to the UNIX type Make functions. EXPORTS
all() -> up_to_date | error all(Options) -> up_to_date | error Types Options = [Option] Option = noexec | load | netload | <compiler option> This function first looks in the current working directory for a file named Emakefile (see below) specifying the set of modules to compile and the compile options to use. If no such file is found, the set of modules to compile defaults to all modules in the cur- rent working directory. Traversing the set of modules, it then recompiles every module for which at least one of the following conditions apply: * there is no object file, or * the source file has been modified since it was last compiled, or, * an include file has been modified since the source file was last compiled. As a side effect, the function prints the name of each module it tries to compile. If compilation fails for a module, the make pro- cedure stops and error is returned. Options is a list of make- and compiler options. The following make options exist: * noexec No execution mode. Just prints the name of each module that needs to be compiled. * load Load mode. Loads all recompiled modules. * netload Net load mode. Loads all recompiled modules an all known nodes. All items in Options that are not make options are assumed to be compiler options and are passed as-is to compile:file/2 . Options defaults to [] . files(ModFiles) -> up_to_date | error files(ModFiles, Options) -> up_to_date | error Types ModFiles = [Module | File] Module = atom() File = string() Options = [Option] Option = noexec | load | netload | <compiler option> files/1,2 does exactly the same thing as all/0,1 but for the specified ModFiles , which is a list of module or file names. The file extension .erl may be omitted. The Emakefile (if it exists) in the current directory is searched for compiler options for each module. If a given module does not exist in Emakefile or if Emakefile does not exist, the module is still compiled. EMAKEFILE
make:all/0,1 and make:files/1,2 looks in the current working directory for a file named Emakefile . If it exists, Emakefile should contain elements like this: Modules. {Modules,Options}. Modules is an atom or a list of atoms. It can be * a module name, e.g. file1 * a module name in another directory, e.g. ../foo/file3 * a set of modules specified with a wildcards, e.g. 'file*' * a wildcard indicating all modules in current directory, i.e. '*' * a list of any of the above, e.g. ['file*','../foo/file3','File4'] Options is a list of compiler options. Emakefile is read from top to bottom. If a module matches more than one entry, the first match is valid. For example, the following Emake- file means that file1 shall be compiled with the options [debug_info,{i,"../foo"}] , while all other files in the current directory shall be compiled with only the debug_info flag. {'file1',[debug_info,{i,"../foo"}]}. {'*',[debug_info]}. Ericsson AB tools 2.6.6.3 make(3erl)
All times are GMT -4. The time now is 02:36 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy