initial upload

Author: Botspot

expect-scripts/dropbox.exp

@@ -0,0 +1,71 @@
+#!/usr/bin/expect -f
+#
+# This Expect script was generated by autoexpect on Sun Jul 25 20:00:46 2021
+# Expect and autoexpect were both written by Don Libes, NIST.
+#
+# Note that autoexpect does not guarantee a working script.  It
+# necessarily has to guess about certain things.  Two reasons a script
+# might fail are:
+#
+# 1) timing - A surprising number of programs (rn, ksh, zsh, telnet,
+# etc.) and devices discard or ignore keystrokes that arrive "too
+# quickly" after prompts.  If you find your new script hanging up at
+# one spot, try adding a short sleep just before the previous send.
+# Setting "force_conservative" to 1 (see below) makes Expect do this
+# automatically - pausing briefly before sending each character.  This
+# pacifies every program I know of.  The -c flag makes the script do
+# this in the first place.  The -C flag allows you to define a
+# character to toggle this mode off and on.
+
+set force_conservative 0  ;# set to 1 to force conservative mode even if
+			  ;# script wasn't run conservatively originally
+if {$force_conservative} {
+	set send_slow {1 .1}
+	proc send {ignore arg} {
+		sleep .1
+		exp_send -s -- $arg
+	}
+}
+
+#
+# 2) differing output - Some programs produce different output each time
+# they run.  The "date" command is an obvious example.  Another is
+# ftp, if it produces throughput statistics at the end of a file
+# transfer.  If this causes a problem, delete these patterns or replace
+# them with wildcards.  An alternative is to use the -p flag (for
+# "prompt") which makes Expect only look for the last line of output
+# (i.e., the prompt).  The -P flag allows you to define a character to
+# toggle this mode off and on.
+#
+# Read the man page for more info.
+#
+# -Don
+
+
+set timeout -1
+spawn rclone config
+match_max 100000
+expect -exact "e/n/d/r/c/s/q> "
+send -- "n\r"
+expect -exact "name> "
+send -- "$env(drivename)\r"
+expect -exact "Storage> "
+send -- "dropbox\r"
+expect -exact "client_id> "
+send -- "\r"
+expect -exact "client_secret> "
+send -- "\r"
+
+#Edit advanced config?
+expect -exact "y/n> "
+send -- "n\r"
+
+#Use auto config?
+expect -exact "y/n> "
+send -- "y\r"
+
+expect -exact "y/e/d> "
+send -- "y\r"
+expect -exact "e/n/d/r/c/s/q> "
+send -- "q\r"
+expect eof

expect-scripts/gdrive.exp

@@ -0,0 +1,83 @@
+#!/usr/bin/expect -f
+#
+# This Expect script was generated by autoexpect on Sun Jul 25 17:43:41 2021
+# Expect and autoexpect were both written by Don Libes, NIST.
+#
+# Note that autoexpect does not guarantee a working script.  It
+# necessarily has to guess about certain things.  Two reasons a script
+# might fail are:
+#
+# 1) timing - A surprising number of programs (rn, ksh, zsh, telnet,
+# etc.) and devices discard or ignore keystrokes that arrive "too
+# quickly" after prompts.  If you find your new script hanging up at
+# one spot, try adding a short sleep just before the previous send.
+# Setting "force_conservative" to 1 (see below) makes Expect do this
+# automatically - pausing briefly before sending each character.  This
+# pacifies every program I know of.  The -c flag makes the script do
+# this in the first place.  The -C flag allows you to define a
+# character to toggle this mode off and on.
+
+set force_conservative 0  ;# set to 1 to force conservative mode even if
+			  ;# script wasn't run conservatively originally
+if {$force_conservative} {
+	set send_slow {1 .1}
+	proc send {ignore arg} {
+		sleep .1
+		exp_send -s -- $arg
+	}
+}
+
+#
+# 2) differing output - Some programs produce different output each time
+# they run.  The "date" command is an obvious example.  Another is
+# ftp, if it produces throughput statistics at the end of a file
+# transfer.  If this causes a problem, delete these patterns or replace
+# them with wildcards.  An alternative is to use the -p flag (for
+# "prompt") which makes Expect only look for the last line of output
+# (i.e., the prompt).  The -P flag allows you to define a character to
+# toggle this mode off and on.
+#
+# Read the man page for more info.
+#
+# -Don
+
+
+set timeout -1
+spawn rclone config
+match_max 100000
+expect "e/n/d/r/c/s/q> "
+send -- "n\r"
+expect "name> "
+send -- "$env(drivename)\r"
+expect "Storage> "
+send -- "drive\r"
+expect "client_id> "
+send -- "\r"
+expect "client_secret> "
+send -- "\r"
+expect "scope> "
+send -- "drive\r"
+expect "root_folder_id> "
+send -- "\r"
+expect "service_account_file> "
+send -- "\r"
+
+#edit advanced config?
+expect "y/n> "
+send -- "n\r"
+
+#use auto config?
+expect "y/n> "
+send -- "y\r"
+#Configure this as a Shared Drive (Team Drive)?
+expect "y/n> "
+send -- "n\r"
+
+#Is this ok?
+expect "y/e/d> "
+send -- "y\r"
+
+#Quit
+expect "e/n/d/r/c/s/q> "
+send -- "q\r"
+expect eof

expect-scripts/onedrive.exp

@@ -0,0 +1,78 @@
+#!/usr/bin/expect -f
+#
+# This Expect script was generated by autoexpect on Sun Jul 25 19:55:26 2021
+# Expect and autoexpect were both written by Don Libes, NIST.
+#
+# Note that autoexpect does not guarantee a working script.  It
+# necessarily has to guess about certain things.  Two reasons a script
+# might fail are:
+#
+# 1) timing - A surprising number of programs (rn, ksh, zsh, telnet,
+# etc.) and devices discard or ignore keystrokes that arrive "too
+# quickly" after prompts.  If you find your new script hanging up at
+# one spot, try adding a short sleep just before the previous send.
+# Setting "force_conservative" to 1 (see below) makes Expect do this
+# automatically - pausing briefly before sending each character.  This
+# pacifies every program I know of.  The -c flag makes the script do
+# this in the first place.  The -C flag allows you to define a
+# character to toggle this mode off and on.
+
+set force_conservative 0  ;# set to 1 to force conservative mode even if
+			  ;# script wasn't run conservatively originally
+if {$force_conservative} {
+	set send_slow {1 .1}
+	proc send {ignore arg} {
+		sleep .1
+		exp_send -s -- $arg
+	}
+}
+
+#
+# 2) differing output - Some programs produce different output each time
+# they run.  The "date" command is an obvious example.  Another is
+# ftp, if it produces throughput statistics at the end of a file
+# transfer.  If this causes a problem, delete these patterns or replace
+# them with wildcards.  An alternative is to use the -p flag (for
+# "prompt") which makes Expect only look for the last line of output
+# (i.e., the prompt).  The -P flag allows you to define a character to
+# toggle this mode off and on.
+#
+# Read the man page for more info.
+#
+# -Don
+
+
+set timeout -1
+spawn rclone config
+match_max 100000
+expect -exact "e/n/d/r/c/s/q> "
+send -- "n\r"
+expect -exact "name> "
+send -- "$env(drivename)\r"
+expect -exact "Storage> "
+send -- "onedrive\r"
+expect -exact "client_id> "
+send -- "\r"
+expect -exact "client_secret> "
+send -- "\r"
+
+#Edit advanced config?
+expect -exact "y/n> "
+send -- "n\r"
+
+#Use auto config?
+expect -exact "y/n> "
+send -- "y\r"
+expect -exact "Your choice> "
+send -- "onedrive\r"
+expect -exact "Chose drive to use:> "
+send -- "0\r"
+
+#Is that okay?
+expect -exact "y/n> "
+send -- "y\r"
+expect -exact "y/e/d> "
+send -- "y\r"
+expect -exact "e/n/d/r/c/s/q> "
+send -- "q\r"
+expect eof