pacman -S openssh
systemctl start sshd
systemctl enable sshd.socket
| #!/bin/sh | |
| # invoke global X session script | |
| #. /etc/X11/Xsession | |
| # HOW-TO : | |
| # 1. Disable any Display Manager (lightdm/gdm/gdm3) from executing on startup | |
| # 2. Allow user to start X : | |
| # a. Edit /etc/X11/Xwrapper.config | |
| # b. Set value : "allowed_users=anybody" | |
| # 3. insert "su kiosk -c xinit &" into /etc/rc.local |
| #!/usr/bin/env python | |
| import pygtk | |
| import gtk | |
| import webkit | |
| import sys | |
| class Browser: | |
| def __init__(self): |
| #!/usr/bin/env bash | |
| # MIT © Sindre Sorhus - sindresorhus.com | |
| # git hook to run a command after `git pull` if a specified file was changed | |
| # Run `chmod +x post-merge` to make it executable then put it into `.git/hooks/`. | |
| changed_files="$(git diff-tree -r --name-only --no-commit-id ORIG_HEAD HEAD)" | |
| check_run() { | |
| echo "$changed_files" | grep --quiet "$1" && eval "$2" |
#Node - Processes
To launch an external shell command or executable file you can use the child_process. Apart from command line arguments and environment variables you cannot communicate with the process using child_process.exec. However you can use child_process.spawn to create a more integrated processes.
##Executing Child Processes
###To launch an external shell command
var child_process = require('child_process');
var exec = child_process.exec;From Meteor's documentation:
In Meteor, your server code runs in a single thread per request, not in the asynchronous callback style typical of Node. We find the linear execution model a better fit for the typical server code in a Meteor application.
This guide serves as a mini-tour of tools, trix and patterns that can be used to run async code in Meteor.
Sometimes we need to run async code in Meteor.methods. For this we create a Future to block until the async code has finished. This pattern can be seen all over Meteor's own codebase:
| #!/bin/bash | |
| # | |
| # DESCRIPTION: | |
| # | |
| # Set the bash prompt according to: | |
| # * the active virtualenv | |
| # * the branch/status of the current Git, Mercurial or Subversion repository | |
| # * the return value of the previous command | |
| # * the fact you just came from Windows and are used to having newlines in | |
| # your prompts. |
