diff options
author | David Runge <dave@sleepmap.de> | 2015-07-26 14:12:17 +0200 |
---|---|---|
committer | David Runge <dave@sleepmap.de> | 2015-07-26 14:12:17 +0200 |
commit | af1c8e988aa91391a5906f64a6137d44b3de237d (patch) | |
tree | 8356a6aca881fd4563be97049b5428fa63be1801 /README.md | |
parent | 013b05ecb9747f9613288c50c66ac8b7cac4c4fe (diff) | |
download | uenv-af1c8e988aa91391a5906f64a6137d44b3de237d.tar.gz uenv-af1c8e988aa91391a5906f64a6137d44b3de237d.tar.bz2 uenv-af1c8e988aa91391a5906f64a6137d44b3de237d.tar.xz uenv-af1c8e988aa91391a5906f64a6137d44b3de237d.zip |
README.md: Updating all tmux related links. Adding information for irssi and weechat user service.
Diffstat (limited to 'README.md')
-rw-r--r-- | README.md | 30 |
1 files changed, 25 insertions, 5 deletions
@@ -35,12 +35,12 @@ Some services are dependant or anti-dependant on the kernel command line option This is pretty useful when wanting to enable or disable certain services using *ConditionKernelCommandLine* in their **[Unit]** sections, ### Separate tmux environment -Tmux is used for a couple of services to start an environment in which other command line interface programs can run. To achieve this and not get in conflict with the standard tmux environment, some modifications might be needed. +[tmux](https://tmux.github.io/) is used for a couple of services to start an environment in which other command line interface programs can run. To achieve this and not get in conflict with the standard [tmux](https://tmux.github.io/) environment, some modifications might be needed. In some services the following Environment will be set: Environment=TMUX_TMPDIR=/run/user/%U/tmux -This will store the tmux server socket in the users run directory. If after starting this service one wants to connect to that special tmux session, it is necessary to either define the absolute path to the socket +This will store the [tmux](https://tmux.github.io/) server socket in the users run directory. If after starting this service one wants to connect to that special [tmux](https://tmux.github.io/) session, it is necessary to either define the absolute path to the socket tmux -S /run/user/<your-user-id>/tmux/<name-of-socket> attach @@ -78,6 +78,16 @@ Some systemd user services will need a dbus message bus, started by the user. Un systemctl --global enable dbus.socket +### irssi +The systemd user service *irssi.service* starts the [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) client [irssi](http://irssi.org/) in a separate [tmux](https://tmux.github.io/) environment for the current user. +To connect to it after starting the service, just do + + tmux -S /run/user/<your-user-id>/tmux/irssi attach + +or (if you've setup *$TMUX_TMPDIR* properly in your shell) + + tmux -L irssi attach + ### JACK JACK2 comes with a dbus interface. Unfortunately systemd's efforts regarding [kdbus](https://en.wikipedia.org/wiki/Kdbus) and integrating kernel CPU [cgroups](https://www.kernel.org/doc/Documentation/cgroups/) (and thereby also real-time scheduling) is still somewhat in limbo. The included jack@.service starts JACK using */usr/bin/jackd"* (so no dbus), according to a profile. The name of that profile follows after the *@* on starting/ activating the unit. @@ -88,7 +98,7 @@ The included jack@.service starts JACK using */usr/bin/jackd"* (so no dbus), acc This service is dependant on the real-time kernel command line option. It will only start, if that condition is met. ### Monitoring -The systemd user service *monitoring.service* is just a useful tool, that's hopefully going to expand in features in the near future. It starts htop, glances and a *"loginctl user-status"* for the current user in a separate tmux environment. +The systemd user service *monitoring.service* is just a useful tool, that's hopefully going to expand in features in the near future. It starts htop, glances and a *"loginctl user-status"* for the current user in a separate [tmux](https://tmux.github.io/) environment. To connect to it after starting the service, just do tmux -S /run/user/<your-user-id>/tmux/mon attach @@ -127,7 +137,7 @@ Make sure to also disable autospawn in your *~/.config/pulse/client.conf*, like autospawn = no ### rtorrent -rtorrent doesn't really come with any systemd service. Here it is started within a separate tmux environment. It will automatically create *~/Downloads/rtorrent/{tmp,session}*, if non-existent, set its working directory to *~/Downloads*. +rtorrent doesn't really come with any systemd service. Here it is started within a separate [tmux](https://tmux.github.io/) environment. It will automatically create *~/Downloads/rtorrent/{tmp,session}*, if non-existent, set its working directory to *~/Downloads*. The systemd user service is started/ enabled like this: systemctl --user start rtorrent @@ -162,7 +172,7 @@ To start/enable the service afterwards just do: systemctl --user enable systemd-analyze-plot ### tmux -[Tmux](http://tmux.sourceforge.net/) is a very useful tool to multiplex your terminals. It offers tiling and a high configurability. +[tmux](https://tmux.github.io/) is a very useful tool to multiplex your terminals. It offers tiling and a high configurability. The systemd user service for tmux starts it in a separate environment (set in *$TMUX\_TMPDIR*). This way it is started as soon as the *user@.service* starts, but will also close, when your last session closes! To start/enable it, just do: @@ -184,5 +194,15 @@ To start/enable it, just do: systemctl start update-mirrorlist.timer systemctl enable update-mirrorlist.timer +### weechat +The systemd user service *weechat.service* starts the [IRC](https://en.wikipedia.org/wiki/Internet_Relay_Chat) client [weechat](http://irssi.org/) in a separate [tmux](https://tmux.github.io/) environment for the current user. +To connect to it after starting the service, just do + + tmux -S /run/user/<your-user-id>/tmux/weechat attach + +or (if you've setup *$TMUX_TMPDIR* properly in your shell) + + tmux -L weechat attach + ## LICENSE **uenv** and all of its components are licensed under the GPLv3. |