This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#include <iostream> | |
int main(){ | |
std::cout << "wow" << std::endl; | |
return 0; | |
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Bind as Manager and add a user as spcified in the ldif file test | |
ldapadd -x -W -D cn=Manager,dc=blah,dc=xxx -a -f test | |
# Bind as "Driver Team" and search for everything in dc=blah,dc=xxx | |
ldapsearch -x -D cn="Driver Team",ou=Users,dc=blah,dc=xxx -W -b dc=blah,dc=xxx | |
# Set the password for "Drivers-Team" | |
ldappasswd -x -D cn="Drivers-Team",ou=Users,dc=blah,dc=xxx -W -S |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
$ clang++ -v test.cpp | |
clang version 3.4 (tags/RELEASE_34/final) | |
Target: x86_64-redhat-linux-gnu | |
Thread model: posix | |
Selected GCC installation: | |
"/usr/bin/clang" -cc1 -triple x86_64-redhat-linux-gnu -emit-obj -mrelax-all -disable-free -disable-llvm-verifier -main-file-name test.cpp -mrelocation-model static -mdisable-fp-elim -fmath-errno -masm-verbose -mconstructor-aliases -munwind-tables -target-cpu x86-64 -target-linker-version 2.20.51.0.2 -v -resource-dir /usr/bin/../lib/clang/3.4 -internal-isystem /usr/local/include -internal-isystem /usr/bin/../lib/clang/3.4/include -internal-externc-isystem /include -internal-externc-isystem /usr/include -fdeprecated-macro -fdebug-compilation-dir /home/ec2-user -ferror-limit 19 -fmessage-length 179 -mstackrealign -fobjc-runtime=gcc -fcxx-exceptions -fexceptions -fdiagnostics-show-option -fcolor-diagnostics -vectorize-slp -o /tmp/test-377209.o -x c++ test.cpp | |
clang -cc1 version 3.4 based upon LLVM 3.4 default target x86_64-redhat-linux-gnu | |
ignoring nonexistent directory " |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sudo ipsec auto --up xgen | |
104 "xgen" #1: STATE_MAIN_I1: initiate | |
003 "xgen" #1: received Vendor ID payload [RFC 3947] method set to=115 | |
003 "xgen" #1: received Vendor ID payload [Dead Peer Detection] | |
106 "xgen" #1: STATE_MAIN_I2: sent MI2, expecting MR2 | |
003 "xgen" #1: NAT-Traversal: Result using draft-ietf-ipsec-nat-t-ike (MacOS X): i am NATed | |
108 "xgen" #1: STATE_MAIN_I3: sent MI3, expecting MR3 | |
004 "xgen" #1: STATE_MAIN_I4: ISAKMP SA established {auth=OAKLEY_PRESHARED_KEY cipher=oakley_3des_cbc_192 prf=oakley_sha group=modp1024} | |
117 "xgen" #2: STATE_QUICK_I1: initiate | |
003 "xgen" #2: NAT-Traversal: received 2 NAT-OA. ignored because peer is not NATed |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
yaourt trucov | |
1 aur/trucov 10.1-1 (1) | |
trucov coverage analysis tool a developer tool to analyze coverage information generated by gcc --coverage | |
==> Enter n° of packages to be installed (ex: 1 2 3 or 1-3) | |
==> ------------------------------------------------------- | |
==> 1 | |
==> Downloading trucov PKGBUILD from AUR... | |
x PKGBUILD |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#include "mongo/util/net/ssl_options.h" | |
#include "mongo/client/init.h" | |
int main() { | |
sslGlobalParams.sslMode.store(SSLGlobalParams::SSLMode_requireSSL); | |
// only really need a PEM on the server side | |
mongo::sslGlobalParams.sslPEMKeyFile = "<path/to/keyfile.pem>"; | |
mongo::Status status = mongo::client::initialize(); |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
$ ./configure --enable-man-pages --prefix /home/tbrock/mantest | |
checking for gcc... gcc | |
checking whether the C compiler works... yes | |
checking for C compiler default output file name... a.out | |
checking for suffix of executables... | |
checking whether we are cross compiling... no | |
checking for suffix of object files... o | |
checking whether we are using the GNU C compiler... yes | |
checking whether gcc accepts -g... yes | |
checking for gcc option to accept ISO C89... none needed |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
#ifndef LIBFOO_H_INCLUDED | |
#define LIBFOO_H_INCLUDED | |
#pragma once | |
#include "libfoo_export.h" | |
#if defined(__cplusplus) | |
#define LIBFOO_NOEXCEPT noexcept | |
extern "C" { |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
db.test.write(std::vector awesome) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Feature: Driver failure recovery | |
In order to ensure the driver remains usable in the face of failures | |
As a driver author | |
I want the driver to recover in the event of failures | |
Scenario: Server is stopped and started | |
Given a cluster in the standalone server configuration | |
When I insert a document | |
Then the insert succeeds | |
When I stop the server |
OlderNewer