$3\mathrm{.}2$ logservice$.$c $3\mathrm{.}4$ logserver$.$c $3\mathrm{.}5$ makefile

$3\mathrm{.}6$ launch$\_$s

Pl write a complete working code in detail for below one. Thanks

$3\mathrm{.}1$ logservice$.$h$2$ Specification

The task is broken into two parts, a message logging server, and a library to log messages. The

message server listens to a message queue and extracts the log messages from it$.$ The library

provides a more convenient way access the message queue.

You have been provided with a program to test that your library communicates with your

server. You will need to review the lecture notes, and the documentation supplied in Section $4$

to implement these programs.

$2\mathrm{.}1$ Message Logging Server

The message logging server should attempt to create the message queue, if this fails then it

should terminate with an error message, it should not run if the message queue actually exists

$($IPC$\_$EXCL will help here$).$

Once connected to the message queue, the program should sit in a loop, receiving a message, and printing it to the stdout. Messages should be formatted:

id: message

where id is the type from the message structure and message is the message field.

The server should shutdown cleanly $($i$.$e$.$ delete the message queue$)$ on receipt of a SIGINT

$($generated by pressing control and C keys at the same time$).$

The sample code files logservice$.$h and logserver$.$c should form the basis of

your solution for this part. There are a number of comments in this file to help you structure

your code.

$2\mathrm{.}2$ Messaging library

The messaging library consists of two functions, both defined in logservice$.$h:

int initLogService$()$

This function should initialise the message queue to log messages to$,$ returning

an id if successful, and $-1$ on error.

This function should not attempt to create the message queue, only attach it to

the process.

$1$

int logMessage$($int id$,$ char $*$message$)$

This function logs the message passed as the string message to the log

service id$.$ It should return $0$ on success and $-1$ on error.

When sending a message, the function should encode the processes pid into

the type field of the message, and the string into the message field.

It is your choice what to do if the message is too long $($i$.$e$.$ longer than

MSGCHARS$),$ sample behaviours include breaking the message up into

smaller pieces or simply rejecting it$.$ Whatever the choice, the documentation in

the header file should reflect this choice.

The sample code files logservice$.$h and logservice$.$c should form the basis of

your solution for this part.

$3$ Sample Code

In addition to the sample code files, two additional files have been provided, a makefile

that contains build rules, and a server launch script.

The make utility simplifies the build process for large projects, introductory documentation for make is included in the documentation section $($Sec$.4).$ To use make to automate compile process simply type $$make$$ at the terminal $($in the same directory as the other

files$),$ it will use the rules defined in the makefile to build both the logserver and

logclient executables from the source files, and it will also ensure that the

launch server.sh script is executable. If none of the source files have changed since

the last build $($based on their timestamps$)$ the make utility will not rebuild the executables.

There should be no need to modify the makefile, its format is a bit fussy so it is safer to

download the file from vUWS than type it up$.$

The launch server.sh script will open the logserver program in a new terminal window for you. This script detects the host operating system and performs an equivalent action after this detection. There is nop need to understand how this file achieves its goal. Validate message length here $*$

$3\mathrm{.}2$ logservice$.$c

$/*$ logservice$.$c $--$ implementation of the log service

$*$ Dr Evan Crawford $($e$.$crawford@westernsydney.edu.au$)$

$*$ COMP $30015$ Operating Systems Programming

$*$ Practical Case Study C

$*$ This is the sample file

$*/$

#include "logservice.h$"$

int logServiceInit$()$

$\{$

int id;

$/*$ TODO: connect to message queue here $*/$

return id;

$\}$

int logMessage$($int serviceId,char $*$message$)$

$\{$

int rv;

printf$("$The message is $\backslash "\%$s$\backslash "$

$",$ message$)$;

$/*$ TODO: Validate message length here $*/$

$/*$ TODO: Send the message $*/$

return rv;

$\}$

$4$

$3\mathrm{.}3$ logclient$.$c

$/*$ logclient$.$c $--$ implements a simple log service client

$*$ Dr Evan Crawford $($e$.$crawford@westernsydney.edu.au$)$

$*$ COMP $30015$ Operating Systems Programming

$*$ Practical Case Study C

$*$ This is the sample file

$*/$

#include "logservice.h$"$

int main$($int argc,char $**$argv$)$

$\{$

int id;

$/*$ Check if arguments are present on command line $*/$

if $($argc $<mtext></mtext><mn>2</mn><mi>)</mi>$

$\{$

fprintf$($stderr$,$ "Usage: $\%$s message", argv$[0])$;

exit$(1)$;

$\}$

$/*$ connect to the log service $*/$

if$(-1==($id $=$ logServiceInit$()))$

$\{$

perror$("$Connecting to queue"$)$;

exit$(1)$;

$\}$

$/*$ log the message supplied on the command line $*/$

if$(-1==$ logMessage$($id$,$ argv$[1]))$

$\{$

perror$("$Sending Message"$)$;

exit$(1)$;

$\}$

return $0$;

$\}$

$5$

$3\mathrm{.}4$ logserver$.$c

$/*$ logserver$.$c $--$ implementation of the log server

$*$ Dr Evan Crawford $($e$.$crawford@westernsydney.edu.au$)$

$*$ COMP $30015$ Operati