Start rtorrent in tmux from rc.local at boot-time

[hanzer]

Hi,

I would like to share several datasets via net/rtorrent from a headless OpenBSD server:

$ uname -a

OpenBSD lucidrine.bohemia.net 6.0 GENERIC#1 i386

I am trying to devise a setup that will share the datasets whenever the computer is on. rtorrent runs as a regular user with a curses (text/terminal) interface. I interact with this headless machine via ssh and tmux. So, what I would like to do is start a tmux server at boot-time as the regular user and start rtorrent in a pseudo terminal in that tmux session.

This is what I've tried so far (it doesn't work):
/etc/rc.local

doas -u hanzer tmux new-session rtorrent

/etc/doas.conf

# Non-exhaustive list of variables needed to
# build release(8) and ports(7)
permit nopass setenv { \
        FTPMODE PKG_CACHE PKG_PATH SM_PATH SSH_AUTH_SOCK \
        DESTDIR DISTDIR FETCH_CMD FLAVOR GROUP MAKE MAKECONF \
        MULTI_PACKAGES NOMAN OKAY_FILES OWNER PKG_DBDIR \
        PKG_DESTDIR PKG_TMPDIR PORTSDIR RELEASEDIR SHARED_ONLY \
        SUBPACKAGE WRKOBJDIR SUDO_PORT_V1 } :wsrc
permit setenv { -ENV PS1=$DOAS_PS1 SSH_AUTH_SOCK } :wheel
permit nopass keepenv root

/home/hanzer/.tmux.conf

set -g history-limit 2000
set-option -g status-bg white
set-option -g status-fg black
new-session -n $HOST
set -g status-right '#H #(date +"%Y-%m-%d %a %H:%M")'

rtorrent and pf are configured and working.

My experience with tmux is somewhat superficial. Any ideas?

[TronDD]

You didn't say what about it doesn't work. Or if anything works when done manually. But the net/syncthing pkg-readme has a recipe for doing what you want to do from cron:

It might be desirable to have Syncthing executed on system reboot for each user individually. To achieve this a crontab entry can be created on per-user basis:

@reboot tmux new-session -d '/usr/local/bin/syncthing'

This will result in a new tmux(1) session being spawned each system boot. The user can later use `tmux attach` to view and control their Syncthing process.

[hanzer]

Thanks!

man 5 crontab describes the @reboot option. With that hint, I did this:

$ crontab -e

SHELL=/bin/ksh
PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
HOME=/home/hanzer
#
#minute (0-59)
#|   hour (0-23)
#|   |    day of the month (1-31)
#|   |    |   month of the year (1-12 or Jan-Dec)
#|   |    |   |   day of the week (0-6 with 0=Sun or Sun-Sat)
#|   |    |   |   |   commands
#|   |    |   |   |   |
23   *    *   *   *   wget -O - "http://freedns.afraid.org/dynamic/update.php?REDACTED" >> /tmp/freedns.log 2>&1 &
@reboot               tmux new-session -d 'rtorrent'

And it does exactly what I needed. Thanks again!

[scottro]

If you like, you should be able to click the thread tools link at top and mark the topic solved.
Thanks for coming back and sharing how you fixed it.

[hanzer]

Originally Posted by scottro

If you like, you should be able to click the thread tools link at top and mark the topic solved.

The Thread Tools menu doesn't seem to have that option

Originally Posted by scottro

Thanks for coming back and sharing how you fixed it.

That's how we roll

[LeFrettchen]

Originally Posted by hanzer

The Thread Tools menu doesn't seem to have that option

So, just change the topic title, and add [Solved]

[scottro]

Sorry, the Fedora forums which uses a similar interface, has it. (Or at least had it, I don't know if upgrades have removed it, and I know there are some slight differences--not sure if this one or Fedora is newer.)

[hanzer]

Originally Posted by LeFrettchen

So, just change the topic title, and add [Solved]

Hmm, in what color should be this [s]bikeshed[/s] "[Solved]" label?

Or more importantly, why doesn't the BBCode for strikethrough text render properly?

[ocicat]

Originally Posted by hanzer

Or more importantly, why doesn't the BBCode for strikethrough text render properly?

The strike-through tag supported here is [del], not [s]. As an example, strike-through.

Supported BBCode tags are discussed in the Forum rules.

[hanzer]

Originally Posted by ocicat

Supported BBCode tags are discussed in the Forum Info Thread.

Supa-cool, and bookmarked.

After spending a little more time with the "[Solved]" label issue this thread, I am inclined to Paint it black.