svmsg/svmsg_file_server.cThis is svmsg/svmsg_file_server.c (Listing 46-8, page 957), an example from the book, The Linux Programming Interface. The source code file is copyright 2024, Michael Kerrisk, and is licensed under the GNU General Public License, version 3. This page shows the "distribution" or "book" version of the file (why are there two versions?), or the differences between the two versions. You can switch between the views using the tabs below. In the listing below, the names of Linux system calls and C library functions are hyperlinked to manual pages from the Linux man-pages project, and the names of functions implemented in the book are hyperlinked to the implementations of those functions.
|
/* svmsg_file_server.c A file server that uses System V message queues to handle client requests (see svmsg_file_client.c). The client sends an initial request containing the name of the desired file, and the identifier of the message queue to be used to send the file contents back to the child. The server attempts to open the desired file. If the file cannot be opened, a failure response is sent to the client, otherwise the contents of the requested file are sent in a series of messages. This application makes use of multiple message queues. The server maintains a queue (with a well-known key) dedicated to incoming client requests. Each client creates its own private queue, which is used to pass response messages from the server back to the client. This program operates as a concurrent server, forking a new child process to handle each client request while the parent waits for further client requests. */ #include "svmsg_file.h"
static void /* SIGCHLD handler */ grimReaper(int sig) { int savedErrno; savedErrno = errno; /* waitpid() might change 'errno' */ while (waitpid(-1, NULL, WNOHANG) > 0) continue; errno = savedErrno; }
static void /* Executed in child process: serve a single client */ serveRequest(const struct requestMsg *req) { int fd; ssize_t numRead; struct responseMsg resp; fd = open(req->pathname, O_RDONLY); if (fd == -1) { /* Open failed: send error text */ resp.mtype = RESP_MT_FAILURE; snprintf(resp.data, sizeof(resp.data), "%s", "Couldn't open"); msgsnd(req->clientId, &resp, strlen(resp.data) + 1, 0); exit(EXIT_FAILURE); /* and terminate */ } /* Transmit file contents in messages with type RESP_MT_DATA. We don't diagnose read() and msgsnd() errors since we can't notify client. */ resp.mtype = RESP_MT_DATA; while ((numRead = read(fd, resp.data, RESP_MSG_SIZE)) > 0) if (msgsnd(req->clientId, &resp, numRead, 0) == -1) break; /* Send a message of type RESP_MT_END to signify end-of-file */ resp.mtype = RESP_MT_END; msgsnd(req->clientId, &resp, 0, 0); /* Zero-length mtext */ }
int main(int argc, char *argv[]) { struct requestMsg req; pid_t pid; ssize_t msgLen; int serverId; struct sigaction sa; /* Create server message queue */ serverId = msgget(SERVER_KEY, IPC_CREAT | IPC_EXCL | S_IRUSR | S_IWUSR | S_IWGRP); if (serverId == -1) errExit("msgget"); /* Establish SIGCHLD handler to reap terminated children */ sigemptyset(&sa.sa_mask); sa.sa_flags = SA_RESTART; sa.sa_handler = grimReaper; if (sigaction(SIGCHLD, &sa, NULL) == -1) errExit("sigaction"); /* Read requests, handle each in a separate child process */ for (;;) { msgLen = msgrcv(serverId, &req, REQ_MSG_SIZE, 0, 0); if (msgLen == -1) { if (errno == EINTR) /* Interrupted by SIGCHLD handler? */ continue; /* ... then restart msgrcv() */ errMsg("msgrcv"); /* Some other error */ break; /* ... so terminate loop */ } pid = fork(); /* Create child process */ if (pid == -1) { errMsg("fork"); break; } if (pid == 0) { /* Child handles request */ serveRequest(&req); _exit(EXIT_SUCCESS); } /* Parent loops to receive next client request */ } /* If msgrcv() or fork() fails, remove server MQ and exit */ if (msgctl(serverId, IPC_RMID, NULL) == -1) errExit("msgctl"); exit(EXIT_SUCCESS); }
Note that, in most cases, the programs rendered in these web pages are not free standing: you'll typically also need a few other source files (mostly in the lib/ subdirectory) as well. Generally, it's easier to just download the entire source tarball and build the programs with make(1). By hovering your mouse over the various hyperlinked include files and function calls above, you can see which other source files this file depends on.