summaryrefslogtreecommitdiff
path: root/src/Linux:Vpnc_Restart_Script.ascii
diff options
context:
space:
mode:
Diffstat (limited to 'src/Linux:Vpnc_Restart_Script.ascii')
-rw-r--r--src/Linux:Vpnc_Restart_Script.ascii47
1 files changed, 47 insertions, 0 deletions
diff --git a/src/Linux:Vpnc_Restart_Script.ascii b/src/Linux:Vpnc_Restart_Script.ascii
new file mode 100644
index 0000000..d7f7d0a
--- /dev/null
+++ b/src/Linux:Vpnc_Restart_Script.ascii
@@ -0,0 +1,47 @@
+Linux: VPNC Restart Script
+==========================
+:author: Aaron Ball
+:email: nullspoon@iohq.net
+
+
+== {doctitle}
+
+The VPN at my company is very... spotty... at best. When working from home, it
+used to boot you about once every hour. For whatever reason though, it has
+recently started booting sessions every five minutes. Now, the solution is of
+course to speak with our networking folks rather than to write a script to fix
+the issue on a client by client basis. Unfortunately, due to the culture and
+various political situations, the networking folks will not fix this because
+they don't believe it's an issue. All opinionattion aside, this sounds like an
+opportunity for a nice shell script.
+
+To start things off, on my Linux box I use vpnc from the command line as I
+don't want to install network manager due to additional resource consumption
+(albeit a very small amount). That said, throw the following script in
++~/bin/vpnconnect+ and include +~/bin+ in your PATH variable (+export
+PATH=~/bin:$\{PATH}+).
+
+[[source]]
+== Source
+
+_Edit_: Found a pretty sizeable flaw in my script. Pulled the source until I
+can sort it out.
+
+
+[[order-of-operations]]
+== Order of Operations
+
+. Check if vpnc is already running
+ * Start if it is not running
+. Start an infinite loop
+ . Sleep 5 to keep from using too many resources
+ . Check cpu time on pid - if it is greater than 1 minute
+ * Kill pid and restart vpnc
+
+
+
+Category:Linux
+Category:Drafts
+
+
+// vim: set syntax=asciidoc:

Generated by cgit