Re: Standard way to create a generic queue in ksh

2016-04-16 Thread Raul Miller
The way I have created a queue in shell is: (1) create a directory to manage queue entries. (2) file names in that directory are high precision timer values (3) file contents in that directory are command lines. Then you need something to service the queue. In my case, I also decided that I coul

Re: Standard way to create a generic queue in ksh

2016-04-16 Thread andrew fabbro
On Sat, Apr 16, 2016 at 4:32 AM, Craig Skinner wrote: > A bloated way to do that is with an SQLite database, with a table's > unique primary key being some (job number) attribute. Another column > could auto timestamp on row insertion, so you could query on job number > or time added. Unless you'

Re: Standard way to create a generic queue in ksh

2016-04-16 Thread Craig Skinner
Hi Jon, On Fri, Apr 15, 2016 at 10:29:24PM +0200, Jon S wrote: > > As a port of a backup solution, i needa a queue. Having looked around the > net, i haven found any standard way (besides named pipes) that I can use. > Here's some shell scripting suggestions (which can be BASH specfic...) http:

Re: Standard way to create a generic queue in ksh

2016-04-15 Thread Jiri B
On Fri, Apr 15, 2016 at 10:29:24PM +0200, Jon S wrote: > Hello all! > > As a port of a backup solution, i needa a queue. Having looked around the > net, i haven found any standard way (besides named pipes) that I can use. > > Requirements are: > * There will be few elements in the queue (<20) > *

Standard way to create a generic queue in ksh

2016-04-15 Thread Jon S
Hello all! As a port of a backup solution, i needa a queue. Having looked around the net, i haven found any standard way (besides named pipes) that I can use. Requirements are: * There will be few elements in the queue (<20) * No critical section is needed (this is already adressed using mkdir)