I am searching for a way to run multiple commands at boot time using the gnu screen utility.
A solution could be:
But the result would be many sessions, each one with just one child. What I need is just one session with many children, one child per command.
out of no where it seems ubuntu no longer wants to cooperate when suspending/hibernating. the screen will just turn to a black screen without shutting down. each time i have to maually power down my laptop.
View 1 Replies View RelatedCant type anything when i attach to my screen by typing screen -r. It doesn't even say neokyle@server, the only thing i can get it to let me do is detach. I cant even kill it.
View 2 Replies View RelatedI can't seem to get Ubuntu to run on my old Dell Dimension 2300. It boots to a purple screen then it goes to a black screen with a load of writing nothing else happens after this screen. [URL] Could someone advise how I can get it to work?
View 1 Replies View Relatedwhat is the command for:
locking the screen
creating a new folder
log out
on the shell?
I have several screen sessions running, one of them named 'test'. I want to send a simple command to there without attaching the screen, so I do:
screen -S test -X ls
But when I attach the screen to see if it has done something, nothing is different... How can I send commands then? Of course the 'ls' command is not what I want to do, but it's just an example in how this is not working.
I'm just installed ns 2.31 in my cumputer:fedora 12 (this is the first time working with ns2 and fedora) but I don't know commands to run an example of tcl script and show the graph in my screen.
View 9 Replies View RelatedI'm running a Counter Strike 1.6 Game server on my centos 5 VPS. I can get it to run by simply switching to the directory, then doing: ./hltv Now, when I do that, it obviously closes when I exit Shell. So I do the following and it gives me errors then. screen -A -m -d -S hltv ./hltv My question is, do I need all of those commands after screen? I just simply want it to not close once I exit Shell.
View 5 Replies View RelatedI am learning linux commands. I just wanted to see what happens when I type
Code:
The screen became blank. Keyboard was not responding. I couldn't do a proper shutdown. I switched off computer by pulling out the plug. When I restarted, I heard a series of beeps (approximately 10 beeps). Then I was dropped to the grub prompt. The problem now is I can not type anything into the grub prompt, because the character 'c' is continously printed across the screen like this:
Code:
I couldn't stop the character 'c' from printing (I tried pressing Esc, Ctrl+C)
The solution is easy. I can reinstall grub from a livecd. Or even reinstalling the entire operating system wouldn't take more than 30 minutes. But I want to know:
1) What exactly happened to grub? What stage does this error belong to (1, 1.5 or 2)? What is the error number?
2) How can running "sudo kill -9 -1" affect grub?
So I pressed ctrl+alt+F3 and now my whole system is basically one big terminal - black screen and only accepts terminal commands. How do I go back to the 'normal' Ubuntu desktop screen? Rebooting only takes me back to the terminal command page described above. I can access root commands with sudo bash and my password, if fact all terminal commands seem to work. Is there a command I can use to go back to the regular desktop?
View 10 Replies View RelatedI am a linux newbie. I have a situation where I need to send a command line -X command to a screen session owned by root from a nonprivliged account. The command is executed by a shell script, which in turn is executed from a PHP script. Is there a way to make this work?
View 3 Replies View RelatedI've recently installed the 64bit version of WUBI on ASUS K50IJ with windows 7. Everything went smooth however when I try to boot into ubuntu, it shows that all the drivers are loading, I can even see the desktop background image for a second and then the screen goes blank. It is still ON however nothing is showing on it.
Pressing "CTRL+ALT+DEL" reboot the system.
even get access to the console for further debugging?
I looked for this but couldn't find it.
When Gnome starts, I would like to auto-login a user account, but I and the screensaver to lock at boot. I am using the gnome-screensaver.
I've been using 10.04 for a while now with no problems but for some reason it started freezing on the splash screen, 2 of my keyboards lights start blinking and thats it, I've tried with recovery mode and no luck either. The thing is I don't remember doing anything wrong.
View 3 Replies View RelatedI recently switched from KDE to Gnome, and when i setup Kubuntu I checked "Do not require login at startup", so i didnt get the screen. When i switched to gnome, it still didnt show it, and for various reasons i want the login screen at startup. I am running Ubuntu 10.10.
View 1 Replies View RelatedI recently upgraded to Ubuntu 11.04, and I installed it via the Update Manager and restarted as normal. But, as I went on my dual boot OS selection screen and selected Ubuntu, this message appeared:
init: udevtrigger main process ( 398 ) terminated with status 1
init: udevtrigger post-stop process (404) terminated with status 1
init: udevmonitor main process (397) killed by TERM signal
The disk drive for / is not yet ready or is not present
Continue to wait; or Press S to skip mounting or M for manual
I'm afraid to do anything after this screen...
OS: Ubuntu Server 10.04.2 LTS
I have a problem, I have a script which need to be ran in a screen, automaticly at startup (SRCDS Spesificly).
What I've done:
Ive placed a boot.sh script in init.d: Code: sh /home/xinity/eXtremeServer/startup.sh startup.sh: Code: cd /home/xinity/eXtremeServer
screen -S Sandbox ./orangebox/StartServer.sh Code: cd /home/xinity/eXtremeServer/orangebox/
[Code].....
What is wrong/happens: The server will run, I can connect to it, and see its process in top (running as root though). But it will not appear in the screen -ls list. And I cannot attach to it, therefor I have no way to manage my screen/server.
Is there any other way to execute scripts at startup? I remember when I ran Ubuntu Desktop, I managed to run it by the program Startup Manager. There has to be an nongui way to do this?
i recently was trying to install the ubuntu 10.04 in a machine with a 2x xeon processor but i'm getting some errors.In the installation first (and second, third...) try, the splash screen just freeze.After a lot of tries, just when i actived the acpi=off, noapic and nolapic, i finaly mounted the virtual desktop but after the succesful installation the machine wont boot! Only thing i get is a blank screen with a blinking dot on the left top.? it probaly somenthing related to the things i actived in grub boot, but i'm new to linux and can't find the problem! i can acess the ubuntu via hdd. I edited the boot on grub menu removing the "quite splash" from it and added "nolapic" in there place.Only thing left was the OS are now too slow. He works fine for 5 seconds and completely freeze for 2 seconds, then work for 5 secs again.
View 1 Replies View RelatedI long while ago (when I was in collage) I used VIM a bit. I have not used it since and would like to get back into using it. I remember there being a way to split the screen within VIM to show common commands on the bottom portion of the screen. I've searched a while and cannot find how to set this up.
View 1 Replies View RelatedI have Ubuntu 9.10 and I want to replace the splash screen with the white Ubuntu logo and the marquee progress bar with that of Xubuntu with those whirling sparkles.
View 1 Replies View RelatedI've been using Ubuntu off and on since 6.10, but I am definitely a noob when it comes to troubleshooting this kind of stuff. All of my previous installs went flawlessly, so I guess I've been lucky so far. I finally decided that I would bite the bullet, and remove Windows altogether. No more dual-boot with XP or 7 for me.I've been attempting to install the 10.04 RC all weekend, and it's been pretty frustrating. I decided I would start with my aging laptop, a HP Pavilion ze8500 that I custom-ordered way back in 2003. A few specs I know off the top of my head:
P4 (2.30 GHz)
512MB RAM
40GB SATA HDD
I burned the ISO to CD-R and started the install. When I boot from the CD, I get a purple screen which is blank other than two symbols at the very bottom. IIRC, one looked like a ruler or something, and the other looked sort of like a star in a circle? I think they were separated by an equal sign.I have no idea what that meant, but I knew enough to hit F6 and that got the install menu to appear onscreen. The only way I could get through the installer without losing video was to use 'nomodeset'
I installed over top of Windows 7 RC with the default partition table settings and after the install finished, I got the dialog box telling me that a restart is necessary. I hit Continue, the CD tray ejected, and my laptop restarted.So, assuming that the installation was a success, I see the BIOS screen, and then that goes blank, and where I would expect to see a boot screen or a Grub dialog, I see nothing at all.After the first install attempt, I would hear a drum sound after the screen went blank.I tried hitting 'Esc', along with 'Ctrl+Alt+F1', 'Ctrl + Alt + F2' or whatever else I could think of, and nothing seems to work.I updated my BIOS, remembering that I forgot to do that, and then I reinstalled Ubuntu. Again, no display when Ubuntu boots. And now, I hear no drum sound at all.
Recently my laptop running Ubuntu 10.10 has had an abrupt power shutoff (actually several times -- my battery has some problems).
Now when Ubuntu boots, I get the startup screen, but after a few seconds, the screen goes black. I can still boot from the live CD and in fact I am using my computer from the CD to write this post.
A few more details: When I press the power button while my computer is in this "blank" state, I get hard drive activity. Also, if I press "power", and then "enter", the machine actually shuts down.power
I have ubuntu desktop 10.10. I wrote a simple script that I want to execute at system startup. The only problem I have (and one that I've been struggling with for the better part of the day) is that I don't see the outputs of the script during startup.
View 1 Replies View RelatedI'm a beginner with Linux. I'm using the version of Ubuntu 10.10 installed in a notebook HP Pavilion tx 2000 (Turion 64 x2). My Ubuntu is 32 bits.
I'm passing for the following situation:
When I turn on my notebook, if it is running on battery (even with the battery has 100% of charge), a login / password screen does not appear, and the screen goes dark and nothing more I can do (that I knew!). So I re-start the machine.
However, if the notebook is plugged into electrical energy (with or without battery), a login / password appears normally.
If, with the notebook plugged into electrical energy, I log in Ubuntu operating system, then great. After loaded the operating system, I can turn off electrical energy and the notebook works normally (only with battery). In other words, just the login screen that is with this electrical energy problem.
I did a fresh install of 11.04 a week ago and I had my screen saver set to run 'Floating Feet' after 15 minutes idle time. Twice I've left my computer, and returned, clicked the mouse, and found my computer frozen on the screen saver. I was able to recover once by hitting the power button, which brought up the shut down/restart options and normal desktop. It hasn't happened since I turned off the screen saver, so I'll just leave it that way until a solution arises.
View 4 Replies View RelatedI recently started using Ubuntu 11.04. Everything works fine with my monitor directly connected to the computer. I get a default screen resoluton of 1680 x 1050, which is just fine.
However, when I connect the screen through a video splitter to be able to use a beamer, the screen resolution defaults to 1024x768. Moreover, Ubuntu then detects an unknown monitor and I cannot select a higher resolution.
I searched for modifications of xrandr en xorg.conf but I have to admit I don't understand what I've read. So my question remains: how can I force Ubuntu 11.04 to start with a screen resololution of 1680 x 1050 (without first connecting monitor only, that is).
I hereby add some information I retrieved with the screen connected without the splitter, so you can see what hardware is involved.
Code:
dirk@LaboFysica:~$ xrandr
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
VGA1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm
1680x1050 60.0*+
1280x1024 75.0 60.0
[Code].....
I am running linuxmint . Trying to configure my start-up resolutions using the Startup Manager. But they only offer 4:3 resolutions. (My screen is a widescreen, 1600 by 900). So I could check the 1600 x 1200 option but that is not the correct resolution. And I get a reminder from my screen that the resolution is wrong.
View 2 Replies View RelatedI installed ubuntu via virtualbox one day for fun, just to test it out. I didn't really need it, so i deleted the partition it was on and resized my hard drive. Thing is, when i startup my computer, ubuntu is still listed as an operating system, but whenever i go to choose it, my computer says "this file is missing or corrupt." I was just wondering if i make it so Ubuntu is not even shown on the screen anymore.
View 7 Replies View Relatedand I've had Ubuntu Linux (10.10) for maybe a month and a half now. Im very satisfied with the whole system, no problems up until an update about maybe 2 weeks ago from today (rough estimate). Anyways, when I start my computer and choose to start Ubuntu, about half of the time it will load with some weird new login screen (because of update), and their are other times where the screen will go blank. I dont think its very safe to cut the power from the computer through the power button :/ I realize there are other posts regarding this, and I apologize if this is against the rules, I just thought maybe it would be appropriate to start a thread with this problem for 10.10 users
View 2 Replies View RelatedHP laptop with Intel graphicsunning Slackware current with a 2.6.38.7-smp kernel.Booting with the "nomodeset" kernel parm works but X gets stuck with a 1024x768 resolution. When booting without, the screen goes black after a few pages scroll by, just at the point where the console switches to a higher resolution. Changing to a different console didn't help, so I blindly log on and type startx, and the screen comes back to life with KDE running at the higher 1366x768 resolution, I try a few apps, the webcam, suspend to RAM, resume, and everything is now working flawlessly so it doesn't look like an X issue.At this point I can change to another console (or exit KDE altogether) and the screen is back on at the higher resolution. Looking at the X log and some dmesg output makes it seem that starting X possibly replaces, reloads or unloads a driver? If this is the case, how can I prevent the conflicting driver from loading in the first place?Quote:
dmesg |grep drm
[ 11.481967] [drm] Initialized drm 1.1.0 20060810
[ 11.637941] [drm] MTRR allocation failed. Graphics performance may suffer.
[code]...
