I did some experimenting... but it's not always the case, it depends on what you are doing. But doing this with simple counting results:
And for fun lol....
@scottalanmiller said in Script to Move and Decrypt Files in a Specified Directory:
for i in $(ls /orig/directory/*.gpg); do
gpg --decrypt $i > /new/directory/$i.txt
done
Here it is as a command....
for i in $(ls /orig/directory/*.gpg); do gpg --decrypt $i > /new/directory/$i.txt; done
@matteo-nunziati said in bash script help splitting string:
try this:
# initializing agi variables
declare -a array
while read -e ARG && [ "$ARG" ] ; do
array=(` echo "$ARG" | sed -e 's/://'`)
export ${array[0]}=${array[@]:1}
#next added line for debug only. comment this out in prod.
echo "${array[0]}=${array[@]:1}"
done
if you want to "slice" an array use the syntax: ${array[@]:from:to}, not providing the 'to' arg means go up to the end of array.
source here.
Almost right. Because of the export command parsing spaces, I needed to stick it in a variable first.
# Variable to hold the details for the log file
DUMPARG=" Begin Argument dump:\n"
# Create an Array to hold the results of the loop
declare -a array
# Loop through the AGI variables
while read -e ARG && [ "$ARG" ] ; do
# Dump them into an array, after removing the :
array=(` echo $ARG | sed -e 's/://'`)
# take the array and create a variable from the first element put the rest as the value
# value must be put into a holding variable to parse correctly by the export command
val=${array[@]:1}
export ${array[0]}="$val"
# Dump them into a string for the log file
DUMPARG="$DUMPARG $ARG\n"
done
This is what I do when I use nohup.
I usually create a file with the current pid just in case I need to stop it.
nohup wget 'https://example.com/fedora.iso' > wget_fedora.log 2>&1 &
echo $! > wget_fedora_pid.txt
kill -9 `cat wget_fedora_pid.txt`
rm wget_fedora_pid.txt
@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:
@matteo-nunziati said in Tracking Down Ubuntu BASH Session Closing:
@scottalanmiller said in Tracking Down Ubuntu BASH Session Closing:
If I use zsh, I'm good. If I enter BASH from zsh, I get kicked out after several seconds. Definitely is something to do with BASH.
Stupid tryout: use bash and then enter zsh before being kicked out. Still out?
To understand if it is the firing of bash itself or the stay in bash...
No, the underlying bash remains until the ZSH closes. Same as if you were running top from it, for example.
So basically bash is able to run long running jobs with your user...
It's the interactivity with the shell to be broken... Meh.
Sorry the thread is long, did you mention any test from zsh with:
Bash <-- ok this kills the session
Bash -i any difference???
Bash -l ???
bash --norc
bash --noprofile
From bashman page
@JaredBusch : I'm not certain if this fits the bill, but what about the "diff" command? Of course, this does nothing to sync the files but does offer a way to simply compare the directories.
diff -rs manxam jaredbusch
This will get you :
Files /home/manxam/TEST and /home/jaredbusch/TEST are identical
Only in /home/manxam: i_am_manxam
Only in /home/jaredbusch: you_are_jared
Just used this again today, as another script I have had this attribute.
Not sure when the attribute was written to the script though. But it's working now.
This is the full error.
/bin/sh: bad interpreter: Operation not permitted
@penguinwrangler
Good work! I admit I would have been to lazy to go through all that. I would just have written a program to deal with it straight up instead instead of trying to use nix commands and scripting. Anything to avoid "escape hell" as I like to call it.
@stacksofplates said in A script to pull updates from GH or use History:
@DustinB3403 said in A script to pull updates from GH or use History:
So to clarify here, the goal is to allow admins an easy way to pull the most current update script. Not to run it for them on a set schedule.
(reason being is if we auto-force an update, and that update breaks their system, I don't want to have that on my mind)
I don't understand the hangup here. The cron job I pasted above does not update anything. It doesn't run any scripts. It doesn't force anything. Where this is coming from I have no idea.
This is from sidebar conversations regarding the topic. It has nothing to do with the cron job you posted.
I guess I could do a wildcard at the beginning and end of whatever I'm searching for with killall but that freaks me out a little. I could accidentally do a lot of damage with that.
@mlnews said:
And this is the current site for the project...
https://github.com/Pash-Project/Pash
I love it when people port garbage to other platforms
@scottalanmiller said:
Best practice, which almost no one follows, is to use explicit paths in scripts rather than implicit. then you don't need that at all.
I guess that makes 100% sense since you have to start the script with an absolute path ha.
And here is a sample output:
./counter.sh five six four three two one seven twenty onehundred eleven ten do a deer a female deer and that is how the cookie crumbles and i am pretty sure that you will find that this is a really useful bash script no matter how many things that you want to pass into its parameter fields
1 letters: 4
2 letters: 6
3 letters: 12
4 letters: 17
5 letters: 2
6 letters: 11
8 letters: 1
9 letters: 1
10 letters: 1
