Gnu screen start at boot

hello.
ive been googleing around and havent found an answer to this..
what is the recommended way to start screen at boot?
i want it to run as regular user and detached so i can just do a screen -r when im ready to use the applications defined in .screenrc (rtorrent, newsbeuter, mutt, etc).

If you use a window manager / desktop environment, they usually have ways to launch programs at startup
Last edited by xenofungus (2010-03-19 08:49:19)

Similar Messages

  • HT4623 My I pad one constantly crashes, goes back to home screen, started just in Facebook but now it does it in everything! I have cleared all cookies, and even did the hard re boot...I am about to throw it! Trying to type this it kicked me out twice;-(

    My I pad one constantly crashes, goes back to home screen, started just in Facebook but now it does it in everything! I have cleared all cookies, and even did the hard re boot...I am about to throw it! Trying to type this it kicked me out twice;-(

    1. Close all apps in the Task Bar. Double-click the Home button and hold apps down for a second or two. Tap the minus sign to close app.
    2. Hold the Sleep/Wake and Home button down until you see the Apple Logo.

  • [SOLVED] rtorrent&screen don't start at boot time

    Hello. I use rc-script from ArchWiki to start screen with rtorrent (http://wiki.archlinux.org/index.php/RTo … ith_screen), but at boot time neither rtorrent nor screen start, although script prints "[DONE]". If I login as root and start script manually it works perfect, but I can't understand why it doesn't start automatically.
    Please, help.
    P.S. Of course script was added to DAEMONS array in rc.conf.
    Last edited by Atragor (2009-03-29 11:56:10)

    jordz, adding command to rc.local didn't change anything.
    LeoSolaris, yes, script is executable, and according to screen's man page:
    -d -m      Start screen in "detached" mode. This creates a new session but doesn't  attach  to  it.  This  is  useful  for  system startup scripts.
    I think it's something that could be called "daemon mode".
    Maybe some environment variables must be set in order to execute screen and rtorrent? I've tried to set HOME manually but it didn't help.

  • (MacBook 2014 model) most of keybord stopped working can't login. Restarted, screen started flashing bootup was slow and but no success. Tried safe boot but still no effect. Any suggestions please!! Urgentw

    (MacBook 2014 model) most of keybord stopped working can't login. Restarted, screen started flashing bootup was slow and but no success. Tried safe boot but still no effect. Any suggestions please!! Urgentw

    Try SMC and NVRAM resets:
    https://support.apple.com/en-us/HT201295
    https://support.apple.com/en-us/HT204063
    Then try the safe boot again:
    https://support.apple.com/en-us/HT201262
    If no success, make an appointment at an Apple store genius bar for a FREE evaluation.
    Ciao.

  • HP DV4-1155SE Black Screen and Wont Boot. Please Help!

    Hello all I am working on an Hp DV4-1155SE. I have tested the memory modules, the hard drive and everything else that I can take out of the computer easily. Everything works but!, The laptop will not boot into the bios or anything else. Black screen, wont boot and i have the bios file that HP supplies on the support page of the site. I have looked at the instructions that a few people have posted about re flashing the bios and that does not seem to help me at all with this AMD processor. If anyone can please offer any help at all this would be greatly appreciated.
    Thank you!

    I will search on int 19h....thanks.
    My problem started before the bios-screen.
    This is what I tried this evening:
    - Disconnected all non-essential devices...no effect.
    - Cleared the CMOS...system booted to OS!    Screens still garbled! 
    - Put in an older graphics-card...No artifacts! 
    - Put my MSI NX6600GT (AGP) back in...screen grabled while booting. Once in OS everything
      looks fine at first. Later I noticed some odd random pixels. Playing movies is working fine.
      Playing 3D games results in all kinds of strange looking artifacts.
    - Installed the latest NVidia- drivers...no effect.
    Is my problem still MOBO related or Graphics Adapter?
    Any further advice?
    Thanks!

  • The screen on my macbook has malfunction. When I change the brightness to zero and return to the first level of brightness it works briefly but then the screen starts to flicker brightness and quickly extinguished.

    The screen on my macbook has malfunction. When I change the brightness to zero and return to the first level of brightness it works briefly but then the screen starts to flicker brightness and quickly extinguished. It seems to be a bad contact, it would not be normal for a quality product that should have, he has less than two years of use. Not because of the bad use or crash. Someone with the same problem or can help me? It's really a contact problem? I've done all the procedures recommended by the online support. Thanks.

    Hey everyone in Apple world!
    I figured out how to fix the flashing yellow screen problem that I've been having on my MBP!  Yessssss!!!
    I found this super handy website with the golden answer: http://support.apple.com/kb/HT1379
    I followed the instructions on this page and here's what I did:
    Resetting NVRAM / PRAM
    Shut down your Mac.
    Locate the following keys on the keyboard: Command (⌘), Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    Turn on the computer.
    Press and hold the Command-Option-P-R keys before the gray screen appears.
    Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    Release the keys.
    I went through the 6 steps above twice, just to make sure I got rid of whatever stuff was holding up my bootup process.  Since I did that, my MBP boots up just like normal.  No flashing yellow screen anymore!!   
    (Note that I arrived at this solution when I first saw this page: http://support.apple.com/kb/TS2570?viewlocale=en_US)
    Let me know if this works for you!
    Elaine

  • Starts to boot, shows Apple logo for 2+ minutes, then starts again

    Yesterday the computer started to boot up as usual with the 'boot chord', Apple logo, then the screen went black, and started over again.  This time it successfully booted and ran normally for the rest of the day.  This morning, it never gets beyond the boot process; i.e. start chord, Apple logo for several minutes, then black screen and the whole process repeats over and over again.  Front panel status LED is on and steady.  I tried 5 different boot disks (internal HD, two external SuperDuper clones, a DiskWarrior DVD and the OSX 10.6 install disk and the results were the same.   It is still under extended warranty, but I can't afford the downtime for Apple to repair it.  Any idea what might be wrong?  Any thing else I might try to get it going again?

    Hopefully  the Time Machine backup is intact and the computer will continue to work with it connected (requires a 3rd party eSATA RAID controller card).  Assuming all the hardware works, I am unclear how best to restore the app's from the TM backup.
    The official way to do a full restore from TM is to boot from an installation DVD and select "Restore from Time Machine" from the Utilities menu. I don't see how that will work if your backup is on a third-party RAID, because the controller requires a driver that isn't on the DVD. That may be why you can't boot from the DVD.
    I think your best bet is to clone the installation disc to a bootable volume and install the RAID driver on it. The volume could be hosted on an external storage device or burned to a DVD. See here for an example of how to do this.

  • A205-S5804 "Dark Screen" start-up

    My A205-S5804 (P/N PSAF3U-0NR00V) starts up with the screen totally dark until it gets to the mouse pointer and "circulating ring", just before the circular Windows logo. Before that there SHOULD BE (which I still see on my wife's unaffected computer - same identical model):
    (1) Toshiba screen, with options at bottom bar to use F2  or F12
    (2) copyright symbol and "Windows" , and below that a small bar moving repeatedly left to right
    Item (1) should come from BIOS (someone please correct me if I'm wrong)
    Item (2) should NOT be part of BIOS
    Further, when I try to use F2 or F12 at startup, the screen stays dark, the computer reaches a stage of not doing anything (disk light off) and remains in that state.
    I did recntly flash a newer BIOS (version 2.50 for this model, 12/08/2008, file name sa200f3v250.exe), but I think the dark screen start-up began some time before that. The newer BIOS appeared to get in successfully. Also note that a bad BIOS would not explain the missing item (2) above.
    Where do I start?
    Solved!
    Go to Solution.

    After typing out this long query, I realized this looked like a case of BIOS not handling my video, but Windows doing so (once booted far enough). There is in fact something different about my video. The video is set to drive the notebook screen and the external RGB output (which goes to a flat-screen TV so online streaming video can be watched there). It has been convenient to just leave the notebook set for that video option. When I go back to video driving the notebook only, AND DISCONNECT THE CABLE TO THE TV, the start-up is normal.
    Now my question is, is there some way to leave the video set up for the 2 devices, and still get normal start-up?

  • When I turn on my macbook air, it starts to boot and then stops and turns off.  How do I fix this?

    When I try to turn my MacBook Air on, it starts to boot (gray screen with Apple logo and the swirling indicator) but then it simply shuts off. I have tried Safe Booting but that doesn't work either.
    Does anyone have a suggestion as I really need to get a couple of files off the hard drive.

    The progress bar on the apple screen indicates that the machine is attempting to boot to safe mode.
    Boot your mac and holds down the Option key to boot to the boot manager.
    Once in the boot manager click on macintosh HD and click the arrow to boot, this should boot your machine normally.
    Also perform an SMC/PRAM reset:
    SMC RESET:
    Shut down the computer.
    Plug in the MagSafe power adapter to a power source, connecting it to the Mac if its not already connected.
    On the built-in keyboard, press the (left side) Shift-Control-Option keys and the power button at the same time.
    Release all the keys and the power button at the same time.
    Press the power button to turn on the computer. 
    Note: The LED on the MagSafe power adapter may change states or temporarily turn off when you reset the SMC.
    PRAM RESET:
    Shut down the computer.
    Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
    Turn on the computer.
    Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
    Hold the keys down until the computer restarts and you hear the startup sound for the second time.
    Release the keys.
    If these fail, insert your OSX dvd, boot to boot manager, click the disc, reinstall the mac OSX.

  • Gnu Screen theme cycle with keybinding

    A guy at work did this and shared with me, so i thought I'd continue spreadin the love.    If you have multiple gnu screen sessions going at once, wouldn't it be nice to visually tell them apart without spending time to read the session name of each or trying to see what was going on within each?   
    The best way would be to color code the caption and hardlinestatus lines and be able to easily select a "color" per screen session and that's what he and I did.  Using C-g, we/you can easily cycle through various "themes".   This could also be useful if you wanted to cycle through mutiple hardstatus lines that displayed different information too if that's the route you'd like to go.   Anyways here it goes:
    #terminfo and termcap for nice 256 color terminal
    # allow bold colors - necessary for some reason
    attrcolor b ".I"
    # tell screen how to set colors. AB = background, AF=foreground
    termcapinfo xterm 'Co#256:AB=\E[48;5;%dm:AF=\E[38;5;%dm'
    # erase background with current bg color
    defbce "on"
    startup_message off
    bindkey ^G screen screen_theme.sh
    caption always "%{= KW}%-w%{= gW}%n %t%{-}%+w %-="
    hardstatus alwayslastline "%{= kW} %-= %{= kG}Session:%u%{= kW} %5` | %{= kG}Host:%{= kW} %H | %{= kG} MEM:%{= kW} %2`MB |%{= kG} SW: %{= kW}%3`MB | %{= kG}Unread: %{= kW} %4` | %m/%d %C %A"
    vbell off
    #Backticks to display information in status bar
    backtick 1 60 60 $HOME/bin/get_uptime
    backtick 2 60 60 $HOME/bin/get_freemem
    backtick 3 60 60 $HOME/bin/get_freeswap
    backtick 4 60 60 $HOME/bin/get_gmail
    backtick 5 60 60 $HOME/bin/get_sessionname
    defscrollback 5000
    screen -t root 0 sudo -s
    screen -t shell 1 bash
    screen -t shell 2 bash
    screen -t shell 3 bash 
    screen -t shell 4 bash
    screen -t shell 5 bash   
    screen -t shell 6  bash 
    screen -t shell 7  bash 
    screen -M  -t irc 8 irssi
    screen -t home 9 ssh home
    select 1
    This script resides in ~/bin which is in my path.  screen_theme.sh:
    #!/bin/bash
    INDEXFILE="$HOME/bin/themes/theme_index"
    # if this is the first time then set
    # the index to 0
    if [[ ! -e $INDEXFILE ]]
    then
    echo 0 > $INDEXFILE
    fi
    THEMENO=`cat $INDEXFILE`
    THEMEMAX=5
    if [[ $THEMENO -eq $THEMEMAX ]]
    then
    THEMENO=0
    else
    THEMENO=`expr $THEMENO + 1`
    fi
    echo $THEMENO > $INDEXFILE
    THEMEFILE=$HOME/bin/themes/theme${THEMENO}
    if [[ -e $THEMEFILE ]]
    then
    bash $THEMEFILE $STY
    else
    # reset the index back to zero if broken
    echo 0 > $INDEXFILE
    fi
    then I created a directory ~/bin/themes.  Within that directory I have the following files:
    $ ls themes/
    theme0 theme1 theme2 theme3 theme4 theme5 theme_index
    Each theme file is another color theme, the index just holds a count of the number of themes.
    An example of theme0  ( remember when doing yours to escape your backticks, otherwise it'll break).
    #!/bin/bash
    # yellow
    SESSION=$1
    screen -S $SESSION -X caption always "%{= KW}%-w%{= yk}%n %t%{-}%+w %-="
    screen -S $SESSION -X hardstatus alwayslastline "%{= kW} %-= %{= ky}Session: %u%{= kW}%5\` | %{= ky}Host:%{= kW} %H | %{= ky} MEM:%{= kW} %2\`MB |%{= ky} SW: %{= kW}%3\`MB | %{= ky}Unread: %{= kW}%4\` | %m/%d %c"
    Here's how my screen started:
    http://tuxtraining.com/images/screen1.png
    After C-g
    http://tuxtraining.com/images/screen2.png
    After C-g again
    http://tuxtraining.com/images/screen3.png
    and so on.
    Last edited by scv5 (2009-10-12 16:38:51)

    thayer wrote:
    steve___ wrote:
    Lich wrote:... useless for most of us as we only use one screen session normally.
    How do you know this?
    Just a guess, but doesn't that sort of defeat the purpose of a multiplexer?  I mean it's like running 20 instances of firefox instead of using a single firefox window with 20 tabs.  I'm sure some folks prefer the former, but I think it's safe to say the majority use the latter method.
    Sort of, I find screen becomes difficult to manage once we're talking more than the original 0-9 windows and you have to C-a-##, there's also the issue of screenspace.  With firefox i can list my tabs vertically giving me a lot more room to manage my tabs, screen doesn't have that option, so they go horizontally.    If i name all my tabs after the IP or name of the machine theiy are logged into, approach 15-20 windows really creaps on the screenspace.
    So typically what i do is have four shells open (grouped together or done in something like terminotor, or tabbed in flux or pekwm) each with 0-9 shells a piece, each session organized into type of servers.   So the upper left may be the email systems i support, the uppser right screen session may hold all the shell of our public facing web environment, bottom left is my local box, bottom right being misc boxes (dns servers, nis/ldap servers, various developement boxes..)  you get the hint.
    take into consideration i get one of these going per monitor that gives me approximately 80 shells, which is quite unmanagable in one screen session if you ask me.

  • GNU Screen prints back garbage?

    So. I've noticed an odd thing happening. Eventually, while running GNU Screen, lynx will start spitting out garbage characters at me. It usually starts with lynx, and then spreads to my other programs. http://homepage.mac.com/jamesebailey/screen_garbage.png is a picture of irssi with the garbage. I've only just started using screen, and I don't have the problem when I log in remotely, but only on my local login. I guess I could just SSH into my home computer while sitting in front of it, but that just seems silly, and there's got to be an explanation and solution for this, other than just working around it.
    Maybe not.

    Yeah, I know a couple of ways of getting it to do that, unfortunately, I've done none. Usually, I just switch back to a screen and see garbage. Moments later, all of my screens have garbage. Usually quitting the program and then quitting terminal gets rid of it, I'm just wondering if anyone knows what causes it and how to prevent it.

  • GNU Screen Scroll problem

    Hello everyone, I'm a new member in the Arch community and I'm enjoying myself a lot by using this distribution.
    the problem I'm having is that I can't seem to get the mouse scrollwheel to scroll upwards in GNU Screen running in a Terminator emulator once the terminal is filled.
    I have searched a bit and found that I should put something like this in my ~/.screenrc
    terminfo xterm* ti@:te@
    I have changed the xterm* to terminator* to match my emulator, my full .screenrc is as follows
    bind c screen 1
    bind ^c screen 1
    bind 0 select 10
    screen 1
    term screen-256color
    hardstatus alwayslastline '%{= g}[ %{G}%H %{g}][%= %{= w}%?%-Lw%?%{= R}%n*%f %t%?%{= R}(%u)%?%{= w}%+Lw%?%= %{= g}][%{B}%Y-%m-%d%{g}]'
    startup_message off
    terminfo terminator* ti@:te@
    vbell off
    altscreen on
    defscrollback 5000
    When I first open screen I can scroll up and down using the mouse wheel, but once the terminal gets filled all the way, the mouse wheel starts to show the command history instead of scrolling, which is a pretty odd behavior in my point of view.
    Anyone knows why is that happening?

    geekinthesticks wrote:I think I am missing something obvious and simple, but can't see what it is!
    They're called code tags
    I can't help with the problem directly, but those who can will probably be more inclined to do so if you include file contents of command output in [ code ] ... [ /code ] tags to keep it clean and readable.

  • Gnu Screen and 10.5

    So, does anyone else have problems with Gnu Screen and OSX 10.5? If I use the box-shipped version, my PATH is completely ignored, and it doesn't understand deflogin or login in my .screenrc file.
    If I use the macports version, I get UTMP problems and unless I manually create /var/run/utmp, eventually /etc/sudoers and passwd gets updated, and UID 501 is no longer in the passwd file!

    That's actually not screen's fault.
    When bash starts, it will read either .profile_bash or .bashrc but not both, depending whether it is a shell process or subprocess.
    On X-window based systems, one of these (I can never remember which) gets read when the root window starts, and then the other gets read when every sub-process starts. On OS X this approach breaks down.
    There is a slightly different bug I have been seeing, and I think it is due to multi-threading. Basically the screen session starts before the $PATH gets entries like /sw/bin or /opt/local/bin set. I never figured out how, but my hackish workaround is simply to start screen and then invoke the process I want, rather than to do it all in one command. (This gets annoying if you are writing shell scripts that invoke screen).

  • GNU screen, spawn windows and issue specific command to each

    Hello folks.
    I want gnu screen to spawn some windows, let's say, so I've put these lines in .screenrc:
    screen -t foo
    screen -t bar
    now I'd like to change the directories for foo and bar. I've tried multiple commands like:
    screen -X at foo screen -X stuff 'cd /tmp^M'
    screen -X at bar screen -X stuff 'cd ~/projects^M'
    and some other variations. At best, it gives the error message: "key: screen: invalid option -X .", at worst it doesn't start at all.
    Regards.

    problem solved. for others in need, put in .screenrc:
    screen -t foo
    at foo stuff 'cd /tmp^M'
    where "^M" is generated by pressing sequentially ctrl+v,ctrl+m

  • MBP 2011 Grey Screen. Normal Boot, Recovery Partition AND Network Recovery

    Hey Fellow Apple Lovers!
    My Macbook Pro 2011 recently froze and afterwards I haven't been able to log into the system. On start-up I encounter a gray screen. I'm sure this problem is very common on in the Community.
    I have tried the following:
    SCM reset
    NVRAM reset
    Safeboot (ends with blue screen)
    Tried to boot into the recovery partition (Gray Screen)
    Network recovery. The application downloads the data after connecting to my network and then continiues to start up.. Gray Screen
    Now I realize that at this point, we're probably talking about a problem with the HDD. However, I am slightly perplexed by the fact that even Network Recovery acts the same. Any specialists who might have some deeper knowledge about the inner workings of the MBP?
    Best regards
    Kristian Holm Sejersen

    Kristian,
    The blue screen is what I would be most concerned with. It could mean, if you've a 15" or 17" 2011 model, that you've the faulty installed AMD Radeon GPU, as discussed here -> https://discussions.apple.com/thread/4766577?tstart=0.
    Unfortunately, if you DO have this problem, it won't show up in either the Apple Hardware Test, which you can run, or in the normal tests performed by Apple techs.
    If you've a 13" model, this problem would not apply.
    The only thing that I can suggest is to take the machine to your local Apple Store or an AASP and see if your machine can be evaluated properly. If you do have a 15" or 17" and if you do have the problem of the faulty soldering, Apple will suggest a logic board replacement. That is only a temporary fix: a 'real' fix is having the GPU reballed and it's much, much cheaper than a logic board replacement.
    Give a ring back - if you've a 13" machine, I'm not certain what the problem might be.
    Clinton

Maybe you are looking for