posix

来源： https://stackoverflow.com/questions/32205396/share-posix-semaphore-among-multiple-processes

问题 The MSDN documentation for LoadLibrary warns not to use normal Unix slash "/": When specifying a path, be sure to use backslashes (\), not forward slashes (/). I couldn't find any problems using either forward slashes or backslashes (or both) when calling this API. I tried the following pathnames: c:/foo/bar/baz.dll /foo/bar/baz.dll c:/foo/bar\\baz.dll /foo/bar\\baz.dll ./bar/baz.dll All combinations worked as expected. Why does the MSDN recommend against using forward slashes as path

问题 The MSDN documentation for LoadLibrary warns not to use normal Unix slash "/": When specifying a path, be sure to use backslashes (\), not forward slashes (/). I couldn't find any problems using either forward slashes or backslashes (or both) when calling this API. I tried the following pathnames: c:/foo/bar/baz.dll /foo/bar/baz.dll c:/foo/bar\\baz.dll /foo/bar\\baz.dll ./bar/baz.dll All combinations worked as expected. Why does the MSDN recommend against using forward slashes as path

问题 When should we use fdopen and how do we use it? My understanding of that is when we can't use fopen to read (read from pipe). I don't really understand the description of fdopen on the man page: The fdopen() function associates a stream with the existing file descriptor, fd . 回答1: You use fdopen() when you have a file descriptor ( int fd; ) of some sort but you need to call functions that require a file stream ( FILE *fp; ) instead. This could be a pipe file descriptor, or a socket file

问题 When should we use fdopen and how do we use it? My understanding of that is when we can't use fopen to read (read from pipe). I don't really understand the description of fdopen on the man page: The fdopen() function associates a stream with the existing file descriptor, fd . 回答1: You use fdopen() when you have a file descriptor ( int fd; ) of some sort but you need to call functions that require a file stream ( FILE *fp; ) instead. This could be a pipe file descriptor, or a socket file

问题 sprintf_s is a Microsoft implementation of the function sprintf where they patched a flaw, adding an argument to take a boundary value where the function is limited to write. An equivalent was introduced in C++11 : snprintf . But here, we are talking of C++03 syntax. Signatures: count_char_written sprintf(char* string_out, const char* output_template, VARIADIC_ARGS); // and count_char_written sprintf_s(char* string_out, size_t buffer_max_size, const char* output_template, VARIADIC_ARGS);

问题 I'm writing some software to deal with pretty critical data, and need to know what exactly I need to do to achieve durability. Everywhere I look is contradictory information, so I'd appreciate any insight. There are three ways I write to disk. Using O_DIRECT | O_DSYNC, and pread'ing and then pwrite'ing 512 byte - 16 MB blocks. Using O_DIRECT, pread'ing and then pwrite'ing 512 byte blocks, and calling fdatasync as regularly as necessary. Using a memory mapped file, which I call msync(..., MS

问题 I have a multicore program that uses a UNIX domain datagram socket. Three cores (or more, but 3 in this example) send records with sendto and one core receives records with recvfrom and processes the records sent by multiple clients. Each core is assigned to a separate core (using its affinity mask). The program processes a data series in a loop and at the end of each iteration the cores send data to the socket. The data series is small 64-bit integers. My problem is that I receive records

问题 I have to create single Server Process A and multiple client process(es). All should use Linux POSIX IPC message queue for data passing. Message(s) will flow in both direction. It is also possible that at time multiple client process(es) may have registered to Server Process A. Currently I'm using only one named Message queue which is created and Opened by Server Process A and used/opened (only) by client process(es). This works with two process scenario (i.e One server Process A and one

问题 I have large zip files that contain huge files. There are "metadata" text files within the zip archives that need to be modified. However, it is not possible to extract the entire zip and re-compress it. I need to locate the target text file inside the zip, edit it, and possibly append the change to the zip file. The file name of the text file is always the same, so it can be hard-coded. Is this possible? Is there a better way? 回答1: There are two approaches. First, if you're just trying to