Chrissie Caulfield comments

Results 23 comments of


                                            Chrissie Caulfield

Using /dev/shm directly is (potentially) broken

Good catch, I'll look into this.

Using /dev/shm directly is (potentially) broken

In general I'm very much in favour of keeping abstract sockets on Linux. They have a few good advantages (not having to deal with filesystem variances is one, but automatic...

Using /dev/shm directly is (potentially) broken

Thanks for that. I think that should definitely be on the roadmap. I have very little time for libqb at the moment, sadly, but I'll keep this on the list...

Linux sockets should maybe pass effective UID/GID

@kgaillot While you are undoubtedly right, I worry what would break if we were to change it now.

broken `test_ipc_max_dgram_size` test needs to be reviewed

Very odd. I'm not going to worry about it short-term, though it would be useful to know how the test systems are set up. Can we reproduce it with clang...

broken `test_ipc_max_dgram_size` test needs to be reviewed

It's testing socket buffers rather than SHM arenas so it might be a ulimit issue. Odd that it failed there though because that's comparing the reported maximum with the actual...

storage_mon: Use the O_DIRECT flag in open() to eliminate cache effects

I agree with Ken (in the above thread) that there should be a fallback if O_DIRECT fails. There are filesystems and options even on Linux that don't always support O_DIRECT...

storage_mon: Use the O_DIRECT flag in open() to eliminate cache effects

retest this please

storage_mon: Use the O_DIRECT flag in open() to eliminate cache effects

retest this please

Default socketdir (`/var/run`) is restricted area

You can configure libqb with --socketdir though that's obviously not a good general solution. I think this is partly down to libqb being spun-off from corosync where the daemons it...