12-04-2012
I used to migrate to a new haredware.
You need to do it manually.
From top of my head, you need the following checklist.
1. /etc is important which has most of configuration files such as hosts,network info, dns,mail,applications startup scripts so you need to back up and copy each files to new hardware.
2. crontab files : /var/spool/cron
3. home directories : /export/home
4. root profile
5. kernal values
6. Package list
Cheers,
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
Figured this would be a good a place (well more apropriate) to ask this ... What considerations are necesary to port a script from one system to another?
The below link is a script that I'm currently working on at work. The work system is a SCO box and I'm slowly becoming familar... (1 Reply)
Discussion started by: Cameron
1 Replies
2. Programming
I have ported a c program to solaris.
When I run , it gives me segmentation fault error at line :-
memcpy ((char *)a_string ,(char *)0, MAX_READ ) ;
originally this was in reliant unix as :-
memcpy ( a_string , 0 , MAX_READ ) ;
Can somebody help me about this ? (1 Reply)
Discussion started by: suds19
1 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
i wanted to port some HP-UX code to linux. can anybody point to some documents or resources that would help me in doing the porting..
thanks in advance
Arun Prakash (0 Replies)
Discussion started by: arunprakash
0 Replies
4. Programming
I m sorry if this is the wrong place to post this. I m going to do a project on porting tools in unix platform. Can any one give me further suggestions and resources for this topic "Porting tools". Thanks in advance (5 Replies)
Discussion started by: veeru554
5 Replies
5. UNIX for Advanced & Expert Users
I want to know what are the design considerations to be taken into account. when porting a socket project from Unix platform to another ...... (10 Replies)
Discussion started by: areef4u
10 Replies
6. Linux
helo,
i m porting HP-UX socket application to Linux SSL-socket application.
I have use htonl() in HP-UX.
so when i use it in Linux, data transf is not done and application become soem time crashed.
now when i remove htonl() in linux, then i got data but it will not proper order or some data may... (1 Reply)
Discussion started by: amitpansuria
1 Replies
7. HP-UX
I am trying to port to HP-UX 11i v3 system an application in C++ language written for a Tru64 Unix V5.
I am trying to execute on HP-UX 11i v3 a Makefile written for
Tru64 Unix V5 with this code:
$(TARGET_MORE): $(DEPEND_FILE) $(SOURCE_MORE.cc) $(LIBS)
@for i in $(TARGET_MORE); do \
... (1 Reply)
Discussion started by: angeloberardi
1 Replies
8. AIX
I am orignally a VC++ programmer, this is the my post in UNIX form.
I have an existing source code, that was developed in old HP-UX system, the objective is to make it work on new AIX system.
It does'nt appear that AIX has the necessary libraries or even run the application if its... (0 Replies)
Discussion started by: maverick786us
0 Replies
9. Solaris
Hi folk,
I have this hardware faunty message, but dont know which hardware is this ? can you guide me ?
--------------- ------------------------------------ -------------- ---------
TIME EVENT-ID MSG-ID SEVERITY
---------------... (9 Replies)
Discussion started by: dehetoxic
9 Replies
CRON(8) System Manager's Manual CRON(8)
NAME
cron - daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-l load_avg] [-n]
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. The -n option
changes this default behavior causing it to run in the foreground. This can be useful when starting it out of init.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if
time has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
PAM Access Control
On SUSE LINUX systems, crond now supports access control with PAM - see pam(8). A PAM configuration file for crond is installed in
/etc/pam.d/crond . crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files.
Naturally this is not relevant if cron was built to use syslog(3).
CAVEATS
In this version of cron, /etc/crontab must not be writable by any user other than root. No crontab files may be links, or linked to by any
other file. No crontab files may be executable, or be writable by any user other than their owner.
SEE ALSO
crontab(1), crontab(5), pam(8)
AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 10 January 1996" CRON(8)