Dendrobatus Azureus
It is a beautiful sight to see gping with it's output sent through locat.
Gping gives you a graphical representation of the ping responses of a site
This is the output of the command
`curl style.ysap.sh`
JdeBPThere seem to be no answers matching "back". Both options match "up".
I think that you've overlooked an even more important poll that might be the shibboleth of our time: Does one go up and down a tree? Or does one go back and forth a tree?
Has the tree been chopped down?
(-:
Dendrobatus`curl style.ysap.sh` Bash Style Guide for scripting
Felix Palmen 
@jhx Regarding that, at least in theory, it's indeed "truly portable" as it works fine using only #POSIX compliant APIs.
In practice, there can be issues with platforms that don't implement the *full* POSIX feature-set (which is in fact most platforms nowadays). There can also be nasty issues with how feature-test macros are handled (set by the compiler, interpreted by the system's headers) and sometimes with which libraries are needed (unfortunately, POSIX doesn't specify that, e.g. on illumos, you have to link a libsocket for any socket functionality π).
Once I started to add optional support for the platform-specific mechanisms #epoll on #Linux and #kqueue on #BSD (because the POSIX standard select and poll have severe scalability issues), I wanted to also add support for /dev/poll as used on solaris, that's why I installed #OpenIndiana (illumos-based) in a VM to do tests, and I quickly learned /dev/poll was superseded by "event ports", so that's what I added instead.
In the Everlasting search for clients and servers Federated, detached from corporate underlords, connected to the masses I learned about the following client server duo
Client: Delta Chat
Servers: Chat Mail servers
One thing that jumps immediately into attention, is the fact that when you download the client, select a server, you get a QR code
When you've configured your client, you will immediately notice that you do not need to enter a password for your client. The system is passwordless by default.
You do not need to enter a multi-factor authentication code it doesn't need it.
What you need to do is be careful with, is who you share your link with. Go and play with it, see if it something for you
#Federated #FediVerse #OpenSource #POSIX #Chat #Mail #Secure #encryption #programming #underlords #DeltaChat #email
Radio AzureusWhen was the last time you played with apropos? It's a very handy command to search man pages names and descriptions
Type only apropos and see a nice response ;)
Just released: #swad 0.11 -- the session-less swad is done!
Swad is the "Simple Web Authentication Daemon", it adds cookie/form #authentication to your reverse #proxy, designed to work with #nginx' "auth_request". Several modules for checking credentials are included, one of which requires solving a crypto challenge like #Anubis does, to allow "bot-safe" guest logins. Swad is written in pure #C, compiles to a small (200-300kiB) binary, has minimal dependencies (zlib, OpenSSL/LibreSSL and optionally libpam) and *should* work on many #POSIX-alike systems (#FreeBSD tested a lot, #Linux and #illumos also tested)
This release is the first one not to require a server-side session (which consumes a significant amount of RAM on really busy sites), instead signed Json Web Tokens are now implemented. For now, they are signed using HMAC-SHA256 with a random key generated at startup. A future direction could be support for asymmetric keys (RSA, ED25519), which could open up new possibilities like having your reverse proxy pass the signed token to a backend application, which could then verify it, but still not forge it.
Read more, grab the latest .tar.xz, build and install it ... here: π
HoldMyTypesemantics of POSIX I/O, which define what is and is not guaranteed to happen when a POSIX I/O API call is made. For example, the guarantee that data has been committed to somewhere durable when a write() call returns without an error is a semantic aspect of the POSIX write() API. While this notion of write() being honest about whether it actually wrote data may seem trivial, these semantics can incur a significant performance penalty at scale despite not being strictly necessary.
POSIX I/O is stateful; reading and writing data is governed by some persistent state that is maintained by the operating system in the form of file descriptors.
page cache becomes much more difficult to manage on networked file systems because different client nodes who want to read and write to the same file will not share a common page cache.
POSIX consistency model also makes the other two scalability limits, statefulness and metadata prescription, even worse. For example, the stateful nature of I/O, when combined with the need to implement locking, means that parallel file systems usually have to track the state of every lock on every region of each file. As more compute nodes open files and obtain read or write locks, the burden is on the parallel file system to manage which client nodes possess which locks on which byte ranges within all files. Similarly, metadata such as mtime and atime must be updated in concert with fully consistent reads and writes. This effectively requires that every time a file is read, a new value for the fileβs last-accessed time (POSIX atime) must be written as well.
#posix
https://www.nextplatform.com/2017/09/11/whats-bad-posix-io/
POSIX I/O is stateful; reading and writing data is governed by some persistent state that is maintained by the operating system in the form of file descriptors.
page cache becomes much more difficult to manage on networked file systems because different client nodes who want to read and write to the same file will not share a common page cache.
POSIX consistency model also makes the other two scalability limits, statefulness and metadata prescription, even worse. For example, the stateful nature of I/O, when combined with the need to implement locking, means that parallel file systems usually have to track the state of every lock on every region of each file. As more compute nodes open files and obtain read or write locks, the burden is on the parallel file system to manage which client nodes possess which locks on which byte ranges within all files. Similarly, metadata such as mtime and atime must be updated in concert with fully consistent reads and writes. This effectively requires that every time a file is read, a new value for the fileβs last-accessed time (POSIX atime) must be written as well.
#posix
https://www.nextplatform.com/2017/09/11/whats-bad-posix-io/
Something fascinating happens when I run sudo without having a gateway to the internet ready.
Instead of executing immediately sudo times out for nine, I repeat 9 full seconds, before it reacts
I use sudo plain without any switches and my command structure is
sudo command
I wouldn't have stumbled upon this, if for reasons which are not important now, I didn't have a permanent internet connection at this moment.
I will say that this bug that I have found has nothing to do with sudo in itself
The reason why I say that is when you look at the man page of sudo you will see that it doesn't do any networking at all, when you don't invoke switches
Besides the sudo that I use comes straight of the BSD source structure
The BSD programmers do not play when it comes down to stability of their software. Only when a program runs Rock Solid stable is it released. When a program is in beta it is clearly marked and it shall not be in a standard BSD distribution which is deemed stable.
This means that I have to hunt for something somewhere within my distribution, where there's a link put which shouldn't be there, between sudo and a live internet connection when you do not invoke any network switches.
Mind you that my lan is running and the machine is connected to the lan, via a switch, which is connected to the router, which is connected to the Gateway. The Gateway is live, the DSLAM is working but the internet connection is down
https://linux.die.net/man/8/sudo
#Bugs #BètaTesting #networking #sudo #timeout #GNU #utilities #OpenSource #BSD #POSIX
