Re: Pipeline Production Problems

[Chris Albertson <chrisalbertson90278@yahoo.com>]

> Is there a way to get communication with a Windows 98 computer
> restarted
> without rebooting the linux machine?

Ideally the best fix would be to program the pipelines so that
they checkpoint their work and can be killed and will re-start
where they left off.  This could be as simple as writting the
filenames already processed to a file and then skipping filenames
in theis file when it starts.  (If I were the programmer it would
likey all be DBMS based. 

One other Idea might be to suck all the files off the Windows box
as the first step, then if Windows hangs no big deal, you have the
files

OK direct answer to the question:

Almost certainly it is not the re-boot of the linux OS itself that
fixes the problem but the fact the re-booting runs some scripts at
shutdwon and restart times.  These scripts can be run manually.
The trick is to figure out what to run.

On a Linux or any UNIX System V system what happens durring re-boot
ultimatly controlled by the file /etc/inittab but don't mess with that
file.  All it really does is point the process to the "correct"
directory, (either /etc/rc3.d or /etc/rc5.d)  On shutdown everyrhing
in /etc/rcN.d that looks like xxx.Knn gets run and on boot up
everything
like /etc/rcN.d/xxxx.S?? gets run in numeric order based on ?? 
(thats "S" for "Startup" and "K" for "Kill".  When the boot
process "sees" a file called xxx.Snn it runs the script with
a parameter "start". 

Maybe that's not so clear but it doesn't
matter.  All of the scripts whoes names are like /etc/init.d/xxx
take parameters like "start", "stop", "restart" and "status"

So..  If you want to re-start your FTP server without a re-boot
try typing "ftp restart" or "ftp stop; ftp start".  As far as FTP
is concerned this is the same as a re-boot.

Clearly "ftp" is the wrong script to run for your prolem.  Your
task is to figure out which is the correct one.  It is different
depending of your exact system redhat vs. suse vs, Solaris as these
scripts are all written by whoever put your system together.

The above to the "blessed" canonnical method.  You may also find
that something totally ad-hoc works like doing an "unmount" and
then a mount of the hung file system.  Possibly preceeded by
a "kill <process-id>" of any hung pipeling process. But the above
"/etc/init.d/xxx.S?? stop; /etc/init.dxxx.S?? start" will do
that same thing as a reboot for the "xxx" subsystem.



=====
Chris Albertson
  Home:   310-376-1029  chrisalbertson90278@yahoo.com
  Cell:   310-990-7550
  Office: 310-336-5189  Christopher.J.Albertson@aero.org
  KG6OMK

__________________________________
Do you Yahoo!?
The New Yahoo! Shopping - with improved product search
http://shopping.yahoo.com