EmbLogic » Project 03: Client Server Communication using Linux and IPC

Socket programming based Home Automation

Raghu Nath — Fri, 09 Dec 2016 12:04:21 +0000

The main aim of this project is to implement Socket programming using Embedded linux based boards using beagle bone as server and pc as a client. The entire electrical system like home appliances are interfaced to Server (Beagle bone black) using relay electronics system.There will be authentication system for accessing the server like user id and password which will be provided by user through client.The enhancement of authentication system will be based on shell scripts.The user can control any appliance at any time from linux terminal.The user will run application based code which is interfaced to the Client program by providing basic authentication. An acknowledgement is also provided to user to monitor the status of the Appliance by server.The protocol used here is TCP (Transmission Control protocol)Client Server model, The Client will send the request to server.The Server process takes a request from the client. After getting a request from the client, this process will perform the required processing, gather the requested information, and send it to the requester client. The user will provide some input data by command line arguments to application Client.The beagle bone Server application will be automated after initial boot power-on with the help of bashRC Scripting.

client-server program using AF_UNIX

Jyoti Singh — Sun, 03 Apr 2016 15:37:46 +0000

RCS file: header.h,v
Working file: header.h
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is the base header file for the Project
—————————-
revision 1.1 locked by: root;
date: 2016/04/03 15:35:50; author: root; state: Exp;
Initial revision
=============================================================================RCS file: req_client.c,v
Working file: req_client.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
This is the requesting client …sending request to the server.
Has socket() to creat the socket.
Has the connect() to connect to the server.
—————————-
revision 1.2 locked by: root;
date: 2015/06/18 09:04:22; author: root; state: Exp; lines: +7 -1
client has entered some data …into the buffer…and send that buffer through the socket file discriptor.
write()is used to wrote data
—————————-
revision 1.1
date: 2015/06/18 07:20:19; author: root; state: Exp;
Initial revision
=============================================================================RCS file: srvr.c,v
Working file: srvr.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
this is my server program for socket programming.
this includes socket()to create the socket and returns file discriptor.
then there is bind call to name the socket created.
—————————-
revision 1.4 locked by: root;
date: 2016/01/29 08:41:59; author: root; state: Exp; lines: +36 -25
Used remove instead of unlink
used strncpy insted of strcpy to maintain the portability.
—————————-
revision 1.3
date: 2015/06/18 09:05:59; author: root; state: Exp; lines: +16 -2
the data accepted by the accept()call .
read and print the data
—————————-
revision 1.2
date: 2015/06/18 06:37:40; author: root; state: Exp; lines: +27 -7
Created listen() to listen the accept and given backlog value as 10.that is listen queue size
created accept() to accept the request of the client
—————————-
revision 1.1
date: 2015/06/18 05:55:53; author: root; state: Exp;
Initial revision
=============================================================================

Multiple Client server program using Thread,Pipes and signals

Jyoti Singh — Sun, 03 Apr 2016 15:33:30 +0000

RCS file: ./header.h,v
Working file: ./header.h
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is the header file
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 18:20:29; author: root; state: Exp;
Initial revision
=============================================================================RCS file: server.c,v
Working file: server.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
This is the server
—————————-
revision 1.2 locked by: root;
date: 2015/09/01 09:01:10; author: root; state: Exp; lines: +12 -4
Included comments
—————————-
revision 1.1
date: 2015/08/11 18:20:38; author: root; state: Exp;
Initial revision
=============================================================================

Multiple Client-server Program using threads and Message Queue

Jyoti Singh — Wed, 30 Mar 2016 17:30:30 +0000

RCS file: ./header.h,v
Working file: ./header.h
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is the Base header file.
—————————-
revision 1.1 locked by: root;
date: 2016/03/30 17:27:32; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./req_client1.c,v
Working file: ./req_client1.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is req_client1
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 18:07:35; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./req_client2.c,v
Working file: ./req_client2.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
Req_client2
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 18:12:14; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./req_client3.c,v
Working file: ./req_client3.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
req_client3
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 18:07:49; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./request.h,v
Working file: ./request.h
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This header contains requesting structure.
—————————-
revision 1.1 locked by: root;
date: 2016/03/30 17:29:41; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./srvr.c,v
Working file: ./srvr.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
srvr
—————————-
revision 1.2 locked by: root;
date: 2015/09/01 08:53:00; author: root; state: Exp; lines: +7 -4
included comments
—————————-
revision 1.1
date: 2015/08/11 18:07:54; author: root; state: Exp;
Initial revision
=============================================================================

Multiple client server program using Shared Memory

Jyoti Singh — Wed, 30 Mar 2016 17:19:11 +0000

RCS file: ./header.h,v
Working file: ./header.h
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is Base Header file for Multiple client server program using shared memory.
—————————-
revision 1.1 locked by: root;
date: 2016/03/30 17:16:27; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./req_add.c,v
Working file: ./req_add.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
req_add
—————————-
revision 1.2 locked by: root;
date: 2015/09/20 07:41:00; author: root; state: Exp; lines: +7 -4
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/11 17:57:03; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./req_sub.c,v
Working file: ./req_sub.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
req_sub
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:57:08; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./req_mul.c,v
Working file: ./req_mul.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
req_mul
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:57:13; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./server.c,v
Working file: ./server.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
server
—————————-
revision 1.2 locked by: root;
date: 2015/09/01 08:16:17; author: root; state: Exp; lines: +8 -2
Included comment.
—————————-
revision 1.1
date: 2015/08/11 17:57:30; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_add.c,v
Working file: ./proc_add.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
proc_ad
—————————-
revision 1.2 locked by: root;
date: 2015/09/01 08:16:00; author: root; state: Exp; lines: +4 -0
Included comment
—————————-
revision 1.1
date: 2015/08/11 17:57:17; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_sub.c,v
Working file: ./proc_sub.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
proc_sub
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:57:21; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_mul.c,v
Working file: ./proc_mul.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
proc_mul
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:57:26; author: root; state: Exp;
Initial revision
=============================================================================

Multiple Client-server Program using Message Queue?

Jyoti Singh — Mon, 28 Mar 2016 16:58:12 +0000

RCS file: ./header.h,v
Working file: ./header.h
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
This is Base Header file for this project.
—————————-
revision 1.2 locked by: root;
date: 2016/03/28 16:51:10; author: root; state: Exp; lines: +3 -6
*** empty log message ***
—————————-
revision 1.1
date: 2016/03/28 16:50:39; author: root; state: Exp;
Initial revision
=========================================================================RCS file: ./req_add.c,v
Working file: ./req_add.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is req_add
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:52:09; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./req_sub.c,v
Working file: ./req_sub.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
req-sub
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:52:16; author: root; state: Exp;
Initial revision
=============================================================================

====RCS file: ./req_mul.c,v
Working file: ./req_mul.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
rwq_mul
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:52:21; author: root; state: Exp;
Initial revision
==========================================================RCS file: ./server.c,v
Working file: ./server.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
server
—————————-
revision 1.2 locked by: root;
date: 2015/09/01 07:41:36; author: root; state: Exp; lines: +3 -3
Included comments.
—————————-
revision 1.1
date: 2015/08/11 17:52:57; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_add.c,v
Working file: ./proc_add.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
proc_add
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:52:31; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_sub.c,v
Working file: ./proc_sub.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
proc_sub
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:52:45; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_mul.c,v
Working file: ./proc_mul.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
proc_mul
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:52:51; author: root; state: Exp;
Initial revision
=============================================================================

===================

Multiple Client-server Program using FIFO and Semaphore

Jyoti Singh — Sun, 27 Mar 2016 14:37:00 +0000

RCS file: ./header.h,v
Working file: ./header.h
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is the base header file for this multiple client server program.
where There are three client named req_add ,req_sub,req_mul and server and
three processing client proc_add,proc_sub,proc_mul.
in this req_client send request to server then server passes to processing client for
further processing.
to provide the synchorinazation symphore are used.
—————————-
revision 1.1 locked by: root;
date: 2016/03/27 14:32:26; author: root; state: Exp;
Initial revision
===============================RCS file: ./req_add.c,v
Working file: ./req_add.c
head: 1.3
branch:
locks: strict
root: 1.3
access list:
symbolic names:
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
This is the req_add
—————————-
revision 1.3 locked by: root;
date: 2015/09/01 07:18:22; author: root; state: Exp; lines: +29 -2
included comments.
—————————-
revision 1.2
date: 2015/09/01 06:29:42; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/11 17:21:48; author: root; state: Exp;
Initial revision
===========================================================================RCS file: ./req_sub.c,v
Working file: ./req_sub.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is the req_sub
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:21:55; author: root; state: Exp;
Initial revision
====================================================================RCS file: ./req_mul.c,v
Working file: ./req_mul.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is the req_mul
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:22:02; author: root; state: Exp;
Initial revision
=====================================================================RCS file: ./server.c,v
Working file: ./server.c
head: 1.3
branch:
locks: strict
root: 1.3
access list:
symbolic names:
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
This is the server
—————————-
revision 1.3 locked by: root;
date: 2015/10/23 07:20:14; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.2
date: 2015/09/01 07:18:37; author: root; state: Exp; lines: +25 -5
included comments.
—————————-
revision 1.1
date: 2015/08/11 17:22:42; author: root; state: Exp;
Initial revision
=============================================================================
========RCS file: ./proc_add.c,v
Working file: ./proc_add.c
head: 1.2
branch:
locks: strict
root: 1.2
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
This is the proc_add
—————————-
revision 1.2 locked by: root;
date: 2015/09/01 07:18:31; author: root; state: Exp; lines: +2 -0
included comments.
—————————-
revision 1.1
date: 2015/08/11 17:22:11; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_sub.c,v
Working file: ./proc_sub.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is the proc_sub
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:22:24; author: root; state: Exp;
Initial revision
============================================================================RCS file: ./proc_mul.c,v
Working file: ./proc_mul.c
head: 1.1
branch:
locks: strict
root: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
This is the proc_mul
—————————-
revision 1.1 locked by: root;
date: 2015/08/11 17:22:32; author: root; state: Exp;
Initial revision
=============================================================================
=

=========
==
==============================================

Multi-Tasking Operating System

Jyoti Singh — Sat, 26 Mar 2016 16:23:17 +0000

Multitasking OS is the one that can simultaneously interleave execution of more then one process.

They are of two types :
>>cooperative multitasking : in this process don’t stop running until it voluntary decide to do so . This is known as yielding.

>>Preemptive multitasking : in this scheduler decides when a process to cease running and a new process to begin running. This involuntary suspending of running program is called preemptive. This maintains that no process monopolize the resource.

Multiple Client – server Program using PIPE and Signal.

Jyoti Singh — Sat, 26 Mar 2016 15:50:56 +0000

PIPE to mean connecting a data flow from one process to another.PIPE is passed (a pointer to) an array of two integer file descriptors.It fills the array with two new file descriptors and returns a zero. On failure, it returns -1.The two file descriptors returned are connected in a special way. Any data written to file_descriptor[1] can be read back from file_descriptor[0]. The data is processed in a first in, first out basis, usually abbreviated to FIFO.

Fd[0] = read

fd[1] = write

CODE:

RCS file: ./header.h,v
Working file: ./header.h
head: 1.3
branch:
locks: strict
root: 1.3
access list:
symbolic names:
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
This is the base header file for the project 3_client server ipc technique using pipe and signals
—————————-
revision 1.3 locked by: root;
date: 2015/08/04 06:05:54; author: root; state: Exp; lines: +1 -0
Included color.h
—————————-
revision 1.2
date: 2015/08/03 18:37:10; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/03 17:53:18; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./req_add.c,v
Working file: ./req_add.c
head: 1.10
branch:
locks: strict
root: 1.10
access list:
symbolic names:
keyword substitution: kv
total revisions: 10; selected revisions: 10
description:
This is Requesting client named adder
—————————-
revision 1.10 locked by: root;
date: 2015/08/31 18:06:46; author: root; state: Exp; lines: +7 -0
Included comment
—————————-
revision 1.9
date: 2015/08/04 07:09:47; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.8
date: 2015/08/04 07:07:31; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.7
date: 2015/08/04 06:59:09; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.6
date: 2015/08/04 06:56:03; author: root; state: Exp; lines: +4 -4
*** empty log message ***
—————————-
revision 1.5
date: 2015/08/04 06:06:04; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.4
date: 2015/08/03 18:38:24; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.3
date: 2015/08/03 18:14:47; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.2
date: 2015/08/03 18:12:15; author: root; state: Exp; lines: +4 -4
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/03 17:53:18; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./req_sub.c,v
Working file: ./req_sub.c
head: 1.8
branch:
locks: strict
root: 1.8
access list:
symbolic names:
keyword substitution: kv
total revisions: 8; selected revisions: 8
description:
This is the subtractor req_client
—————————-
revision 1.8 locked by: root;
date: 2015/08/04 07:09:48; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.7
date: 2015/08/04 07:02:15; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.6
date: 2015/08/04 06:59:10; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.5
date: 2015/08/04 06:56:05; author: root; state: Exp; lines: +5 -5
*** empty log message ***
—————————-
revision 1.4
date: 2015/08/03 18:38:26; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.3
date: 2015/08/03 18:14:48; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.2
date: 2015/08/03 18:12:16; author: root; state: Exp; lines: +4 -4
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/03 17:53:18; author: root; state: Exp;
Initial revision
============================================================================RCS file: ./req_mul.c,v
Working file: ./req_mul.c
head: 1.8
branch:
locks: strict
root: 1.8
access list:
symbolic names:
keyword substitution: kv
total revisions: 8; selected revisions: 8
description:
This is the mul req_client
—————————-
revision 1.8 locked by: root;
date: 2015/08/04 07:09:49; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.7
date: 2015/08/04 07:07:32; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.6
date: 2015/08/04 06:59:11; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.5
date: 2015/08/04 06:56:06; author: root; state: Exp; lines: +4 -5
*** empty log message ***
—————————-
revision 1.4
date: 2015/08/03 18:38:27; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.3
date: 2015/08/03 18:14:49; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.2
date: 2015/08/03 18:12:17; author: root; state: Exp; lines: +4 -4
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/03 17:53:18; author: root; state: Exp;
Initial revision
=============================================================================
=
RCS file: ./server.c,v
Working file: ./server.c
head: 1.4
branch:
locks: strict
root: 1.4
access list:
symbolic names:
keyword substitution: kv
total revisions: 4; selected revisions: 4
description:
—————————-
revision 1.4 locked by: root;
date: 2015/08/31 18:06:59; author: root; state: Exp; lines: +7 -0
Included comment
—————————-
revision 1.3
date: 2015/08/04 07:09:52; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.2
date: 2015/08/03 18:37:11; author: root; state: Exp; lines: +6 -6
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/03 18:34:43; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_add.c,v
Working file: ./proc_add.c
head: 1.8
branch:
locks: strict
root: 1.8
access list:
symbolic names:
keyword substitution: kv
total revisions: 8; selected revisions: 8
description:
This is proc_client for adder
—————————-
revision 1.8 locked by: root;
date: 2015/08/31 18:06:54; author: root; state: Exp; lines: +3 -0
Included comment
—————————-
revision 1.7
date: 2015/08/04 07:09:49; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.6
date: 2015/08/04 07:07:33; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.5
date: 2015/08/04 06:56:06; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.4
date: 2015/08/03 18:18:14; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.3
date: 2015/08/03 18:14:49; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.2
date: 2015/08/03 18:12:18; author: root; state: Exp; lines: +2 -1
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/03 17:53:18; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_sub.c,v
Working file: ./proc_sub.c
head: 1.7
branch:
locks: strict
root: 1.7
access list:
symbolic names:
keyword substitution: kv
total revisions: 7; selected revisions: 7
description:
This is the proc_client for subtractor
—————————-
revision 1.7 locked by: root;
date: 2015/08/04 07:09:50; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.6
date: 2015/08/04 07:07:33; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.5
date: 2015/08/04 06:56:07; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.4
date: 2015/08/03 18:18:15; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.3
date: 2015/08/03 18:14:50; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.2
date: 2015/08/03 18:12:18; author: root; state: Exp; lines: +2 -1
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/03 17:53:18; author: root; state: Exp;
Initial revision
=============================================================================RCS file: ./proc_mul.c,v
Working file: ./proc_mul.c
head: 1.7
branch:
locks: strict
root: 1.7
access list:
symbolic names:
keyword substitution: kv
total revisions: 7; selected revisions: 7
description:
This is the processing client for the multiplier
—————————-
revision 1.7 locked by: root;
date: 2015/08/04 07:09:51; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.6
date: 2015/08/04 07:07:33; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.5
date: 2015/08/04 06:56:08; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.4
date: 2015/08/03 18:18:16; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.3
date: 2015/08/03 18:14:50; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.2
date: 2015/08/03 18:12:19; author: root; state: Exp; lines: +2 -1
*** empty log message ***
—————————-
revision 1.1
date: 2015/08/03 17:53:18; author: root; state: Exp;
Initial revision
=============================================================================

Single Client Server And Single Thread Communication Using FIFO With Use The Shell Script

Gurbhej Gill — Thu, 25 Feb 2016 22:09:59 +0000

RCS file: header.h,v
Working file: header.h
head: 1.15
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 15; selected revisions: 15
description:
In file all include header files related this project.
—————————-
revision 1.15
date: 2016/02/25 06:18:43; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.14
date: 2016/02/25 06:15:12; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.13
date: 2016/02/24 09:13:23; author: root; state: Exp; lines: +1 -0
In file include a semaphore.h header files .
—————————-
revision 1.12
date: 2016/02/24 08:44:38; author: root; state: Exp; lines: +0 -1
In file remove a prototype second thread hendler function
—————————-
revision 1.11
date: 2016/02/23 16:38:46; author: root; state: Exp; lines: +1 -0
In file decalre a prototypes another handler function this handler in server in handler function return type void.
—————————-
revision 1.10
date: 2016/02/23 11:41:03; author: root; state: Exp; lines: +2 -1
In file declare a prototypes of signal handler is return type is chany void not a void .
void *.
—————————-
revision 1.9
date: 2016/02/23 11:39:06; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.8
date: 2016/02/23 10:30:18; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.7
date: 2016/02/23 10:28:18; author: root; state: Exp; lines: +1 -0
In file now include a signal.h header file before declare a prototype signal handler functions.
—————————-
revision 1.6
date: 2016/02/23 10:18:53; author: root; state: Exp; lines: +1 -0
In file include a new a header file signal.h
—————————-
revision 1.5
date: 2016/02/21 08:40:55; author: root; state: Exp; lines: +1 -1
In file check how working
—————————-
revision 1.4
date: 2016/02/21 08:08:10; author: root; state: Exp; lines: +1 -1
In file decalre a prototypes in will agrument pass in thread is type void *
—————————-
revision 1.3
date: 2016/02/21 07:49:17; author: root; state: Exp; lines: +2 -0
In file decalre a prototypes of processing client thread .
—————————-
revision 1.2
date: 2016/02/20 05:54:00; author: root; state: Exp; lines: +3 -0
In file include a header files.
—————————-
revision 1.1
date: 2016/02/20 05:33:07; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: request.h,v
Working file: request.h
head: 1.2
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
In file assgin a data in structure then open a fifo in write only mode then write the data .
—————————-
revision 1.2
date: 2016/02/23 10:19:14; author: root; state: Exp; lines: +1 -0
In file in structure member decalre a pid variable in int type.
—————————-
revision 1.1
date: 2016/02/20 05:34:10; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: processing_client.c,v
Working file: processing_client.c
head: 1.30
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 30; selected revisions: 30
description:
In file this is processing client thread this call from the server in file return and pasing argument is void *
then decalre a struct operations type a variable then open a fifo in read only mode then read the data all.
—————————-
revision 1.30
date: 2016/02/25 06:27:07; author: root; state: Exp; lines: +2 -1
*** empty log message ***
—————————-
revision 1.18
date: 2016/02/24 11:00:55; author: root; state: Exp; lines: +11 -1
In fioe fd=open(“fifo”,O_RDONLY);

In file calling a sem_wait and sem_post and display this values.
—————————-
revision 1.17
date: 2016/02/24 09:59:46; author: root; state: Exp; lines: +1 -2
*** empty log message ***
—————————-
revision 1.16
date: 2016/02/24 09:28:27; author: root; state: Exp; lines: +2 -0
In file this thread starting call to the sem_wait beacuse now this thread for read for the working and any another
thread don’t interupted so then this thread complete the work then call to the sem_post beacuse this thread works are complted and out of critical section this thread .
—————————-
revision 1.15
date: 2016/02/24 09:17:08; author: root; state: Exp; lines: +1 -1
In file removes a sum bugs.
—————————-
revision 1.14
date: 2016/02/24 09:16:27; author: root; state: Exp; lines: +0 -1
*** empty log message ***
—————————-
revision 1.13
date: 2016/02/24 09:15:13; author: root; state: Exp; lines: +2 -2
In file decalre a properly sem
sem_t type sem2 variable .
—————————-
revision 1.12
date: 2016/02/24 08:45:16; author: root; state: Exp; lines: +5 -3
In file fretch a semaphore a variable void * type then this variable type cast in sem_init type and before signals methmethod are falied in thread because thread to main thread don’t send a signals always because thread id we do not can find
in main_thread so that reason is falied
—————————-
revision 1.11
date: 2016/02/23 16:44:20; author: root; state: Exp; lines: +1 -0
decalre a pthread_t type id variable
—————————-
revision 1.10
date: 2016/02/23 16:39:52; author: root; state: Exp; lines: +4 -1
In file frecth the value in thread id void * type then type cast of pthread_id data type then pthread_kill using the
SIGINT signal send the the main thread .
—————————-
revision 1.9
date: 2016/02/21 09:48:10; author: root; state: Exp; lines: +1 -1
In file some corrections in code.
—————————-
revision 1.8
date: 2016/02/21 09:42:17; author: root; state: Exp; lines: +7 -1
In file a get a data then solve the result means two variable add and in store a result variable then open a fifo
in write only mode then write the result.
—————————-
revision 1.7
date: 2016/02/21 09:18:11; author: root; state: Exp; lines: +3 -3
In file remvoe the sleep in 3 second
—————————-
revision 1.6
date: 2016/02/21 08:41:18; author: root; state: Exp; lines: +2 -2
In file pass a argument in a void * variable
—————————-
revision 1.5
date: 2016/02/21 08:29:01; author: root; state: Exp; lines: +3 -0
*** empty log message ***
—————————-
revision 1.4
date: 2016/02/21 08:15:14; author: root; state: Exp; lines: +1 -1
In file frecth a agrument is void * c
—————————-
revision 1.3
date: 2016/02/21 08:14:13; author: root; state: Exp; lines: +2 -1
*** empty log message ***
—————————-
revision 1.2
date: 2016/02/21 08:08:58; author: root; state: Exp; lines: +1 -1
In file fretch the argument thread_id varable void *
—————————-
revision 1.1
date: 2016/02/21 07:40:25; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: request_client.c,v
Working file: request_client.c
head: 1.13
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 13; selected revisions: 13
description:
In file assgin a data in structure then open a fifo in write only mode then write the data .
—————————-
revision 1.13
date: 2016/02/23 11:42:19; author: root; state: Exp; lines: +1 -1
In file signal handler change a return type only void not a void *.
—————————-
revision 1.12
date: 2016/02/23 11:39:07; author: root; state: Exp; lines: +2 -2
*** empty log message ***
—————————-
revision 1.11
date: 2016/02/23 10:23:23; author: root; state: Exp; lines: +16 -4
In file make a signal handler names functions in file top and in which file calling to that functions and then add a
pause() and when SIGINT signal is genrate then calling to signal handler functions and sleep is removes in file .
—————————-
revision 1.10
date: 2016/02/21 11:34:30; author: root; state: Exp; lines: +1 -0
In file check how working.
—————————-
revision 1.9
date: 2016/02/21 11:24:56; author: root; state: Exp; lines: +2 -1
In file calling to sleep.
—————————-
revision 1.8
date: 2016/02/21 11:23:55; author: root; state: Exp; lines: +2 -2
In file some removes a bugs .
—————————-
revision 1.7
date: 2016/02/21 11:23:10; author: root; state: Exp; lines: +2 -2
In file decarle a result variable .
—————————-
revision 1.6
date: 2016/02/21 11:09:51; author: root; state: Exp; lines: +17 -0
In file open a fifo in read only mode if fd is negative then call to open then read a result if read is failed then
report to read then display the result.
—————————-
revision 1.5
date: 2016/02/20 17:45:12; author: root; state: Exp; lines: +1 -1
In file add a count varable how many bytes write a request_client in fifo then return a count any case count falied then then report it.
—————————-
revision 1.4
date: 2016/02/20 13:17:05; author: root; state: Exp; lines: +1 -0
In file decalre a fd,count variables.
—————————-
revision 1.3
date: 2016/02/20 13:16:15; author: root; state: Exp; lines: +3 -3
In file some removes a bugs
—————————-
revision 1.2
date: 2016/02/20 13:14:12; author: root; state: Exp; lines: +1 -1
In file included request.h file corrections the speling mistake .
—————————-
revision 1.1
date: 2016/02/20 05:34:55; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: server.c,v
Working file: server.c
head: 1.43
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 43; selected revisions: 43
description:
In file decalre a structure variable then check if user allow a permissions then create a fifo then read a structure
then display a structure .
—————————-
revision 1.43
date: 2016/02/25 08:28:56; author: root; state: Exp; lines: +1 -1
In file create a thread semaphore in semaphore a some eshu then resolve this .
—————————-
revision 1.42
date: 2016/02/25 06:25:03; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.41
date: 2016/02/25 06:22:47; author: root; state: Exp; lines: +3 -3
*** empty log message ***
—————————-
revision 1.40
date: 2016/02/25 06:15:14; author: root; state: Exp; lines: +0 -1
*** empty log message ***
—————————-
revision 1.39
date: 2016/02/25 06:13:16; author: root; state: Exp; lines: +2 -5
*** empty log message ***
—————————-
revision 1.38
date: 2016/02/25 05:58:10; author: root; state: Exp; lines: +0 -1
*** empty log message ***
revision 1.37
date: 2016/02/25 05:52:27; author: root; state: Exp; lines: +25 -30
*** empty log message ***
—————————-
revision 1.36
date: 2016/02/24 12:36:19; author: root; state: Exp; lines: +3 -4
*** empty log message ***
—————————-
revision 1.35
date: 2016/02/24 12:30:26; author: root; state: Exp; lines: +44 -39
In file add a some if conditions.
—————————-
revision 1.34
date: 2016/02/24 11:36:48; author: root; state: Exp; lines: +6 -1
*** empty log message ***
—————————-
revision 1.33
date: 2016/02/24 11:04:45; author: root; state: Exp; lines: +10 -4
In file calling a sem_wait and sem_post in 6 times and display the 6 times.
.\
—————————-
revision 1.32
date: 2016/02/24 10:30:02; author: root; state: Exp; lines: +3 -1
*** empty log message ***
—————————-
revision 1.31
date: 2016/02/24 10:08:40; author: root; state: Exp; lines: +2 -5
*** empty log message ***
—————————-
revision 1.30
date: 2016/02/24 10:04:01; author: root; state: Exp; lines: +9 -7
*** empty log message ***
—————————-
revision 1.29
date: 2016/02/24 09:59:50; author: root; state: Exp; lines: +6 -3
*** empty log message ***
—————————-
revision 1.28
date: 2016/02/24 09:31:47; author: root; state: Exp; lines: +3 -2
In file create thread before call to the sem_wait thread beacuse this thread is working of ready any other thread din’t interupted then write a data and then call to sem_post beasue this work is complted this main_thread out of critical
sections.
—————————-
revision 1.27
date: 2016/02/24 09:14:06; author: root; state: Exp; lines: +1 -1
In file remove a some errors.
—————————-
revision 1.26
date: 2016/02/24 08:52:01; author: root; state: Exp; lines: +15 -15
In file create a thread semhaphore a and then add a condtions if any cases falied a so return -1 or any negative value
and report the sem_init then add a sem_wait beause In critial section in thread then thread sem_post call then move
and critical section in main thread
—————————-
revision 1.25
date: 2016/02/23 16:41:47; author: root; state: Exp; lines: +9 -13
In file sleep(3) is system call removes and this replace a in pause and make a signal handler SIGINT signal and this
handler function calling the in server means main thread .
—————————-
revision 1.24
date: 2016/02/23 11:29:29; author: root; state: Exp; lines: +2 -2
In file just checking
—————————-
revision 1.23
date: 2016/02/23 10:26:22; author: root; state: Exp; lines: +29 -2
Im file send a signal send a SIGINT siganl in request client process .
—————————-
revision 1.22
date: 2016/02/21 11:34:48; author: root; state: Exp; lines: +0 -1
In file check how working..
—————————-
revision 1.21
date: 2016/02/21 11:19:41; author: root; state: Exp; lines: +21 -0
In file get a result then open a fifo in write only mode then if fd is no is negative then report the open and out
then write a result if any condition write is failed then report to write .
—————————-
revision 1.20
date: 2016/02/21 10:52:08; author: root; state: Exp; lines: +2 -3
In file add twos sleep in 2-2 sec .
—————————-
revision 1.19
date: 2016/02/21 09:44:06; author: root; state: Exp; lines: +8 -0
In file open a fifo then read only mode then read a result then display the result in server.
—————————-
revision 1.18
date: 2016/02/21 09:26:33; author: root; state: Exp; lines: +1 -0
In file add a sleep in 2 second .
—————————-
revision 1.17
date: 2016/02/21 09:25:17; author: root; state: Exp; lines: +0 -1
In file sleep is removed
—————————-
revision 1.16
date: 2016/02/21 09:18:30; author: root; state: Exp; lines: +2 -2
In file add a sleep in 3 second .
—————————-
revision 1.15
date: 2016/02/21 08:41:43; author: root; state: Exp; lines: +0 -1
/.
—————————-
revision 1.14
date: 2016/02/21 08:16:40; author: root; state: Exp; lines: +1 -0
In file c is decalre variable.
—————————-
revision 1.13
date: 2016/02/21 08:15:39; author: root; state: Exp; lines: +1 -1
In file pass a agrument in thread c
—————————-
revision 1.12
date: 2016/02/21 08:14:14; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.11
date: 2016/02/21 08:12:39; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.10
date: 2016/02/21 08:09:56; author: root; state: Exp; lines: +1 -1
In file pass the argument in thread calling tym in server and before types to chnge a void * varbale .
—————————-
revision 1.9
date: 2016/02/21 08:04:33; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.8
date: 2016/02/21 08:02:35; author: root; state: Exp; lines: +1 -1
In file put the NULL is some error then type cast is void *
—————————-
revision 1.7
date: 2016/02/21 08:01:09; author: root; state: Exp; lines: +1 -1
In file thread calling in agrument is NULL.
—————————-
revision 1.6
date: 2016/02/21 07:54:08; author: root; state: Exp; lines: +1 -1
In file correction the thread_create to chnge pthread_create and give the thread id is reffrence
—————————-
revision 1.5
date: 2016/02/21 07:49:55; author: root; state: Exp; lines: +2 -2
In file declare a thread_id variable this data type of pthread_t
—————————-
revision 1.4
date: 2016/02/21 07:43:08; author: root; state: Exp; lines: +14 -0
In file firstly create a thread then thread created then open a fifo in write only mode then write a the data in fifo.
—————————-
revision 1.3
date: 2016/02/20 17:58:58; author: root; state: Exp; lines: +2 -2
date: 2016/02/20 17:58:58; author: root; state: Exp; lines: +2 -2
In file server how many read a bytes sucessfully then return a no. of bytes store in count if read is failed then reporreport the read call .
—————————-
revision 1.2
date: 2016/02/20 05:54:11; author: root; state: Exp; lines: +3 -1
In file declare a variables .
—————————-
revision 1.1
date: 2016/02/20 05:35:20; author: root; state: Exp;
Initial revision
=============================================================================
(-SHELL SCRIPT-
#! /bin/bash

delete()
{
rm -rf request_client
rm -rf *.o
rm -rf server
}

edit()
{
read -p “do you want a edit further (y or n)” answer

if [ 'y' = $answer ]
then

for file in $(ls *.h,v)
do
co -l $file
done

for file in $(ls *.c,v)
do
co -l $file
done
delete
exit 0
fi

}

execute()
{
read -p “do you want a compile a project” answer

if [ 'y' = $answer ]
then
if ( gcc -c server.c -lpthread)
then
echo “compile is successfull”
else
echo “compile is failed”
edit
fi

if ( gcc -o request_client request_client.c )
then
echo “compile is sucessfull”
else
echo “compile is failed”
edit
fi

if ( gcc -c processing_client.c -lpthread )
then
echo “compile is sucessfull”
else
echo “compile is failed”
edit
fi
else
edit
fi

read -p “do you want a execute this project” answer

if [ 'y' = $answer ]
then
if (gcc -o server server.o processing_client.o -lpthread)
then
./server & ./request_client -lpthread
else
echo “executeable is failed”
edit
fi
else
edit
fi

}

logfile()
{
read -p “do you want a run a logfile” answer
if [ 'y' = $answer ]
then
chmod +x rlog.sh
./rlog.sh
fi
}

for file in $(ls *.h)
do
ci $file
done

for file in $(ls *.c)
do
ci $file
done

for file in $(ls *.h,v)
do
co $file
done

for file in $(ls *.c,v)
do
co $file
done
execute
logfile
edit

SEVER SINGLE CLIENT FIFO AND PIPES WITH USE THE SHELL SCRIPT

Gurbhej Gill — Sun, 07 Feb 2016 19:15:48 +0000

RCS file: header.h,v
Working file: header.h
head: 1.1
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
In file include a all header files realted this project.
—————————-
revision 1.1
date: 2016/02/04 11:32:41; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: request.h,v
Working file: request.h
head: 1.3
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
In file delacare a structure name is struct opreations and decalre a in member variable .
—————————-
revision 1.3
date: 2016/02/04 20:20:28; author: root; state: Exp; lines: +0 -1
In file decalre result varable.
—————————-
revision 1.2
date: 2016/02/04 20:19:24; author: root; state: Exp; lines: +1 -0
*** empty log message ***
—————————-
revision 1.1
date: 2016/02/04 11:33:11; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: processing_client.c,v
Working file: processing_client.c
head: 1.8
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 8; selected revisions: 8
description:
In file a getv the all structure data read the all structure using pipe and then found the result give the sever call to to the write.
—————————-
revision 1.8
date: 2016/02/07 11:01:05; author: root; state: Exp; lines: +2 -0
In file removes the all sleeps.
—————————-
revision 1.7
date: 2016/02/04 19:16:31; author: root; state: Exp; lines: +1 -1
In file display a operator.
—————————-
revision 1.6
date: 2016/02/04 19:14:40; author: root; state: Exp; lines: +1 -1
In file some changing.
—————————-
revision 1.5
date: 2016/02/04 19:12:48; author: root; state: Exp; lines: +4 -1
In file get a display structure in member variable.
—————————-
revision 1.4
date: 2016/02/04 19:07:15; author: root; state: Exp; lines: +1 -0
In file calling sleep in 2 sec.
—————————-
revision 1.3
date: 2016/02/04 19:05:20; author: root; state: Exp; lines: +1 -1
In file now write a result.
—————————-
revision 1.2
date: 2016/02/04 18:50:16; author: root; state: Exp; lines: +1 -0
In file wfd,rfd and result are variables declare.
—————————-
revision 1.1
date: 2016/02/04 13:33:06; author: root; state: Exp;
Initial revision
=============================================================================
RCS file: request_client.c,v
Working file: request_client.c
head: 1.8
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 8; selected revisions: 8
description:
In file declare a struct operations type a variable and all sturcture members in values all assign .
then call to the open and file open the all structure write a in fifo then call to the sleep in 5 sec.
—————————-
revision 1.8
date: 2016/02/07 11:01:44; author: root; state: Exp; lines: +1 -1
In file check the this file write the data or not.
—————————-
revision 1.7
date: 2016/02/04 20:20:54; author: root; state: Exp; lines: +1 -1
In file declare a result varibale and display the result .
—————————-
revision 1.6
date: 2016/02/04 20:19:26; author: root; state: Exp; lines: +7 -9
*** empty log message ***
—————————-
revision 1.5
date: 2016/02/04 20:02:32; author: root; state: Exp; lines: +20 -2
In file get a result of the server and display the result and add a if else condition in a file.
—————————-
revision 1.4
date: 2016/02/04 12:05:34; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.3
date: 2016/02/04 11:49:47; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.2
date: 2016/02/04 11:48:32; author: root; state: Exp; lines: +14 -1
In file add a some checking condtions.
—————————-
revision 1.1
date: 2016/02/04 11:34:07; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: server.c,v
Working file: server.c
head: 1.11
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 11; selected revisions: 11
description:
In file a first one declare a struct operations type a variable then calling to the system call is access and in condtions the fifo file in already avialable or not check the access then if not available the fifo file then call to mkfifo the n create fifo file and then call the open if open file is successfully then call to the read and read the structure in a fifo then all the structure is display in which some condions.
—————————-
revision 1.11
date: 2016/02/07 11:02:37; author: root; state: Exp; lines: +1 -3
In file removes the all sleep.
/.
—————————-
revision 1.10
date: 2016/02/04 20:05:33; author: root; state: Exp; lines: +15 -0
In file get a result to proceesing client and then in sleep 3 sec then give the result of the request client .
—————————-
revision 1.9
date: 2016/02/04 19:16:56; author: root; state: Exp; lines: +1 -1
In file read a result .
—————————-
revision 1.8
date: 2016/02/04 18:55:15; author: root; state: Exp; lines: +3 -3
In file check the working .
—————————-
revision 1.7
date: 2016/02/04 18:51:20; author: root; state: Exp; lines: +2 -0
In file get result to processing client and display a result in file.
—————————-
revision 1.6
date: 2016/02/04 13:34:28; author: root; state: Exp; lines: +25 -5
In file call a first call to the pipe and create a pipe then call to fork and then add a switch statements then execl call and and write a data give the all structure to processing client and then get a result of the processing client .
—————————-
revision 1.5
date: 2016/02/04 12:05:36; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.4
date: 2016/02/04 11:53:18; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.3
date: 2016/02/04 11:52:22; author: root; state: Exp; lines: +1 -1
*** empty log message ***
—————————-
revision 1.2
date: 2016/02/04 11:43:54; author: root; state: Exp; lines: +2 -0
*** empty log message ***
—————————-
revision 1.1
date: 2016/02/04 11:36:18; author: root; state: Exp;
Initial revision
=============================================================================
SHELL SCRIPT

#! /bin/bash

delete()
{
rm -rf server
rm -rf request_client
}

edit()
{
read -p “do you want a edit further (y or n)” answer

if [ 'y' = $answer ]
then

for file in $(ls *.h,v)
do
co -l $file
done

for file in $(ls *.c,v)
do
co -l $file
done
delete
exit 0
fi
}

execute()
{
read -p “do you want a execute script(y or n)” answer

if [ 'y' = $answer ]
then
if (gcc -o server server.c)
then
echo “compailation successfully”
else
echo “compailation is failed”
edit
fi

if (gcc -o request_client request_client.c)
then
echo “compailation successfully”
else
echo “compailation is failed”
edit
fi
if (gcc -o processing_client processing_client.c)
then
echo “compailation successfully”
else
echo “compailation is failed”
edit
fi

else
edit
fi
./server & ./request_client
}

logfile()
{
chmod +x rlog.sh
./rlog.sh
edit
}

for file in $(ls *.h)
do
ci $file
done

for file in $(ls *.c)
do
ci $file
done

for file in $(ls *.h,v)
do
co $file
done

for file in $(ls *.c,v)
do
co $file
done
execute
read
logfile

Project03: Linux System Programming & Client Server Communication

Reena Rani — Sun, 07 Feb 2016 13:08:43 +0000

RCS file: fork.c,v
Working file: fork.c
head: 1.1
branch:
locks: strict
reena: 1.1
access list:
symbolic names:
keyword substitution: kv
total revisions: 1; selected revisions: 1
description:
process duplication for project 03: Inter Process Communication
using fork()
—————————-
revision 1.1 locked by: reena;
date: 2016/02/07 12:58:41; author: reena; state: Exp;
Initial revision
=============================================================================

SEVER MULTIPLE CLIENT USING PIPES WITH USE A SHELL SCRIPT

Gurbhej Gill — Thu, 04 Feb 2016 18:38:52 +0000

RCS file: header.h,v
Working file: header.h
head: 1.2
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 2; selected revisions: 2
description:
In file a include a header files related the this project
—————————-
revision 1.2
date: 2016/01/31 10:28:12; author: root; state: Exp; lines: +0 -8
remove a some statement.
—————————-
revision 1.1
date: 2016/01/31 09:29:28; author: root; state: Exp;
Initial revision
=============================================================================

RCS file: request.h,v
Working file: request.h
head: 1.3
branch:
locks: strict
access list:
symbolic names:
keyword substitution: kv
total revisions: 3; selected revisions: 3
description:
In file a declare structure and in structure a three member variable.
—————————-
revision 1.3
date: 2016/02/04 06:20:17; author: root; state: Exp; lines: +4 -3
*** empty log message ***
—————————-
revision 1.2
date: 2016/02/03 14:13:25; author: root; state: Exp; lines: +5 -1
In file a declare a in structure another member variable.
—————————-
revision 1.1
date: 2016/01/31 09:30:01; author: root; state: Exp;
Initial revision
=============================================================================

SHELL SCRIPT

delete()
{
rm -rf server
rm -rf add_request_client
rm -rf sub_request_client
rm -rf mul_request_client
rm -rf div_request_client
rm -rf add_processing_client
rm -rf sub_processing_client
rm -rf mul_processing_client
rm -rf div_processing_client

}
edit()
{

read -p “do you want a edit further (y or n) :” answer
if [ 'y' = $answer ]
then
for file in $(ls *.h)
do
co -l $file
done

for file in $(ls *.c)
do
co -l $file
done

delete
fi
exit 0
}

execute()
{
read -p “do you want a execute a script :” answer
if [ 'y' = $answer ]
then

if (gcc -o add_request_client add_request_client.c)
then
echo “complations is successfull”
else
echo “complations is failed”
edit
fi

if (gcc -o sub_request_client sub_request_client.c)
then
echo “complations is successfull”
else
echo “complations is failed”
edit
fi
if (gcc -o mul_request_client mul_request_client.c)
then
echo “complations is successfull”
else
echo “complations is failed”
edit
fi

if (gcc -o div_request_client div_request_client.c)
then
echo “complations is successfull”
else
echo “complations is failed”
edit
fi

if (gcc -o add_processing_client add_processing_client.c)
then
echo “complations is successfull”
else
echo “complation is failed”
edit
fi
if (gcc -o sub_processing_client sub_processing_client.c)
then
echo “complations is successfull”
else
echo “complation is failed”
edit
fi
if (gcc -o mul_processing_client mul_processing_client.c)
then
echo “complations is successfull”
else
echo “complation is failed”
edit
fi

if (gcc -o div_processing_client div_processing_client.c)
then
echo “complations is successfull”
else
echo “complation is failed”
edit
fi

if (gcc -o server server.c)
then
echo “complations is successfull”
else
echo “complation is failed”
edit
fi

else
edit
fi

./server
}

logfile()
{
read -p “do you want a run a logfile :” answer

if [ 'y' = $answer ]
then
chmod +x rlog.sh
./rlog.sh
fi
edit

}

for file in $(ls *.h)
do
ci $file
done

for file in $(ls *.c)
do
ci $file
done

for file in $(ls *.h,v)
do
co $file
done

for file in $(ls *.c,v)
do
co $file
done

execute
read
logfile

How to Send a signal -Using Kill command

Ankur Garg — Fri, 15 Jan 2016 12:01:08 +0000

Send a signal by Kill command
=======================
- To send a signal to a process other than current task.
- It has prototype :-
int kill(pid_t pid, int signo);
- It is included using header :-
#include
- The system data type pid_t is defined in header :-
#include
- signo is the signal number of signal to be send.
- pid is the PID of the process to which signal is to be send.
- pid can take value:-
* 0 –> To send signo signal to every process in invoking process’ process group
* -1 –>To send signo signal to every process for which invoking process has permission to send a signal, except itself and init
* n(<-1) –> All process in process group
* n(>0) –> process with PID n is signalled.
- This take an optional signal name or number and the PID to send the signal.

- For eg. To send ‘hangup’ signal to shell running on PID 1001, we use command :-
kill(1001,HUP);
- killall is used to send signal to all the processes running.

How to register a signal

Ankur Garg — Fri, 15 Jan 2016 11:59:04 +0000

Register a signal
==================
- Program can handle a signal using signal library function signal().
- signal() is used to register the signal handler function with kernel on behalf of current process.
- It is included in header :-
#include
- Prototype of function is :-
void* (signal(int signo,void(*func)(int)))(int);
- signal() function takes 2 parameters, signo and func.
- The signal to be caught or ignored is given as argument signo.
- The function to be called when the specified signal is received is given as func.
- The function must take a single int argument (the signal received) and has return type void.

- The signal() command can be used in 3 modes :-
(i) Default mode (Terminate the process)
SIG_DFL –> is used in place of func.
(ii) Ignore the signal
SIG_IGN –> is used in place of func.
(iii) User defined mode
User defined function is used in place of func.

- The signal command returns the function which is setup to handle the signal, SIG_DFL or SIG_IGN in 3rd, 1st and 2nd cases respectively.