This is a quick guide to mounting a qcow2 disk images on your host server. This is useful to reset passwords, edit files, or recover something without the virtual machine running.
Step 1 - Enable NBD on the Host
modprobe nbd max_part=8
#!/bin/bash | |
cat init-stream0.m4s $(find . -name "chunk-stream0-*.m4s" | sort) > tmp_video.mp4 | |
cat init-stream1.m4s $(find . -name "chunk-stream1-*.m4s" | sort) > tmp_audio.mp4 | |
docker run --rm -v "$(pwd):/data" jrottenberg/ffmpeg -i /data/tmp_video.mp4 -i /data/tmp_audio.mp4 -c copy /data/final_video.mp4 |
-- ddcavcontrol | |
-- v1.2.1 | |
-- This Hammerspoon script is intended to do the following: | |
-- 1) Control External Display Brightness via DDC (utilizing a proper brightness+contrast curve) | |
-- 2) Control External Display Volume via DDC | |
-- 3) Control Digital AV Volume via Network (currently works with Yamaha AVs) | |
-- 4) Use the standard brightness and volume keys of an Apple keyboards | |
-- 5) Display the standard MacOS OSD as expected |
<?xml version="1.0" encoding="utf-8"?> | |
<set xmlns:android="http://schemas.android.com/apk/res/android" android:ordering="sequentially"> | |
<objectAnimator android:propertyName="alpha" | |
android:duration="200" | |
android:valueFrom="1.0" | |
android:valueTo="0.0" | |
android:valueType="floatType" /> | |
<objectAnimator android:propertyName="alpha" | |
android:duration="200" | |
android:valueFrom="0.0" |
<?xml version="1.0" encoding="utf-8"?> | |
<set xmlns:android="http://schemas.android.com/apk/res/android"> | |
<alpha android:fromAlpha="1.0" android:toAlpha="0.5" android:duration="20" android:startOffset="0"/> | |
<alpha android:fromAlpha="0.5" android:toAlpha="0.04" android:duration="20" android:startOffset="20"/> | |
<alpha android:fromAlpha="0.04" android:toAlpha="0.8" android:duration="20" android:startOffset="40"/> | |
<alpha android:fromAlpha="0.8" android:toAlpha="0.0" android:duration="20" android:startOffset="60"/> | |
<alpha android:fromAlpha="0.0" android:toAlpha="1.0" android:duration="20" android:startOffset="80"/> | |
<alpha android:fromAlpha="1.0" android:toAlpha="0.01" android:duration="40" android:startOffset="100"/> |
// | |
// NSImage+OpenCV.h | |
// | |
#import <AppKit/AppKit.h> | |
@interface NSImage (NSImage_OpenCV) { | |
} |
[program:mongodb] | |
command=/opt/mongodb/bin/mongod --dbpath /storage/mongodb_data --rest | |
directory=/opt/mongodb | |
user=root | |
autostart=false |
#MongoDB 3.2.x Replica Sets on AWS EC2 A MongoDB replica set provides a mechanism to allow for a reliable database services. The basic replica set consists of three servers, a primary, a secondary and an arbitrator. The primary and secondary both hold a copy of the data. The arbitrator is normally a low spec server which just monitors the other servers and help with the failover process. In production, there can be more than three servers.
To setup mongo as a replica set on Amazon Web Services EC2 you need to first setup a security group with ssh on port 22 and mongodb on port 27017. You then need to create three servers. Select Ubuntu 14.04 LTS x64 and a micro (or bigger depending on your database size, ideally you should have enough memory to match your database size) instance for the primary and secondary and a nano instance for the arbitrator.
##Adjust the File System on each Server The operating system by default will update the last access time on a file. In a high data throughput database application