The project aims to prepare a system of processes that can interact with each other communicate and ask each other to trigger commands

The project aims to prepare a system of processes that can interact with each other communicate and ask each other to trigger commands. Each of the processes has a name thanks to it so it will be possible, for example, to ask the process called usr1 to execute the ls command. Belongs use any process communication mechanism. Create a configuration file that will save the process name (given by user) and associate it with a specific communication channel (fifo queue, memory shared message queue). A sample file for message queues looks like Yes: usr1 : 11233 usr2 : 34567 ... The configuration file defines the name of the process and the method of sending a message to it initiating communication. In case of: 1. fifo queue will be the name of the special file 2. for shared memory, this will be the key number 3. for a message queue, this will be the key number Each of the processes is started with a name as the start parameter. e.g. $> ./project usr1 Based on the name (usr1), this process reads the configuration file and creates its global the communication mechanism on which it listens (fifo, message queue, memory shared) of incoming messages from other processes - in the example number 11233 is used Then this process also reads (in the second process) the messages written by user in the terminal (you can use scanf). User input messages is information to which process (with what name from the configuration file to send the command to be performed, and information on which communication channel I am waiting for a return responses - e.g. fifo queue name or message queue / shared memory key). Sending a request to execute a command looks like the user enters in the terminal which ones the command is to execute a process, e.g.: $> usr2 “ls -l | tr a-z A-Z” “./command_queue_1” As a result, the process requesting the above command creates a fifo queue “./command_queue_1” and only after its creation sends the command to the selected one global communication mechanism. In our example, it's a queue (or fifo, shared memory) of the usr2 process (identified by the key 34567). The usr2 process receives this message, opens the fifo queue "./command_queue_1", executes the pipeline rows and writes its result to the “./command_queue_1” queue. It belongs in both processes to implement appropriate error messages (no queue, etc.). Eventually the requesting process will print the result to its terminal.