Hmm probably they race starting the server and only one wins. What tmux
version is this?
On Tue, Dec 03, 2013 at 03:39:48PM -0900, Donavan Kienenberger wrote:
> Ok that worked, although I had to add two things to my cron scripts. I
> had to make sure my environment variables were sourced before
Ok that worked, although I had to add two things to my cron scripts. I
had to make sure my environment variables were sourced before running
tmux and I had to stagger the start-up of my cron scripts using sleep.
Apparently tmux can't handle multiple scripts hammering it all at once
at start-up. It
These will all race against each other. If you want them to run in parallel you
need to specify -t to all commands or the send-keys will probably go to
whatever session started most recently.
Original message
From: Donavan Kienenberger
Date: 03/12/2013 21:46 (GMT+00:00)
To
No, each crontab script has changes appropriate to each processing
script. One of the things that may be causing this is crontab runs a
script and immediately moves on to the next one without waiting for
feed back from the script, these scripts are essentially running at
the same time, but running
You are creating all the sessions with the same name?
Original message
From: Donavan Kienenberger
Date: 03/12/2013 20:18 (GMT+00:00)
To: tmux-users@lists.sourceforge.net
Subject: Using tmux to start separate processing scripts on system boot.
Hi, I'm running tmux 1.6 on
Hi, I'm running tmux 1.6 on centos 5 & 6 servers. We have several
processing servers that run non-daemon scripts on boot that process
data. In the past this was done by using cron to start the script in a
screen process at boot and then detach. The scripts need to be started
in a window session as
