I am guessing here. Something with multiple instances of bash acessing the
history. Are duplicates checked when a bash session is closed?
I am making up and example with 2 instances, B1 and B2:
- history of B1 and B2 initially the same:
com a
com b
com c
What happens if
I am guessing here. Something with multiple instances of bash acessing the
history. Are duplicates checked when a bash session is closed?
I am making up and example with 2 instances, B1 and B2:
- history of B1 and B2 initially the same:
com a
com b
com c
What happens if
Tomthemage wrote:
> I'd like to tail a file that's sitting on another server, but simply typing:
>
> tail address.of.server:/file/to/tail >> output
>
> doesn't seem to be doing the trick:
>
> tail: cannot open "address.of.server:/file/to/tail" for reading: No such
> file or directory
Right. Th
I'd like to tail a file that's sitting on another server, but simply typing:
tail address.of.server:/file/to/tail >> output
doesn't seem to be doing the trick:
tail: cannot open "address.of.server:/file/to/tail" for reading: No such
file or directory
I'm fairly new to bash and linux in general
Hi. I run automated software builds in the background and have had
this problem for years. Platform: FreeBSD RELENG_4
# make tests
# sh run-all
#sh run-read
# bash ./read.tests
# bash ./read2.sub
If make tests is backgrounded, read2.sub will block forever on tty
input. I've been p
