Ubuntu :: Bash Script Will Not Wait For Nautilus To Exit?
Oct 24, 2010
I'm having trouble with a bash script. Does anyone know why this doesn't work?
Code:
nautilus ./ &
wait $!
I'm writing a script which will extract a series of .rar files, present the extracted files to the user in nautilus so they may modify them, then when the user closes nautilus, the modified files are packed back into the archive.
I'm using bash script now,and I want have a script that can do like this: first ,tell me it will shut down ,and then shut down.My script looks like this:
#!/bin/sh /usr/bin/curl $stop_page shutdown -h now
The goal of the script is the following:Whenever I leave my house, my wife comes to my computer to check her mails (She has two computers of her own but they have a dangerous operating system, so they have been banned from the internet).She shuts down qbittorrent so as to download all her mails, and she forgets to execute it again on 98% of the times. End result: my computer is sometimes turned on for 10 hours doing absolutely nothing.I had therefore two choices: a) get on my wife's nerves until she gets the problem or b) write a bash script.If you are married, you will understand that bash scripts are easier to deal with than spouses.Ergo, I wrote the following script:
I'm running Ubuntu with Sun Virtual Macine on my Mac OSX and I have two problems.Somhow I have managed to get the Ubuntu screen to go completely black with a bash command line in the centre of it and the characters: "tty6" at the top of it. How do I exit this??Also I have a file on this virtual machine. Does anyone know how i would put this on my mac without the use of a Pen drive?
I'm new to scripting and I have a trouble with if statement syntax. The code is: Code: #there is a diff command here, and it does what i want but#i wanna see 1 if the exit value of diff is 0, and otherwise i wanna see 0.#the problem is here: (syntax error near unexpected token "then")
I have not been able to write bash to use a PID file to ensure no other instance of the same script is running! All three methods I can think of to see if the PID in the PID file is another instance of the script make the script exit with a return code of 1 but the same commands run at the command prompt work as expected.
The first attempt was:
Code:
The first attempted workaround was:
Code:
The second attempted workaround (with debug to make the following command prompt copy and paste meaningful) was:
Code:
Here's the command prompt session, testing with a stale PID file and then manually running the problem command and it behaving as expected:
Code:
This on Slackware64 13.1 which has bash 4.1.7.
In desperation I tried rebooting but the behaviour was the same.
I have made a simple bash script through which i can add, del, edit user from certain file using different CASE variables. like case 1. adduser 2. del user 3. edit user
Now i want to add a exit CASE like 1. adduser 2. del user 3. edit user 4. exit
Now i want to make a script such a way that, if user input is 4 then only script quit. I used with exit function also but it didn't work. if user press ENTER or other keys then also it quit the program.
I am trying to get bash script using zentity to exit if the user presses the cancel or close buttons.The exit codes are working fine; they read 1 or 0 depending on the status but it always assumes 0. This is the portion of the script: PHP Code:
function settings(){ result=$(zenity --height=30 --width=300 --list --checklist --title='Selection'--column=Boxes --column=Selections --column="Options"
I noticed that if I have "exit" in a bash script file., e.g. script.sh,that when the word "exit" is reached, and the script file being executed is not in the PATH nvironment, i.e. ". script.sh", the whole konsole shell profile is exited! What gives here? Is there another command compatible to "exit" to prevent this, or will I just have the leave the "." part in the PATH enviroment, which is, to my understanding, is not recommended? I desire for a "goto" function in bash script files
In linux, creating thread is same as process (clone()), except the virtual address space gets shared with the parent.If a running main process(thread) creates new thread, and if main thread exits, why should the new thread too exit? both are different entities, The same doesn't happen if the child thread exits, the parent thread would be alive.
I'm trying to write a init.d script to daemonise a sagemath notebook server. Here's what I've done so far, I've copied /etc/init.d/single for the structure, and tried to use dtach to provide a handle to access the process. However, my main problem is issuing the signals to kill the process (Ctrl-C) from a bash script and exit dtach (Ctrl-`)
I read recently that, if I install the 10.04 RC on my laptop I dont have to worry about reinstalling the 10.04 'official' version that comes out on the 29th.
Is it possible to change my current nautilus window to have sudo capabilities,? e.g. to delete locked files. It may be lazy but if it takes a lot of navigation then it would be handy to somehow activate sudo from the open window without the terminal command (gksudo nautilus) which always begins at root.
I attempted to install Nautilus Elementary...the results were not what I expected however. First of all, it doesn't seem to even have installed correctly, but thats not the main issue...after installing, Nautilus looks like this...
I have a small question.We use a backup program, that start an sepparat process with the name SIDB.When the server get an shutdown command. The normale back-up process is stoped. But the SIDB is not stopped correctly. But the shutdown proces should wait till the SIDB proces is stoped, and then proced with the shutdown process
I've added a new Nautilus action and I'd like to use another icon that those provided in the nautilus item con list (see attachment).
But whatever image I try (some PNG or even SVG files) I can't get them to be displayed. It seems there is a very special format, size, type to match the Gnome/GTK+/Nautilus icon requirements...
Does anyone know how I can move the location bar in nautilus up by the toolbar, as shown by this pic: http://i39.tinypic.com/2qdsyll.jpg
I'd rather not have to download the source of nautilus and edit the code / compile it myself.
By the way, a guy on Ubuntu Forums thought this was a mockup. It's not. It's the regular version of Nautilus, only I removed some toolbar buttons through the /usr/share/nautilus/ui xml files.
I just want the location bar next to the toolbar to conserve screen space, and be a bit more like Finder.
Core 2 Duo E4600 2GB DDR2 RAM (1 stick) Intel ICH10R based motherboard (tried an ICH9R aswell) 4-port SATA controller (PCI Sil 3114) O/S: Ubuntu Desktop x64 10.04 LTS (using 'desktop' because I like having a remote desktop)
The Storage Setup Disks: Assorted selection of 9 disk. 750GB, 1000GB and 1500GB Seagate and Western Digital disks. The disks are joined through a standard LVM2 configuration. I don't know the LVM term, but normally you'd call it a JBOD setup. On that LVM device, I've put a cryptsetup device, made with the LUKS tools (aes-xts-plain 256) On the cryptsetup device, I've created and mounted an EXT4 partition.
All in all, a completely standard LVM2 and LUKS setup, running EXT4. After a reboot, I proceed to unlock my cryptsetup encryption device, and then mount the EXT4 partition. All is well, the mount is accessible and everything looks fine. I then try to send a file to the mount, via Samba. After a few hundred MB written, the I/O wait goes berserk. It stays at 50% (dual core setup remember). The system becomes unresponsive to network commands (can't browse samba) for about 5-10 minutes. When it finally responds, the I/O wait is gone and everything is now fine. I can write and read hundreds of GB's of data without any issues at all. I can benchmark and stress all disks perfectly fine and no logs are showing disk errors.
I tried monitoring my disks with 'iostat -d 2' while the I/O wait was happening, and there is some slight Blk_read/s activity on 1 disk at a time. First for example /dev/sda is showing a little Blk_read/s acitivty, then it jumps to the next disk, and when every disk has show that slight Blk_read/s activity (500-800 or so) the problem is gone and the I/O wait is no more. I've tried changing motherboards, switching disks around on the controllers, checking individual disks, replacing disks and I've tried different versions of Ubuntu. The problem however persists. I could see it being a network issue, possibly a driver issue. But since the NIC is a standard RTL8111 on-board it seems unlike that the problem wouldn't be more widespread since this NIC is litterally being used everywhere. I did change my motherboard, so a faulty NIC seems unlikely twice in a row.
How do I create a command to launch a program and then have the terminal wait for a specified time and then move on to the next command?I'm wanting to create a startup script, and I need program B to wait until program A has finished loading up.
I applied all updates to my Kubuntu 10.04 installation, and shutdown and went to bed. Booted up this morning and found: [code]...
This error is returned if the module load command is used before loading a Multiboot kernel. It only makes sense in this case anyway, as GRUB has no idea how to communicate the presence of location of such modules to a non-Multiboot-aware kernel. lets re-install GRUB. So I booted up my live CD, and ran:
Same error. So I started looking around, and most complaints of this particular error seem to be dual boot environments, which I found rather odd, as I have never dual booted this machine.....
I was transferring data from one computer to my laptop and crash error came up on my laptop...
Error 1:
Nautilus-2.32.0-1.fc14 Reason: Process/usr/bin/nautilus was killed by signal 11 (SIGSEGV)
Error 2:
Openoffice.Org-Brand Crash
Reason: Process/usr/lib/openoffice.org3/program/soffice.bin was killed by signal (SIGABRT)
What could be the problem? Is it serious issue? I have been having security issues with Windows and are those issues begun once again? I have been under targeted attack since 2005.