The Gearman job server supports a text-based protocol to pull information and run some administrative tasks. The following commands are supported:
workersstatusmaxqueueshutdownversion
| package com.your.package; | |
| import android.content.ComponentName; | |
| import android.content.Context; | |
| import android.content.Intent; | |
| import android.content.pm.ResolveInfo; | |
| import android.database.DataSetObservable; | |
| import android.os.AsyncTask; | |
| import android.os.Build; | |
| import android.text.TextUtils; |
| <?xml version="1.0" encoding="utf-8"?> | |
| <resources> | |
| <!-- google's material design colours from | |
| http://www.google.com/design/spec/style/color.html#color-ui-color-palette --> | |
| <!--reds--> | |
| <color name="md_red_50">#fde0dc</color> | |
| <color name="md_red_100">#f9bdbb</color> | |
| <color name="md_red_200">#f69988</color> |
| package com.aaplab.robird.util; | |
| import android.content.BroadcastReceiver; | |
| import android.content.Context; | |
| import android.content.Intent; | |
| import android.content.IntentFilter; | |
| import android.net.ConnectivityManager; | |
| import android.os.Handler; | |
| import android.os.Looper; |
| <?php | |
| namespace FTW\GuildBundle\Services; | |
| /** | |
| * Monitoring Gearman over telnet port 4730 | |
| * | |
| * So the only way to monitor Gearman is via doing a telnet to port 4730. The | |
| * current monitoring supported commands are fairly basic. | |
| * There are plans to include more set of commands in the next release. |
| <ul id="members" data-role="listview" data-filter="true"> | |
| <!-- ... more list items ... --> | |
| <li> | |
| <a href="detail.html?id=10"> | |
| <h3>John Resig</h3> | |
| <p><strong>jQuery Core Lead</strong></p> | |
| <p>Boston, United States</p> | |
| </a> | |
| </li> | |
| <!-- ... more list items ... --> |
| package main | |
| import ( | |
| "context" | |
| "flag" | |
| "fmt" | |
| "log" | |
| "net/http" | |
| "os" | |
| "os/signal" |
The purpose of this document is to explain how to deploy an Upspin server on a Debian or Ubuntu based machine - which can be a Raspberry Pi - and, optionally, use Google Drive to back the data.
Effectively, this will give you all the nifty advantages Upspin gives you in terms of file sharing without requiring a costly server.
| #!/bin/bash | |
| # | |
| # | |
| # Script combines given JUnit XML files into one. | |
| # | |
| # Script assumes that file begins with XML header. | |
| # Script will copy content between <testsuite> tags | |
| # to new file with XML header and <testsuites> tags. | |
| # Script will not affect original files, but it will | |
| # overwrite output file contents. Script searches all |