Home Accessibility Courses Twitter The Mouth Facebook Resources Site Map About Us Contact
For 2023 - we are now fully retired from IT training.
We have made many, many friends over 25 years of teaching about Python, Tcl, Perl, PHP, Lua, Java, C and C++ - and MySQL, Linux and Solaris/SunOS too. Our training notes are now very much out of date, but due to upward compatability most of our examples remain operational and even relevant ad you are welcome to make us if them "as seen" and at your own risk.

Lisa and I (Graham) now live in what was our training centre in Melksham - happy to meet with former delegates here - but do check ahead before coming round. We are far from inactive - rather, enjoying the times that we are retired but still healthy enough in mind and body to be active!

I am also active in many other area and still look after a lot of web sites - you can find an index ((here))
Forking in Perl, then communicating between processes
Interprocess Communication example from a Well House Consultants training course
More on Interprocess Communication [link]

This example is described in the following article(s):
   • Perl - doing several things at the same time - [link]

Source code: fdem Module: P223

=head1 Forking in Perl

The fork function in Perl splits the current process
into two, duplicating all variables into each of the
new processes.

One of the new processes is known as the "parent" -
this is the original process (under the original process
id), and the other is know as the "child", which has
a new process id. You can tell them apart by checking
the value returned by fork - in the child it returns a zero,
but in the parent it returns the process id of the newly
created child.

Based on the returned value, the parent and the child can
go off to perform different tasks. You should take care
in your code, though, to ensure that you add an exit call
if appropriate to avoid one dropping through into the other
at run time.

Parent and child can alert each other via signals (not
illustrated in this simple example) or writing messages
to and from each other via a pipe. If you open a pipe
before you fork, with two file handles, you can then
(after forking) write to one of the file handles in the
parent and read in the child, and / or write to a file
handle in the child and read at the parent.

This use of pipes to communicate between processes allows
the processes to wait for one another (syncronise) when
each of their individual tasks reaches a strategic point.


print "hello\n";

$abc = 123;
$ppid = $$;

pipe(FHX, FHY);

if (!($pid = fork())) {
        print ("$abc ... Child of $ppid is $$\n");
        sleep 5;
        print "yawn\n";
        sleep 5;
        print "yawn\n";
        print FHY ("OK, Mum, I'm done\n");
        print "Child completed\n";
print ("$abc ... Parent is $ppid with child $pid\n");
sleep 4;
print "yeah\n";
sleep 4;
print "yeah\n";
$woch = <FHX>;
print ("Always sitting at the school gate!\n");
print $woch;


Dorothy:csr1 grahamellis$ perl fdem
123 ... Parent is 414 with child 415
123 ... Child of 414 is 415
Child completed
Always sitting at the school gate!
OK, Mum, I'm done
Dorothy:csr1 grahamellis$

Learn about this subject
This module and example are covered on our public Perl Extra course. If you have a group of three or more trainees who need to learn the subject, we can also arrange a private or on site course for you.

Books covering this topic
Yes. We have over 700 books in our library. Books covering Perl are listed here and when you've selected a relevant book we'll link you on to Amazon to order.

Other Examples
This example comes from our "Interprocess Communication" training module. You'll find a description of the topic and some other closely related examples on the "Interprocess Communication" module index page.

Full description of the source code
You can learn more about this example on the training courses listed on this page, on which you'll be given a full set of training notes.

Many other training modules are available for download (for limited use) from our download centre under an Open Training Notes License.

Other resources
• Our Solutions centre provides a number of longer technical articles.
• Our Opentalk forum archive provides a question and answer centre.
The Horse's mouth provides a daily tip or thought.
• Further resources are available via the resources centre.
• All of these resources can be searched through through our search engine
• And there's a global index here.

Purpose of this website
This is a sample program, class demonstration or answer from a training course. It's main purpose is to provide an after-course service to customers who have attended our public private or on site courses, but the examples are made generally available under conditions described below.

Web site author
This web site is written and maintained by Well House Consultants.

Conditions of use
Past attendees on our training courses are welcome to use individual examples in the course of their programming, but must check the examples they use to ensure that they are suitable for their job. Remember that some of our examples show you how not to do things - check in your notes. Well House Consultants take no responsibility for the suitability of these example programs to customer's needs.

This program is copyright Well House Consultants Ltd. You are forbidden from using it for running your own training courses without our prior written permission. See our page on courseware provision for more details.

Any of our images within this code may NOT be reused on a public URL without our prior permission. For Bona Fide personal use, we will often grant you permission provided that you provide a link back. Commercial use on a website will incur a license fee for each image used - details on request.

You can Add a comment or ranking to this page

© WELL HOUSE CONSULTANTS LTD., 2023: 48 Spa Road • Melksham, Wiltshire • United Kingdom • SN12 7NY
PH: 01144 1225 708225 • EMAIL: info@wellho.net • WEB: http://www.wellho.net • SKYPE: wellho

PAGE: http://www.wellho.net/resources/ex.php • PAGE BUILT: Sun Oct 11 14:50:09 2020 • BUILD SYSTEM: JelliaJamb