diff --git a/sql/hpr.sql b/sql/hpr.sql
index dd31ce4..4dcf357 100644
--- a/sql/hpr.sql
+++ b/sql/hpr.sql
@@ -20467,7 +20467,8 @@ INSERT INTO `eps` (`id`, `date`, `title`, `duration`, `summary`, `notes`, `hosti
(3982,'2023-11-07','Conversation with ChatGPT',218,'Conversation with ChatGPT about EU Cookie banners','The\nfollowing conversation is from my query to ChatGPT
\nconversation.html
\n',318,0,0,'CC-BY-SA','ChatGPT, EU, GDPR, cookies',0,0,1),
(3983,'2023-11-08','ChatGPT Output is not compatible with CC-BY-SA',536,'Ken is not a lawyer but is fairly sure that ChatGPT is not compatible with Creative Commons','When uploading to HPR you are\nYou are\nagreeing to license your show CC-BY-SA.
\n\nAll our shows are now released under a Creative Commons\nAttribution-ShareAlike 4.0 International (CC BY-SA 4.0) license, which\nmeans that while you continue to retain the copyright to your show, you\nare allowing us (and everyone else) to use it provided we give you\nattribution and that we release it under the same license. Click the\nlink for more information.
\n
\nThe\nCreative\nCommons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)\nlicense itself says that sharing (the S in CC-BY-SA), allows you to\n\"copy and redistribute the material in any medium or format for any\npurpose, even commercially\".
\nOn the face of it the\nOpenAI\nChatGPT Terms of use seem similar, with Section 3 saying \"you can\nuse Content for any purpose, including commercial purposes\".\nUnfortunately they then go on to say \"Subject to your compliance with\nthese Terms\":
\n 3. Content\n\n (a) Your Content. You may provide input to the Services (“Input”), and\n receive output generated and returned by the Services based on the Input\n (“Output”). Input and Output are collectively “Content.” As between the\n parties and to the extent permitted by applicable law, you own all\n Input. Subject to your compliance with these Terms, OpenAI hereby\n assigns to you all its right, title and interest in and to Output. This\n means you can use Content for any purpose, including commercial purposes\n such as sale or publication, if you comply with these Terms. OpenAI may\n use Content to provide and maintain the Services, comply with applicable\n law, and enforce our policies. You are responsible for Content,\n including for ensuring that it does not violate any applicable law or\n these Terms.
\nThe same document lists some restrictions...
\n 2. Usage Requirements\n\n (c) Restrictions. You may not (i) use the Services in a way that\n infringes, misappropriates or violates any person’s rights; (ii) reverse\n assemble, reverse compile, decompile, translate or otherwise attempt to\n discover the source code or underlying components of models, algorithms,\n and systems of the Services (except to the extent such restrictions are\n contrary to applicable law); (iii) use output from the Services to\n develop models that compete with OpenAI;
\n... while the\nUsage policies\nlist more.
\nSo in my opinion, and I am not a lawyer (IANAL) the\nOpenAI\nChatGPT Terms of use is not compatible with the\nCreative\nCommons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0)\nlicense.
\nYou can of course refer to ChatGPT as you would any other non\nCreative Commons site.
\nIf you disagree or would like to weigh in please discuss this on the\nmail list.
\n',30,0,0,'CC-BY-SA','CreativeCommons, CC-BY-SA, ChatGPT, HPR, CC',0,0,1),
(3984,'2023-11-09','Whoppers. How Archer72 and I made moonshine. Volume one.',1730,'Sgoti assists Archer72 with his crazy plan to make moonshine.','What is a whopper?
\nan\nextravagant or monstrous lie
\na\nbig lie
\n
\nA work of Fiction\nis any creative work, chiefly any narrative work, portraying\nindividuals, events, or places that are imaginary or in ways that are\nimaginary.
\n
\n\n- Source: Moonshine is\nhigh-proof liquor, generally whiskey, traditionally made, or at least\ndistributed, illegally.
\n \n- Supporting Source: busthead\n(bust-head). noun. Cheap, strong liquor, usually of the illegal\nvariety. Moonshine. Hooch. Poteen. Pop-skull. Bumblings. The origin is\nobvious to anyone who’s hit the busthead a little hard themselves.
\n \n
\nThe Bureau of Alcohol, Tobacco, Firearms and Explosives (BATFE),\ncommonly referred to as the ATF, is a domestic law enforcement agency\nwithin the United States Department of Justice.
\n
\n\n- Source: Archer72
\n \n- Source: Mechatroniac
\n \n- Source: Klaatu
\n \n- Source: Zen_Floater2
\n \n
\n',391,0,1,'CC-BY-SA','Whoppers, Moonshine, Archer72',0,0,1),
-(3985,'2023-11-10','Bash snippet - be careful when feeding data to loops',1644,'A loop in a pipeline runs in a subshell','\nOverview
\nRecently Ken Fallon did a show on HPR, number\n3962, in which he used a Bash\npipeline of multiple commands feeding their output into a\nwhile loop. In the loop he processed the lines produced by\nthe pipeline and used what he found to download audio files belonging to\na series with wget.
\nThis was a great show and contained some excellent advice, but the\nuse of the format:
\npipeline | while read variable; do ...
\nreminded me of the \"gotcha\" I mentioned in my own show\n2699.
\nI thought it might be a good time to revisit this subject.
\nSo, what\'s the problem?
\nThe problem can be summarised as a side effect of pipelines.
\nWhat are pipelines?
\nPipelines are an amazingly useful feature of Bash (and other shells).\nThe general format is:
\ncommand1 | command2 ...
\nHere command1 runs in a subshell and produces output (on\nits standard output) which is connected via the pipe symbol\n(|) to command2 where it becomes its\nstandard input. Many commands can be linked together in this\nway to achieve some powerful combined effects.
\nA very simple example of a pipeline might be:
\n$ printf 'World\nHello\n' | sort\nHello\nWorld
\nThe printf command (≡\'command1\') writes two\nlines (separated by newlines) on standard output and this is\npassed to the sort command\'s standard input\n(≡\'command2\') which then sorts these lines\nalphabetically.
\nCommands in the pipeline can be more complex than this, and in the\ncase we are discussing we can include a loop command such as\nwhile.
\nFor example:
\n$ printf 'World\nHello\n' | sort | while read line; do echo "($line)"; done\n(Hello)\n(World)
\nHere, each line output by the sort command is read into\nthe variable line in the while loop and is\nwritten out enclosed in parentheses.
\nNote that the loop is written on one line. The semi-colons are used\ninstead of the equivalent newlines.
\nVariables and subshells
\nWhat if the lines output by the loop need to be numbered?
\n$ i=0; printf 'World\nHello\n' | sort | while read line; do ((i++)); echo "$i) $line"; done\n1) Hello\n2) World
\nHere the variable \'i\' is set to zero before the\npipeline. It could have been done on the line before of course. In the\nwhile loop the variable is incremented on each iteration\nand included in the output.
\nYou might expect \'i\' to be 2 once the loop exits but it\nis not. It will be zero in fact.
\nThe reason is that there are two \'i\' variables. One is\ncreated when it\'s set to zero at the start before the pipeline. The\nother one is created in the loop as a \"clone\". The expression:
\n((i++))
\nboth creates the variable (where it is a copy of the one in the\nparent shell) and increments it.
\nWhen the subshell in which the loop runs completes, it will delete\nthis version of \'i\' and the original one will simply\ncontain the zero that it was originally set to.
\nYou can see what happens in this slightly different example:
\n$ i=1; printf 'World\nHello\n' | sort | while read line; do ((i++)); echo "$i) $line"; done\n2) Hello\n3) World\n$ echo $i\n1
\nThese examples are fine, assuming the contents of variable\n\'i\' incremented in the loop are not needed outside it.
\nThe thing to remember is that the same variable name used in a\nsubshell is a different variable; it is initialised with the value of\nthe \"parent\" variable but any changes are not passed back.
\nHow to avoid the\nloss of changes in the loop
\nTo solve this the loop needs to be run in the original shell, not a\nsubshell. The pipeline which is being read needs to be attached to the\nloop in a different way:
\n$ i=0; while read line; do ((i++)); echo "$i) $line"; done < <(printf 'World\nHello\n' | sort)\n1) Hello\n2) World\n$ echo $i\n2
\nWhat is being used here is process\nsubstitution. A list of commands or pipelines are enclosed with\nparentheses and a \'less than\' sign prepended to the list\n(with no intervening spaces). This is functionally equivalent to a\n(temporary) file of data.
\nThe redirection feature allows for data being read from a\nfile in a loop. The general format of the command is:
\nwhile read variable\n do\n # Use the variable\n done < file
\nUsing process substitution instead of a file will achieve what is\nrequired if computations are being done in the loop and the results are\nwanted after it has finished.
\nBeware of this type of\nconstruct
\nThe following one-line command sequence looks similar to the version\nusing process substitution, but is just another form of pipeline:
\n$ i=0; while read line; do echo $line; ((i++)); done < /etc/passwd | head -n 5; echo $i\nroot:x:0:0:root:/root:/bin/bash\ndaemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin\nbin:x:2:2:bin:/bin:/usr/sbin/nologin\nsys:x:3:3:sys:/dev:/usr/sbin/nologin\nsync:x:4:65534:sync:/bin:/bin/sync\n0
\nThis will display the first 5 lines of the file but does it by\nreading and writing the entire file and only showing the first 5 lines\nof what is written by the loop.
\nWhat is more, because the while is in a subshell in a\npipeline changes to variable \'i\' will be lost.
\nAdvice
\n\nUse the pipe-connected-to-loop layout if you\'re aware of\nthe pitfalls, but will not be affected by them.
Use the read-from-process-substitution format if you\nwant your loop to be complex and to read and write variables in the\nscript.
Personally, I always use the second form in scripts, but if I\'m\nwriting a temporary one-line thing on the command line I usually use the\nfirst form.
\nTracing pipelines (advanced)
\nI have always wondered about processes in Unix. The process you log\nin to, normally called a shell runs a command language\ninterpreter that executes commands read from the standard input or\nfrom a file. There are several such interpreters available, but we\'re\ndealing with bash here.
\nProcesses are fairly lightweight entities in Unix/Linux. They can be\ncreated and destroyed quickly, with minimal overhead. I used to work\nwith Digital Equipment Corporation\'s OpenVMS operating system\nwhich also uses processes - but these are much more expensive to create\nand destroy, and therefore slow and less readily used!
\nBash pipelines, as discussed, use subshells. The description\nin the Bash man page says:
\n\nEach command in a multi-command pipeline, where pipes are created, is\nexecuted in a subshell, which is a separate process.
\n
\nSo a subshell in this context is basically another child\nprocess of the main login process (or other parent process), running\nBash.
\nProcesses (subshells) can be created in other ways. One is to place a\ncollection of commands in parentheses. These can be simple Bash\ncommands, separated by semi-colons, or pipelines. For example:
\n$ (echo "World"; echo "Hello") | sort\nHello\nWorld
\nHere the strings \"World\" and \"Hello\", each\nfollowed by a newline are created in a subshell and written to standard\noutput. These strings are piped to sort and the end result\nis as shown.
\nNote that this is different from this example:
\n$ echo "World"; echo "Hello" | sort\nWorld\nHello
\nIn this case \"World\" is written in a separate command,\nthen \"Hello\" is written to a pipeline. All\nsort sees is the output from the second echo,\nwhich explains the output.
\nEach process has a unique numeric id value (the process id\nor PID). These can be seen with tools like ps or\nhtop. Each process holds its own PID in a Bash variable\ncalled BASHPID.
\nKnowing all of this I decided to modify Ken\'s script from show\n3962 to show the processes being created - mainly for my interest,\nto get a better understanding of how Bash works. I am including it here\nin case it may be of interest to others.
\n#!/bin/bash\n\nseries_url="https://hackerpublicradio.org/hpr_mp3_rss.php?series=42&full=1&gomax=1"\ndownload_dir="./"\n\npidfile="/tmp/hpr3962.sh.out"\ncount=0\n\necho "Starting PID is $BASHPID" > $pidfile\n\n(echo "[1] $BASHPID" >> "$pidfile"; wget -q "${series_url}" -O -) |\\n (echo "[2] $BASHPID" >> "$pidfile"; xmlstarlet sel -T -t -m 'rss/channel/item' -v 'concat(enclosure/@url, "→", title)' -n -) |\\n (echo "[3] $BASHPID" >> "$pidfile"; sort) |\\n while read -r episode; do\n\n [ $count -le 1 ] && echo "[4] $BASHPID" >> "$pidfile"\n ((count++))\n\n url="$( echo "${episode}" | awk -F '→' '{print $1}' )"\n ext="$( basename "${url}" )"\n title="$( echo "${episode}" | awk -F '→' '{print $2}' | sed -e 's/[^A-Za-z0-9]/_/g' )"\n #wget "${url}" -O "${download_dir}/${title}.${ext}"\n done\n\necho "Final value of \$count = $count"\necho "Run 'cat $pidfile' to see the PID numbers"
\nThe point of doing this is to get information about the pipeline\nwhich feeds data into the while loop. I kept the rest\nintact but commented out the wget command.
\nFor each component of the pipeline I added an echo\ncommand and enclosed it and the original command in parentheses, thus\nmaking a multi-command process. The echo commands write a\nfixed number so you can tell which one is being executed, and it also\nwrites the contents of BASHPID.
\nThe whole thing writes to a temporary file\n/tmp/hpr3962.sh.out which can be examined once the script\nhas finished.
\nWhen the script is run it writes the following:
\n$ ./hpr3962.sh\nFinal value of $count = 0\nRun 'cat /tmp/hpr3962.sh.out' to see the PID numbers
\nThe file mentioned contains:
\nStarting PID is 80255\n[1] 80256\n[2] 80257\n[3] 80258\n[4] 80259\n[4] 80259
\nNote that the PID values are incremental. There is no guarantee that\nthis will be so. It will depend on whatever else the machine is\ndoing.
\nMessage number 4 is the same for every loop iteration, so I stopped\nit being written after two instances.
\nThe initial PID is the process running the script, not the login\n(parent) PID. You can see that each command in the pipeline runs in a\nseparate process (subshell), including the loop.
\nGiven that a standard pipeline generates a process per command, I was\nslightly surprised that the PID numbers were consecutive. It seems that\nBash optimises things so that only one process is run for each element\nof the pipe. I expect that it would be possible for more processes to be\ncreated by having pipelines within these parenthesised lists, but I\nhaven\'t tried it!
\nI found this test script quite revealing. I hope you find it useful\ntoo.
\nLinks
\n\n- Bash pipelines:\n
\n- GNU\nBash manual: 3.2.3 Pipelines
\n
\n
\n\n- Bash loops:\n
\n- GNU\nBash manual: 3.2.5.1 Looping Constructs
\n
\n
\n\n- Bash process substitution:\n
\n- GNU\nBash manual: 3.5.6 Process Substitution
\n
\n
\n\n- HPR shows referenced:\n
\n- hpr2045 ::\nSome other Bash tips
\n- hpr2699 ::\nBash Tips - 15
\n- hpr3962 ::\nIt\'s your data
\n
\n
\n\n',225,42,1,'CC-BY-SA','Bash,loop,process,shell',0,0,1);
+(3985,'2023-11-10','Bash snippet - be careful when feeding data to loops',1644,'A loop in a pipeline runs in a subshell','\nOverview
\nRecently Ken Fallon did a show on HPR, number\n3962, in which he used a Bash\npipeline of multiple commands feeding their output into a\nwhile loop. In the loop he processed the lines produced by\nthe pipeline and used what he found to download audio files belonging to\na series with wget.
\nThis was a great show and contained some excellent advice, but the\nuse of the format:
\npipeline | while read variable; do ...
\nreminded me of the \"gotcha\" I mentioned in my own show\n2699.
\nI thought it might be a good time to revisit this subject.
\nSo, what\'s the problem?
\nThe problem can be summarised as a side effect of pipelines.
\nWhat are pipelines?
\nPipelines are an amazingly useful feature of Bash (and other shells).\nThe general format is:
\ncommand1 | command2 ...
\nHere command1 runs in a subshell and produces output (on\nits standard output) which is connected via the pipe symbol\n(|) to command2 where it becomes its\nstandard input. Many commands can be linked together in this\nway to achieve some powerful combined effects.
\nA very simple example of a pipeline might be:
\n$ printf 'World\nHello\n' | sort\nHello\nWorld
\nThe printf command (≡\'command1\') writes two\nlines (separated by newlines) on standard output and this is\npassed to the sort command\'s standard input\n(≡\'command2\') which then sorts these lines\nalphabetically.
\nCommands in the pipeline can be more complex than this, and in the\ncase we are discussing we can include a loop command such as\nwhile.
\nFor example:
\n$ printf 'World\nHello\n' | sort | while read line; do echo "($line)"; done\n(Hello)\n(World)
\nHere, each line output by the sort command is read into\nthe variable line in the while loop and is\nwritten out enclosed in parentheses.
\nNote that the loop is written on one line. The semi-colons are used\ninstead of the equivalent newlines.
\nVariables and subshells
\nWhat if the lines output by the loop need to be numbered?
\n$ i=0; printf 'World\nHello\n' | sort | while read line; do ((i++)); echo "$i) $line"; done\n1) Hello\n2) World
\nHere the variable \'i\' is set to zero before the\npipeline. It could have been done on the line before of course. In the\nwhile loop the variable is incremented on each iteration\nand included in the output.
\nYou might expect \'i\' to be 2 once the loop exits but it\nis not. It will be zero in fact.
\nThe reason is that there are two \'i\' variables. One is\ncreated when it\'s set to zero at the start before the pipeline. The\nother one is created in the loop as a \"clone\". The expression:
\n((i++))
\nboth creates the variable (where it is a copy of the one in the\nparent shell) and increments it.
\nWhen the subshell in which the loop runs completes, it will delete\nthis version of \'i\' and the original one will simply\ncontain the zero that it was originally set to.
\nYou can see what happens in this slightly different example:
\n$ i=1; printf 'World\nHello\n' | sort | while read line; do ((i++)); echo "$i) $line"; done\n2) Hello\n3) World\n$ echo $i\n1
\nThese examples are fine, assuming the contents of variable\n\'i\' incremented in the loop are not needed outside it.
\nThe thing to remember is that the same variable name used in a\nsubshell is a different variable; it is initialised with the value of\nthe \"parent\" variable but any changes are not passed back.
\nHow to avoid the\nloss of changes in the loop
\nTo solve this the loop needs to be run in the original shell, not a\nsubshell. The pipeline which is being read needs to be attached to the\nloop in a different way:
\n$ i=0; while read line; do ((i++)); echo "$i) $line"; done < <(printf 'World\nHello\n' | sort)\n1) Hello\n2) World\n$ echo $i\n2
\nWhat is being used here is process\nsubstitution. A list of commands or pipelines are enclosed with\nparentheses and a \'less than\' sign prepended to the list\n(with no intervening spaces). This is functionally equivalent to a\n(temporary) file of data.
\nThe redirection feature allows for data being read from a\nfile in a loop. The general format of the command is:
\nwhile read variable\n do\n # Use the variable\n done < file
\nUsing process substitution instead of a file will achieve what is\nrequired if computations are being done in the loop and the results are\nwanted after it has finished.
\nBeware of this type of\nconstruct
\nThe following one-line command sequence looks similar to the version\nusing process substitution, but is just another form of pipeline:
\n$ i=0; while read line; do echo $line; ((i++)); done < /etc/passwd | head -n 5; echo $i\nroot:x:0:0:root:/root:/bin/bash\ndaemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin\nbin:x:2:2:bin:/bin:/usr/sbin/nologin\nsys:x:3:3:sys:/dev:/usr/sbin/nologin\nsync:x:4:65534:sync:/bin:/bin/sync\n0
\nThis will display the first 5 lines of the file but does it by\nreading and writing the entire file and only showing the first 5 lines\nof what is written by the loop.
\nWhat is more, because the while is in a subshell in a\npipeline changes to variable \'i\' will be lost.
\nAdvice
\n\nUse the pipe-connected-to-loop layout if you\'re aware of\nthe pitfalls, but will not be affected by them.
Use the read-from-process-substitution format if you\nwant your loop to be complex and to read and write variables in the\nscript.
Personally, I always use the second form in scripts, but if I\'m\nwriting a temporary one-line thing on the command line I usually use the\nfirst form.
\nTracing pipelines (advanced)
\nI have always wondered about processes in Unix. The process you log\nin to, normally called a shell runs a command language\ninterpreter that executes commands read from the standard input or\nfrom a file. There are several such interpreters available, but we\'re\ndealing with bash here.
\nProcesses are fairly lightweight entities in Unix/Linux. They can be\ncreated and destroyed quickly, with minimal overhead. I used to work\nwith Digital Equipment Corporation\'s OpenVMS operating system\nwhich also uses processes - but these are much more expensive to create\nand destroy, and therefore slow and less readily used!
\nBash pipelines, as discussed, use subshells. The description\nin the Bash man page says:
\n\nEach command in a multi-command pipeline, where pipes are created, is\nexecuted in a subshell, which is a separate process.
\n
\nSo a subshell in this context is basically another child\nprocess of the main login process (or other parent process), running\nBash.
\nProcesses (subshells) can be created in other ways. One is to place a\ncollection of commands in parentheses. These can be simple Bash\ncommands, separated by semi-colons, or pipelines. For example:
\n$ (echo "World"; echo "Hello") | sort\nHello\nWorld
\nHere the strings \"World\" and \"Hello\", each\nfollowed by a newline are created in a subshell and written to standard\noutput. These strings are piped to sort and the end result\nis as shown.
\nNote that this is different from this example:
\n$ echo "World"; echo "Hello" | sort\nWorld\nHello
\nIn this case \"World\" is written in a separate command,\nthen \"Hello\" is written to a pipeline. All\nsort sees is the output from the second echo,\nwhich explains the output.
\nEach process has a unique numeric id value (the process id\nor PID). These can be seen with tools like ps or\nhtop. Each process holds its own PID in a Bash variable\ncalled BASHPID.
\nKnowing all of this I decided to modify Ken\'s script from show\n3962 to show the processes being created - mainly for my interest,\nto get a better understanding of how Bash works. I am including it here\nin case it may be of interest to others.
\n#!/bin/bash\n\nseries_url="https://hackerpublicradio.org/hpr_mp3_rss.php?series=42&full=1&gomax=1"\ndownload_dir="./"\n\npidfile="/tmp/hpr3962.sh.out"\ncount=0\n\necho "Starting PID is $BASHPID" > $pidfile\n\n(echo "[1] $BASHPID" >> "$pidfile"; wget -q "${series_url}" -O -) |\\n (echo "[2] $BASHPID" >> "$pidfile"; xmlstarlet sel -T -t -m 'rss/channel/item' -v 'concat(enclosure/@url, "→", title)' -n -) |\\n (echo "[3] $BASHPID" >> "$pidfile"; sort) |\\n while read -r episode; do\n\n [ $count -le 1 ] && echo "[4] $BASHPID" >> "$pidfile"\n ((count++))\n\n url="$( echo "${episode}" | awk -F '→' '{print $1}' )"\n ext="$( basename "${url}" )"\n title="$( echo "${episode}" | awk -F '→' '{print $2}' | sed -e 's/[^A-Za-z0-9]/_/g' )"\n #wget "${url}" -O "${download_dir}/${title}.${ext}"\n done\n\necho "Final value of \$count = $count"\necho "Run 'cat $pidfile' to see the PID numbers"
\nThe point of doing this is to get information about the pipeline\nwhich feeds data into the while loop. I kept the rest\nintact but commented out the wget command.
\nFor each component of the pipeline I added an echo\ncommand and enclosed it and the original command in parentheses, thus\nmaking a multi-command process. The echo commands write a\nfixed number so you can tell which one is being executed, and it also\nwrites the contents of BASHPID.
\nThe whole thing writes to a temporary file\n/tmp/hpr3962.sh.out which can be examined once the script\nhas finished.
\nWhen the script is run it writes the following:
\n$ ./hpr3962.sh\nFinal value of $count = 0\nRun 'cat /tmp/hpr3962.sh.out' to see the PID numbers
\nThe file mentioned contains:
\nStarting PID is 80255\n[1] 80256\n[2] 80257\n[3] 80258\n[4] 80259\n[4] 80259
\nNote that the PID values are incremental. There is no guarantee that\nthis will be so. It will depend on whatever else the machine is\ndoing.
\nMessage number 4 is the same for every loop iteration, so I stopped\nit being written after two instances.
\nThe initial PID is the process running the script, not the login\n(parent) PID. You can see that each command in the pipeline runs in a\nseparate process (subshell), including the loop.
\nGiven that a standard pipeline generates a process per command, I was\nslightly surprised that the PID numbers were consecutive. It seems that\nBash optimises things so that only one process is run for each element\nof the pipe. I expect that it would be possible for more processes to be\ncreated by having pipelines within these parenthesised lists, but I\nhaven\'t tried it!
\nI found this test script quite revealing. I hope you find it useful\ntoo.
\nLinks
\n\n- Bash pipelines:\n
\n- GNU\nBash manual: 3.2.3 Pipelines
\n
\n
\n\n- Bash loops:\n
\n- GNU\nBash manual: 3.2.5.1 Looping Constructs
\n
\n
\n\n- Bash process substitution:\n
\n- GNU\nBash manual: 3.5.6 Process Substitution
\n
\n
\n\n- HPR shows referenced:\n
\n- hpr2045 ::\nSome other Bash tips
\n- hpr2699 ::\nBash Tips - 15
\n- hpr3962 ::\nIt\'s your data
\n
\n
\n\n',225,42,1,'CC-BY-SA','Bash,loop,process,shell',0,0,1),
+(3992,'2023-11-21','Test recording on a wireless mic',223,'Archer72 tests out a wireless mic with a USB C receiver','LEKATO 2\nPack Wireless Microphone with Charging Case
\nhttps://www.amazon.com/gp/product/B0C4SNT6QK
\n\n- USB C
\n- Two microphones in a charging case
\n- Charge phone and use the receiver simultaneously
\n
\nClaims
\n\n- 75 ft. transmission range
\n- Wireless Mic can work continuously for 5 hours, and the charging box\ncan quickly charge the device 4 times. The total usage time reaches 25\nhours
\n
\nAxet Audio recorder on\nF-Droid
\nhttps://f-droid.org/packages/com.github.axet.audiorecorder
\n\n- Works to record stereo with this mic set
\n
\n',318,0,0,'CC-BY-SA','Recording, Microphone, Wireless, USB \'C\', F-droid, Android App',0,0,0);
/*!40000 ALTER TABLE `eps` ENABLE KEYS */;
UNLOCK TABLES;
@@ -21391,4 +21392,4 @@ UNLOCK TABLES;
/*!40014 SET UNIQUE_CHECKS=@OLD_UNIQUE_CHECKS */;
/*!40111 SET SQL_NOTES=@OLD_SQL_NOTES */;
--- Dump completed on 2023-11-02 8:40:54
+-- Dump completed on 2023-11-02 12:41:31