fissures

Random notes of a software engineer, guitarist, and beer enthusiast.

[m2ch1ne]

gotrig - lightweight fifo-based IPC event triggers

[m2ch1ne]

Sharding in distributed hash table

[0xcctylerneely]

[m2ch1ne]

Saving this for later..

[m2ch1ne]

Just installed Fedora 21 on an Asus Chromebox and wanted a way for multiple user accounts to play audio while logged in as the main desktop user. Both the TCP and unix domain socket approaches worked perfectly.

In the desktop user's account:

--- /etc/pulse/default.pa 2014-11-14 10:44:14.000000000 -0500 +++ /home/jdefelice/.pulse/default.pa 2015-03-08 10:31:01.915996018 -0400 @@ -77,7 +77,7 @@ .ifexists module-esound-protocol-unix.so load-module module-esound-protocol-unix .endif -load-module module-native-protocol-unix +#load-module module-native-protocol-unix ### Network access (may be configured with paprefs, so leave this commented ### here if you plan to use paprefs) @@ -85,6 +85,9 @@ #load-module module-native-protocol-tcp #load-module module-zeroconf-publish +#load-module module-native-protocol-tcp auth-ip-acl=127.0.0.1 +load-module module-native-protocol-unix auth-anonymous=1 socket=/tmp/jdef-pulse-socket + ### Load the RTP receiver module (also configured via paprefs, see above) #load-module module-rtp-recv

In the auxillary user's account:

$ cat ~/.pulse/client.conf #default-server = 127.0.0.1 default-server = unix:/tmp/jdef-pulse-socket

[m2ch1ne]

BSM Development. Tech Notes - How to print banner and test pages with later versions of CUPS, built from source.

Pretty thankful that someone wrote up this tech note. I have an older CUPS print server and some much newer clients. The OS X clients printed test pages just fine, but not the newer Linux clients. This solved the problem.

[scalingo]

Go has been designed as a backend language and is mostly used as such. Servers are the most common type of software produced with it. The question I’m going to answer here is: how to cleanly upgrade a running server?

Goals:

Do not close any of the existing connections: for instance, we...

[m2ch1ne]

Posts about sharectl set -p lmauth_level=3 smb written by Collin C MacMillan

Definitely wasted a bunch of time on this yesterday: I couldn't get my phone to connect to the ZFS/CIFS share that I had set up. I kept seeing a WRONG_PASSWORD error every time I attempted to access the share. I spent a while reading up (again) on ACLs for ZFS shares. That wasn't the problem at all. As it happens the default setting for the (old and outdated) variant of OpenSolaris that I'm still running is level=4 -- which others have also complained about. Switching the value of this property to 3 does the trick.

I also found this nice SMB for Solaris walk-through, though it wasn't particularly helpful for solving my problem.

[m2ch1ne]

NOVA-PV-D5251-G4 is a 5.25" embedded board with Intel Atom D525 1.8GHz dual core processor, dual channel DDR3 1333/1066MHz memory up to 4GB, quad PCIe Gigabit Ethernet ports, eight USB2.0 ports, six COM ports and two SATA 3.0Gbps ports. It is ideal for high performance and reliability concernd applications.

Considering purchasing one of these. Anyone have experience with them? Also related:

https://www.industrialpcpro.com/nova-hm551-525-embedded-board

http://www.anovotech.com/english/xx-5.25-5845.php (Intel NIC)

http://www.nexcomshop.com/Embedded-Computing/5-25-CPU-Boards/EBC-550.cfm (Intel NIC)

[m2ch1ne]

Last time I applied formal methods was probably 14 years ago, and I hated it: so much work to prove such a little program was correct. Looks like we've made progress since then. The intro manual is a pretty good read. (via)

[nosql]

Hardware failure is one of the major causes leading to failure of systems and implicitely to the deterioration of the quality of service. Predicting hardward failures would allow taking proactive measures, thus reducing the chances of downtime in the systems.

Unfortunately for a large number of hardware components this is not possible. But, Backblaze, the company providing a consumer online backup solution, has published some results that show that hard drivers failure can be predicted; and that by analysing only 5 metrics (out of over 70 available):

From experience, we have found the following 5 SMART metrics indicate impending disk drive failure:

SMART 5 – Reallocated_Sector_Count.

SMART 187 – Reported_Uncorrectable_Errors.

SMART 188 – Command_Timeout.

SMART 197 – Current_Pending_Sector_Count.

SMART 198 – Offline_Uncorrectable.

The rest of the post dives into each of these. If other large cluster users—I’m thinking of Amazon, Facebook, Google, Microsoft here—could back these findings, the results could have a significant impact on operating storage.

Original title and link: Can hard drives’ failure be predicted? (NoSQL database©myNoSQL)

[m2ch1ne]

I recorded a quick asciinema session this morning that shows how to get started running the Kubernetes-Mesos framework on Mesos in digitalocean's cloud.

[m2ch1ne]

What? I built a tool which makes it easier to use ZAP for transparent HTTPS proxying. Why? Man-in-the-middle proxies are useful tools for developers and security people alike. The ability to view and manipulate the data travelling between parts of an ...

[m2ch1ne]

Stumbled across this patch today (via). Probably why my MythTV is needlessly consuming CPU cycles while idle.

[m2ch1ne]

[m2ch1ne]

[m2ch1ne]

xxHash wider : 64-bits