vortec

#!/usr/bin/env python

bld.SAMBA3_MODULE('vfs_fspattern',
                 subsystem='vfs',
                 source='fspattern.c',
                 deps='samba-util',
                 init_function='',
                 internal_module=bld.SAMBA3_IS_STATIC_MODULE('vfs_fspattern'),
                 enabled=True)

vortec

#!/usr/bin/env python

bld.SAMBA3_MODULE('vfs_fspattern',
                 subsystem='vfs',
                 source='fspattern.c',
                 deps='samba-util',
                 init_function='samba_init_module',
                 internal_module=bld.SAMBA3_IS_STATIC_MODULE('vfs_fspattern'),
                 enabled=True)

vortec

#include "../source3/include/includes.h"
#include "lib/util/tevent_unix.h"
#include "lib/util/tevent_ntstatus.h"

static int fspattern_connect(vfs_handle_struct *handle,
                             const char *service,
                             const char *user)
{
    FILE *f = fopen("/tmp/mylog.txt", "w");
    if (f != NULL)

vortec

Keybase proof

I hereby claim:

• I am vortec on github.
• I am fkochem (https://keybase.io/fkochem) on keybase.
• I have a public key whose fingerprint is E272 6047 B340 E2C9 E6D4 4191 3EBD EAC9 4504 DB5C

To claim this, I am signing this object:

vortec

README for Samba Virtual File System (VFS) Example
===================================================

This directory contains skeleton VFS modules.  When used,
this module simply passes all requests back to the disk functions
(i.e it operates as a passthrough filter).  It should be
useful as a starting point for developing new VFS
modules. 

Please look at skel_opaque.c when you want your module to provide

vortec

php > $a = 0;
php > var_dump([$a[0] => $a[0]]);
array(1) {
  [""]=>
  NULL
}
php > 

vortec

cnf: each of our services has its own git repository and some services depend
on each other. my goal is to ease and automate the setup of dev environments.
to do that, i need a Vagrantfile, a few scripts which are part of the provision
process and said git repositories (containing the services' code).
also, you convinced me that it's a good idea to keep the code outside the VM,
because it's better for various reasons (way it's supposed to be, can edit code
in editor on the host)
so, how do i get the vagrant files and service repositories out to the users?
i can think of three ways of doing that: a tarball containing vagrant files +
service repos, another git repository containing vagrant files + service repos

vortec

DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
DEBUG virtualbox_4_3:   - [1, "ssh", 2222, 22]
DEBUG virtualbox_4_3:   - [1, "tcp9080", 9080, 80]
DEBUG virtualbox_4_3:   - [1, "tcp9090", 9090, 9090]
DEBUG ssh: stderr: stdin: is not a tty

DEBUG ssh: stderr: mount: Protocol error

DEBUG ssh: Exit status: 32

vortec

Process:         GRID [87726]
Path:            /Applications/GRID.app/Contents/MacOS/GRID
Identifier:      com.feralinteractive.grid
Version:         1.1 (1.1)
App Item ID:     594773178
App External ID: 81982783
Code Type:       X86 (Native)
Parent Process:  launchd [157]
Responsible:     GRID [87726]
User ID:         501

vortec

Process:         GRID [87357]
Path:            /Applications/GRID.app/Contents/MacOS/GRID
Identifier:      com.feralinteractive.grid
Version:         1.1 (1.1)
App Item ID:     594773178
App External ID: 81982783
Code Type:       X86 (Native)
Parent Process:  launchd [157]
Responsible:     GRID [87357]
User ID:         501