Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.os.linux.misc > #36094
| From | Rich <rich@example.invalid> |
|---|---|
| Newsgroups | comp.os.linux.misc |
| Subject | Re: Running consecutive |
| Date | 2022-11-13 20:40 +0000 |
| Organization | A noiseless patient Spider |
| Message-ID | <tkrkn4$1hcd3$1@dont-email.me> (permalink) |
| References | <tklq3v$sif5$1@dont-email.me> <wwviljlv0t2.fsf@LkoBDZeT.terraraq.uk> <tkr1qt$1fnee$2@dont-email.me> |
db <dieterhansbritz@gmail.com> wrote: > On 11.11.2022 18.49, Richard Kettlewell wrote: >> db <dieterhansbritz@gmail.com> writes: >> >>> I am preparing for an upgrade of my Kubuntu system, and have to do >>> a lot of synching. Some of these will take a longish time, so I >>> want to do them using a script. However, I find that the lines in >>> the script get run simultaneously, rather than one after the other. >>> How do I get them to run one after the other? >> >> Shell scripts normally run commands consecutively rather than >> concurrently. If you want people to debug your script you will have >> to post it. >> > > OK, here is a sample: > > echo " Running 64" > rsync -ar arraydata64/ Dropbox/arraydata64 > echo "running 128" > rsync -ar arraydata144/ Dropbox/arraydata144 > echo "Finished" > > When I just ran this, I got the two messages immediately, although > both synchs take a few seconds. Those run sequentially (one after the other), but if the data is already synchronized, rsync will complete very fast, which is probably giving you a false sense of "concurrency". Try adding rsync's verbose or itemize flags (or both) to the rsync lines so you get status output from rsync and you'll see that the "64" rsync completes before the "running 128" echo happens.
Back to comp.os.linux.misc | Previous | Next — Previous in thread | Next in thread | Find similar
Running consecutive db <dieterhansbritz@gmail.com> - 2022-11-11 16:35 +0100
Re: Running consecutive Aragorn <telcontar@duck.com> - 2022-11-11 16:43 +0100
Re: Running consecutive Richard Kettlewell <invalid@invalid.invalid> - 2022-11-11 17:49 +0000
Re: Running consecutive db <dieterhansbritz@gmail.com> - 2022-11-13 16:17 +0100
Re: Running consecutive Richard Kettlewell <invalid@invalid.invalid> - 2022-11-13 15:44 +0000
Re: Running consecutive Aragorn <telcontar@duck.com> - 2022-11-13 16:56 +0100
Re: Running consecutive Richard Kettlewell <invalid@invalid.invalid> - 2022-11-14 09:00 +0000
Re: Running consecutive Aragorn <telcontar@duck.com> - 2022-11-14 14:57 +0100
Re: Running consecutive Rich <rich@example.invalid> - 2022-11-13 20:40 +0000
Re: Running consecutive db <dieterhansbritz@gmail.com> - 2022-11-14 11:07 +0100
Re: Running consecutive The Natural Philosopher <tnp@invalid.invalid> - 2022-11-14 13:48 +0000
Re: Running consecutive "Carlos E.R." <robin_listas@es.invalid> - 2022-11-11 21:10 +0100
Re: Running consecutive Pancho <Pancho.Jones@proton.me> - 2022-11-11 21:16 +0000
csiph-web