Backup Considerations#

if [ -f /opt/pi/adm/pistop.sh ] ; then
cd /opt/pi/adm
ksh pistop.sh
fi
Next, set the owner, group, and permissions on these files to match the other files in this
directory (check the setting on your system):
root> chown bin /sbin/init.d/PI*
root> chgrp bin /sbin/init.d/PI*
root> chmod 755 /sbin/init.d/PI*
Then, you'll need to set the links in the rc#.d directories. Make sure that the S## number on
the startup file is higher than the S## number for inet, and that the K## number for the kill
file is lower than the K## number for inet (in both directories).
root> ln -s /sbin/init.d/PI /sbin/rc3.d/S96PI
root> ln -s /sbin/init.d/PI /sbin/rc2.d/K04PI
root> ln -s /sbin/init.d/PI /sbin/rc0.d/K04PI
Verify that these files have the same owner, group, and permissions as other startup files in
those directories.
Finally, test your scripts before you restart your machine. To stop PI:
root> sh /sbin/rc2.d/K04PI stop
Verify that PI processes shut down.
root> sh /sbin/rc3.d/S96PI start
Verify that PI starts properly.
If there is any problem with stopping or restarting PI, remove the links in the /sbin/rc#.d
directories until you've debugged and fixed the problems. The files in the /sbin/init.d
directory will not affect your system as long as there are no links in the /sbin/rc#.d#
if [ -f /opt/pi/adm/pistop.sh ] ; then
cd /opt/pi/adm
ksh pistop.sh
fi
Next, set the owner, group, and permissions on these files to match the other files in this
directory (check the setting on your system):
root> chown bin /sbin/init.d/PI*
root> chgrp bin /sbin/init.d/PI*
root> chmod 755 /sbin/init.d/PI*
Then, you'll need to set the links in the rc#.d directories. Make sure that the S## number on
the startup file is higher than the S## number for inet, and that the K## number for the kill
file is lower than the K## number for inet (in both directories).
root> ln -s /sbin/init.d/PI /sbin/rc3.d/S96PI
root> ln -s /sbin/init.d/PI /sbin/rc2.d/K04PI
root> ln -s /sbin/init.d/PI /sbin/rc0.d/K04PI
Verify that these files have the same owner, group, and permissions as other startup files in
those directories.
Finally, test your scripts before you restart your machine. To stop PI:
root> sh /sbin/rc2.d/K04PI stop
Verify that PI processes shut down.
root> sh /sbin/rc3.d/S96PI start
Verify that PI starts properly.
If there is any problem with stopping or restarting PI, remove the links in the /sbin/rc#.d
directories until you've debugged and fixed the problems. The files in the /sbin/init.d
directory will not affect your system as long as there are no links in the /sbin/rc#.d#
if [ -f /opt/pi/adm/pistop.sh ] ; then
cd /opt/pi/adm
ksh pistop.sh
fi
Next, set the owner, group, and permissions on these files to match the other files in this
directory (check the setting on your system):
root> chown bin /sbin/init.d/PI*
root> chgrp bin /sbin/init.d/PI*
root> chmod 755 /sbin/init.d/PI*
Then, you'll need to set the links in the rc#.d directories. Make sure that the S## number on
the startup file is higher than the S## number for inet, and that the K## number for the kill
file is lower than the K## number for inet (in both directories).
root> ln -s /sbin/init.d/PI /sbin/rc3.d/S96PI
root> ln -s /sbin/init.d/PI /sbin/rc2.d/K04PI
root> ln -s /sbin/init.d/PI /sbin/rc0.d/K04PI
Verify that these files have the same owner, group, and permissions as other startup files in
those directories.
Finally, test your scripts before you restart your machine. To stop PI:
root> sh /sbin/rc2.d/K04PI stop
Verify that PI processes shut down.
root> sh /sbin/rc3.d/S96PI start
Verify that PI starts properly.
If there is any problem with stopping or restarting PI, remove the links in the /sbin/rc#.d
directories until you've debugged and fixed the problems. The files in the /sbin/init.d
directory will not affect your system as long as there are no links in the /sbin/rc#.d#
if [ -f /opt/pi/adm/pistop.sh ] ; then
cd /opt/pi/adm
ksh pistop.sh
fi
Next, set the owner, group, and permissions on these files to match the other files in this
directory (check the setting on your system):
root> chown bin /sbin/init.d/PI*
root> chgrp bin /sbin/init.d/PI*
root> chmod 755 /sbin/init.d/PI*
Then, you'll need to set the links in the rc#.d directories. Make sure that the S## number on
the startup file is higher than the S## number for inet, and that the K## number for the kill
file is lower than the K## number for inet (in both directories).
root> ln -s /sbin/init.d/PI /sbin/rc3.d/S96PI
root> ln -s /sbin/init.d/PI /sbin/rc2.d/K04PI
root> ln -s /sbin/init.d/PI /sbin/rc0.d/K04PI
Verify that these files have the same owner, group, and permissions as other startup files in
those directories.
Finally, test your scripts before you restart your machine. To stop PI:
root> sh /sbin/rc2.d/K04PI stop
Verify that PI processes shut down.
root> sh /sbin/rc3.d/S96PI start
Verify that PI starts properly.
If there is any problem with stopping or restarting PI, remove the links in the /sbin/rc#.d
directories until you've debugged and fixed the problems. The files in the /sbin/init.d
directory will not affect your system as long as there are no links in the /sbin/rc#.d#
if [ -f /opt/pi/adm/pistop.sh ] ; then
cd /opt/pi/adm
ksh pistop.sh
fi
Next, set the owner, group, and permissions on these files to match the other files in this
directory (check the setting on your system):
root> chown bin /sbin/init.d/PI*
root> chgrp bin /sbin/init.d/PI*
root> chmod 755 /sbin/init.d/PI*
Then, you'll need to set the links in the rc#.d directories. Make sure that the S## number on
the startup file is higher than the S## number for inet, and that the K## number for the kill
file is lower than the K## number for inet (in both directories).
root> ln -s /sbin/init.d/PI /sbin/rc3.d/S96PI
root> ln -s /sbin/init.d/PI /sbin/rc2.d/K04PI
root> ln -s /sbin/init.d/PI /sbin/rc0.d/K04PI
Verify that these files have the same owner, group, and permissions as other startup files in
those directories.
Finally, test your scripts before you restart your machine. To stop PI:
root> sh /sbin/rc2.d/K04PI stop
Verify that PI processes shut down.
root> sh /sbin/rc3.d/S96PI start
Verify that PI starts properly.
If there is any problem with stopping or restarting PI, remove the links in the /sbin/rc#.d
directories until you've debugged and fixed the problems. The files in the /sbin/init.d
directory will not affect your system as long as there are no links in the /sbin/rc#.d#
if [ -f /opt/pi/adm/pistop.sh ] ; then
cd /opt/pi/adm
ksh pistop.sh
fi
Next, set the owner, group, and permissions on these files to match the other files in this
directory (check the setting on your system):
root> chown bin /sbin/init.d/PI*
root> chgrp bin /sbin/init.d/PI*
root> chmod 755 /sbin/init.d/PI*
Then, you'll need to set the links in the rc#.d directories. Make sure that the S## number on
the startup file is higher than the S## number for inet, and that the K## number for the kill
file is lower than the K## number for inet (in both directories).
root> ln -s /sbin/init.d/PI /sbin/rc3.d/S96PI
root> ln -s /sbin/init.d/PI /sbin/rc2.d/K04PI
root> ln -s /sbin/init.d/PI /sbin/rc0.d/K04PI
Verify that these files have the same owner, group, and permissions as other startup files in
those directories.
Finally, test your scripts before you restart your machine. To stop PI:
root> sh /sbin/rc2.d/K04PI stop
Verify that PI processes shut down.
root> sh /sbin/rc3.d/S96PI start
Verify that PI starts properly.
If there is any problem with stopping or restarting PI, remove the links in the /sbin/rc#.d
directories until you've debugged and fixed the problems. The files in the /sbin/init.d
directory will not affect your system as long as there are no links in the /sbin/rc#.d#
if [ -f /opt/pi/adm/pistop.sh ] ; then
cd /opt/pi/adm
ksh pistop.sh
fi
Next, set the owner, group, and permissions on these files to match the other files in this
directory (check the setting on your system):
root> chown bin /sbin/init.d/PI*
root> chgrp bin /sbin/init.d/PI*
root> chmod 755 /sbin/init.d/PI*
Then, you'll need to set the links in the rc#.d directories. Make sure that the S## number on
the startup file is higher than the S## number for inet, and that the K## number for the kill
file is lower than the K## number for inet (in both directories).
root> ln -s /sbin/init.d/PI /sbin/rc3.d/S96PI
root> ln -s /sbin/init.d/PI /sbin/rc2.d/K04PI
root> ln -s /sbin/init.d/PI /sbin/rc0.d/K04PI
Verify that these files have the same owner, group, and permissions as other startup files in
those directories.
Finally, test your scripts before you restart your machine. To stop PI:
root> sh /sbin/rc2.d/K04PI stop
Verify that PI processes shut down.
root> sh /sbin/rc3.d/S96PI start
Verify that PI starts properly.
If there is any problem with stopping or restarting PI, remove the links in the /sbin/rc#.d
directories until you've debugged and fixed the problems. The files in the /sbin/init.d
directory will not affect your system as long as there are no links in the /sbin/rc#.d#
if [ -f /opt/pi/adm/pistop.sh ] ; then
cd /opt/pi/adm
ksh pistop.sh
fi
Next, set the owner, group, and permissions on these files to match the other files in this
directory (check the setting on your system):
root> chown bin /sbin/init.d/PI*
root> chgrp bin /sbin/init.d/PI*
root> chmod 755 /sbin/init.d/PI*
Then, you'll need to set the links in the rc#.d directories. Make sure that the S## number on
the startup file is higher than the S## number for inet, and that the K## number for the kill
file is lower than the K## number for inet (in both directories).
root> ln -s /sbin/init.d/PI /sbin/rc3.d/S96PI
root> ln -s /sbin/init.d/PI /sbin/rc2.d/K04PI
root> ln -s /sbin/init.d/PI /sbin/rc0.d/K04PI
Verify that these files have the same owner, group, and permissions as other startup files in
those directories.
Finally, test your scripts before you restart your machine. To stop PI:
root> sh /sbin/rc2.d/K04PI stop
Verify that PI processes shut down.
root> sh /sbin/rc3.d/S96PI start
Verify that PI starts properly.
If there is any problem with stopping or restarting PI, remove the links in the /sbin/rc#.d
directories until you've debugged and fixed the problems. The files in the /sbin/init.d
directory will not affect your system as long as there are no links in the /sbin/rc#.d#
if [ -f /opt/pi/adm/pistop.sh ] ; then
cd /opt/pi/adm
ksh pistop.sh
fi
Next, set the owner, group, and permissions on these files to match the other files in this
directory (check the setting on your system):
root> chown bin /sbin/init.d/PI*
root> chgrp bin /sbin/init.d/PI*
root> chmod 755 /sbin/init.d/PI*
Then, you'll need to set the links in the rc#.d directories. Make sure that the S## number on
the startup file is higher than the S## number for inet, and that the K## number for the kill
file is lower than the K## number for inet (in both directories).
root> ln -s /sbin/init.d/PI /sbin/rc3.d/S96PI
root> ln -s /sbin/init.d/PI /sbin/rc2.d/K04PI
root> ln -s /sbin/init.d/PI /sbin/rc0.d/K04PI
Verify that these files have the same owner, group, and permissions as other startup files in
those directories.
Finally, test your scripts before you restart your machine. To stop PI:
root> sh /sbin/rc2.d/K04PI stop
Verify that PI processes shut down.
root> sh /sbin/rc3.d/S96PI start
Verify that PI starts properly.
If there is any problem with stopping or restarting PI, remove the links in the /sbin/rc#.d
directories until you've debugged and fixed the problems. The files in the /sbin/init.d
directory will not affect your system as long as there are no links in the /sbin/rc#.dBackup
Considerations
t PI Interfaces ...............................................................................................

Backup Considerations
t PI Interfaces ...............................................................................................

Backup Considerations
t PI Interfaces ...............................................................................................

Backup Considerations
t PI Interfaces ...............................................................................................

Backup Considerations
t PI Interfaces ...............................................................................................

Backup Considerations
t PI Interfaces ...............................................................................................

Backup Considerations
t PI Interfaces ...............................................................................................

Backup Considerations
t PI Interfaces ...............................................................................................

Backup Considerations
t PI Interfaces ...............................................................................................