Strict Standards: Declaration of action_plugin_loglog::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /home/public/screen/lib/plugins/loglog/action.php on line 15

Strict Standards: Declaration of action_plugin_captcha::register() should be compatible with DokuWiki_Action_Plugin::register($controller) in /home/public/screen/lib/plugins/captcha/action.php on line 0
suggestions
Table of Contents

Suggestions

This page is for suggestions. If you have an idea for the site, please add it to the list below.

Please fix the wiki so spammers don't overwrite it with levitra/viagra ads ;)

Yeah. I rolled it back, but it'm not sure if I rolled it back further than I had to; disabling anonymous edits and allowing us to create users ought to do the trick.

A code walkthrough would be cool.

Some tutorial/discussion on screen v.s. ssh (more specifically, ssh-key-ring/agent) interaction.

Finish documentation

I need to finish writing out the documentation for the screen commands. <PMG>

Discussion of how to set up bash/tcsh autocompletion of attachable screen sessions

I saw a reference (http://wiki.unixpod.com/Screen) that bash would autocomplete screen sessionnames, as in

      guest@zanzibar:~$ screen -list
      There are screens on:
              2441.bar        (Detached)
              2393.foo        (Detached)
      2 Sockets in /var/run/screen/S-guest.
      guest@zanzibar:~$ screen -r b<TAB>

where hitting the TAB key at <TAB> above would complete “b” to “bar”. But it doesn't work on my system. A code snippet for the .bashrc and/or .tcshrc files would be great!

Launch processes in a screen session on system startup

I've almost got this working on a FreeBSD system except for the terminal type. Everything gets started, but only in B&W.

The screen is for user bongo. First I wrote a script to start screen on system startup.

/usr/local/etc/rc.d/bongo_screen.sh
if [ "$1" = "start" ]; then
    su -l bongo -c "/usr/local/bin/screen -c /usr/local/etc/bongo_screen.conf -d -m"
    echo -n "bongo_screen "
fi

Then I wrote the screen configuration file to launch the applications necessary.

/usr/local/etc/bongo_screen.conf
term xterm
screen -t app_1 /usr/local/bin/app_1 app_1_options
screen /usr/local/bin/app_2
screen

The first line got me closest to the proper terminal type. The second line starts app_1 and names the screen “app_1”. The third line starts app_2. The fourth line just starts a shell.