RCS file: sema.c,v
Working file: sema.c
head: 1.8
branch:
locks: strict
akshat: 1.8
access list:
symbolic names:
keyword substitution: kv
total revisions: 8; selected revisions: 8
description:
This is communication btw 3 clients and central server.
all are sendings requests simultaneously.
using semaphore syncronisation is done.
—————————-
revision 1.8 locked by: akshat;
date: 2014/03/27 04:12:31; author: akshat; state: Exp; lines: +3 -5
file descripter was named incorrect.
semaphore is working
project is working.
—————————-
revision 1.7
date: 2014/03/27 01:45:41; author: akshat; state: Exp; lines: +4 -3
Working fine but with few limitations.
:/
—————————-
revision 1.6
date: 2014/03/27 01:30:59; author: akshat; state: Exp; lines: +48 -68
Answer is going exact same in requesting clients.
but now in server operator is not exactly same printed.
checking for any left file descripter to be closed.
—————————-
revision 1.5
date: 2014/03/27 00:58:46; author: akshat; state: Exp; lines: +14 -1
Without using any wait or sleep statement, result is found to be correct.
Semaphore is working very well
Now from server, with a new fifo, this will be passed to the requsting client.
project is 75% done, without any error.
—————————-
revision 1.4
date: 2014/03/26 19:15:50; author: akshat; state: Exp; lines: +12 -3
its working fine, Processing client is getting all the msgs.
now result has to be passed to server again.
From server result will go back to the requesting client.
—————————-
revision 1.3
date: 2014/03/26 03:59:16; author: akshat; state: Exp; lines: +21 -5
Processing client is not getting the data.
checking.
—————————-
revision 1.2
date: 2014/03/26 03:53:00; author: akshat; state: Exp; lines: +54 -38
Now creating a processing client for same.
nos read will dirctly be sent to processing client for processing.
—————————-
revision 1.1
date: 2014/03/26 03:39:54; author: akshat; state: Exp;
Initial revision
=============================================================================