I was wondering if there was a way to create a script that would kill a process (the Folding @ Home one in particular), then shut down my pc. And I was wondering if there was a way to create another script that would set it to a timer, kind of like the shutdown -h command
View 5 RepliesWe may edit some values for GRUB from /etc/default/grub to modify the way that computers boot up and shutdown.My question is how to make such modifications for boot and shutdown. For example, suppose I want to display two splashes one during booting and the other during shutdown or I would like to acpi=off during booting and then acpi=force during shutdown.
View 1 Replies View RelatedNow, this is the case:
Yesterday, i tried to boot up my laptop but the battery was uncharged and it was unable to boot ubuntu karmic 64 bit. so i tried to plug the charger as soon as possible but when i looked at the screen, there was a huge black blank screen. so i had to restart it manually by pressing the power button. Now, i can see the grub screen, i can choose one of three kernels and the Windows. But only Windows can boot but the others doesn't. And also, grub timer does not work not. It does not count down to zero and autoboot the default os. I tried to reinstall grub but everytime , i got problems. Here is what i tried to do. In another try here, i failed again. In chroot, i could not "apt-get install" as it said i wasn't connected to internet (but i was), and in another try, it could not find p/rmonct /mnt/etc/resolv.conf.
How do I make a server wait on shutdown for a set amount of time?I tried making a service that just does Code: sleep 7m and made it first priority on shutdown but it seems to ignore itI'm pretty sure it runs... I'm currently testing that to make sure
View 4 Replies View RelatedI was trying to make shutdown without root user using visudoI tried the following still it did not work for mehawk ALL=NOPASSWD:/sbin/shutdown -h now
View 6 Replies View RelatedI am on opensuse 11.2 and sometimes when I shutdown the computer, It make a noise like "bzzz" but different than error beep. I think maybe there is a problem withe the automatic detection at the boot, but I really don't know alsa configuration or udev rules very well.
Code:
$ cat /proc/asound/cards
0 [Intel ]: HDA-Intel - HDA Intel
HDA Intel at 0xfc400000 irq 22
1 [HDMI ]: HDA-Intel - HDA ATI HDMI
HDA ATI HDMI at 0xcfeec000 irq 17
Code:
$ lspci | grep -i audio
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03)
01:00.1 Audio device: ATI Technologies Inc RV710/730
I have a third party application with a database.
I have created the service but it does not wait for the database to shutdown before the systems continues with the shutdown.
This results in the database being seen as crashed.
here is my stuff i did.
CACHE START AND STOP SCRIPT FOR REDHAT
#vi /home/cacheusr/cache_ctrl
Insert below
#!/bin/sh
#
# /etc/rc.d/init.d/cache_ctrl
# Cashier Control Script
#
# chkconfig: 2345 55 01
code....
I've recently upgraded to 11.04.Till now, I could select an option to make the open folders on shutdown, to restore on startup.There was an option to restore running applications
View 5 Replies View RelatedI have installed a cluster computer with 10 nodes . The manufacturer is HP . All nodes and the master node have redhat enterprise linux installed in them . When I shutdown the nodes from the master terminal using "shutdown -h now" they get shutdown . But they dont get completely turned off . This issue bothers me when the power supply is given , all nodes boot up simultaneously generating a huge heat .
Thing to note : When we shutdown our PC they get completely turned off . When the power supply is given , a press on the Power On button is required to boot the system. But , why does it not happpen in the case of cluster? Is there any other way of completely turning off the nodes from the master terminal ?
when my pc boots and shuts down my monitor goes into 'input out of range' mode for a bit between the gui and the text only phases of boot/shutdown.is there a way to fix this? or where to start troubleshooting?also, when it shuts down it hangs after coming back to the text only part
View 4 Replies View RelatedRecently I installed vncserver (tigervnc) on my desktop. Ever since my computer refuses to shutdown normally. At shutdown the following message pops up: Quote: System policy prevents stopping the system when other users are logged in Then I have to enter the root password to shutdown. If I stop vncserver before, the computer shuts down normally.
[Code]....
I cant shutdown without running sudo shutdown. When I try to use the default gnome shut down it takes me back to the logon screen. Fresh install today and I've had the same problem on other installs.
View 9 Replies View RelatedUbuntu will randomly pop up the shutdown menu and then shutdown.It seems to happen when im in firefox and typing and it has been difficult to replicate. I dont think it is a temp issue since watch sensors shows temmp of 40-50C. Someimtes it happens every minute someimtes i can go 10min without it happening.
Dell Inspiron 1525
ubuntu 10.04 (only os on system)
looking for a command that shutdown/reboot my ubuntu just same as process that happened when I press shutdown buttonIn fact I need to close all programs that are running and then PC shutdown (that happened when I press shutdown button).
View 9 Replies View RelatedI cannot locate shutdown log for Linux shutdown to check various activities carried out during shutdown. I can view Startup Log which is availble on console>Applications>System Tools>System Logs.
I have included Shutdown/Startup in dbora, so that Oracle 10gR2 Shutdown/Startup will be automated during OS Shutdown/Startup.
I want to check Shutdown log because Oracle Shutdown was not running, as from $ORACLE_HOME/shutdown.log contains no entries, where as startup log contains latest startup details.
That means here 2 issues are there. One, I want to locate OS Shutdown Log and the other being Why Oracle Shutdown not getting executed.
I did a live upgrade from 11.3 KDE and observe a following issue.When I press the shutdown button on the laptop it initiates the shutdown and shuts down fine but after a significant delay of time (something like 30 seconds). When I click the shutdown button in KDE it initiates the shutdown instantly. This was not the case in 11.3 where the shutdown worked the same regardless of the method that triggered it
View 6 Replies View RelatedI'm trying to reboot the server (shutdown -r now).But it seems like nothing happened.
When I try "shutdown -c", the system prompts "shutdown: cannot find pid of running shutdown."
I am getting an error as below.
How do I resolve the error: make[2]: *** No rule to make target `', needed by `mpg123'.
How can I resolve this error.
Further to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
Code:
shutdown system down 2.6.29.6-smp Sun Mar 7 15:35 - 03:02 (11:27)
reboot system boot 2.6.29.6-smp Sun Mar 7 09:35 (05:59)
09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this
Code:
shutdown system down 2.6.29.6-smp Sun Feb 21 12:39 - 13:20 (00:40)
reboot system boot 2.6.29.6-smp Sat Feb 20 09:39 (1+02:59)
09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
Code:
[snip]
reboot system boot 2.6.29.6-smp Fri Mar 12 07:42 (01:54)
shutdown system down 2.6.29.6-smp Fri Mar 12 01:31 - 09:37 (08:05)
wtmp begins Thu Mar 11 08:25:26 2010
[snip]
reboot system boot 2.6.29.6-smp Wed Mar 10 14:12 (15+01:42)
shutdown system down 2.6.29.6-smp Wed Mar 10 12:41 - 15:54 (15+03:13)
[snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.
I'm new to Ubuntu and have spent several days trying to make a few simple alterations to my Myth 9.10 installation. My biggest task was to get the MCE "power" and "start" buttons working, which they now are - sort of.
The problem is with the shutdown command that the power button activates seems to be different to the shutdown command from the taskbar shutdown menu i.e. when I switch off the computer with the remote it restarts with the "recovery" menu as it wasn't shutdown properly. Same thing happens with the shutdown command from a terminal window. Shutting off from the desktop menu is fine.
I notice that when you try to Make link to any file or folder form context menu, It just copy the same file size? even when i tried to copy the link to external storage disk..
View 1 Replies View RelatedI am following the instructions on Section 8.1.* Device Driver ConceptsHere I was able to proceed till section 8.1.4.After making the hello.c file,the make file and patching the Kconfig as mentioned,I tried to run the $ make ARCH=ARM CROSS_COMPILE=xscale_be- gconfig This gave error as:make: *** No rule to make target `gconfig'. Stop.I am not sure if my kernel is correctly compliled,but I was able to complie and build the kernel for arm before by cloning the kernel and building from the following link without any error. https://omapzoom.org/gf/project/omap...ux+OMAP+Kernel
View 2 Replies View RelatedI just installed Gnome Shell in Ubuntu 11.04 through UGR Linux and everything works fine! The only problem is that I cannot run make and make install. I get the following errors:
Code:
alexandros@Autobot:~/gnome-shell/source/gnome-shell-extensions$ make && make install
Making all in extensions
make[1]: Entering directory `/home/alexandros/gnome-shell/source/gnome-shell-extensions/extensions'[code]........
he clicks on everything on his GNOME desktop, and manages to delete everything, including menus, icons, etc. The people he lives with aren't skilled enough to fix it, and I live a good eight hours away. I have remote capabilities with NX, but that requires them to initiate a connection to my workstation here, which is more painful than I thought it would be. I need a way of locking down the desktop, so it's read-only, so he can't make the changes he seems to keep making. I figure I could make the .gnome directory read-only, but I don't know if that would affect the normal operation.
View 3 Replies View RelatedI need to modify fs/open.c and fs/read_write.c to make my modifications. I cannot find any options in 'make menuconfig' to make these files modules rather than compiled elements. I'm thinking these cannot be modules because the file system won't work without open.c and read_write.c. Is this correct - I cannot compile fs/open.c and fs/read_write.c as modules, only as compiled elements? Or, is there some way for a module to overwrite these routines when the module is installed and re-enable the routines when the module is removed?
View 3 Replies View RelatedI want to gave much details as possible. working directory (~/a1/shell) in the shell directory i have Makefile. also in the shell directory i have subdirectory's (obj, src, include)
My current Makefile
Quote:
#What needs to be built to make all files and dependencies
clean:
# End of Makefile
I wanted it so: all .o files are created in the obj subdirectory, and my application, sshell, is created in the shell directory.
I am getting this error when i run the make run: No rule to make target 'shell.h', needed by 'shutil.o'. stop
I build and use a custom kernel, and use the nvidia driver. This is on debian stretch.
By default, I build the image and headers packages with this line:
CONCURRENCY_LEVEL=8 nice -n19 ionice -c3 fakeroot make-kpkg --initrd --append-to-version=-something --revision=1 kernel_image kernel_headers
These kernel sources are usually the sources from debian, with a couple of more patches that I add. It appears that for nvidia-driver package versions higher than 352.79-1, the kernel headers/sources need to be prepared with 'make prepare' and 'make prepare scripts'. It's that simple. I concluded this after the nvidia dkms build failed on my custom kernel, but then succeeded after I pointed it to the full sources, but only after running 'make prepare' and 'make prepare scripts' on them. The problem is that this make-kpkg scheme doesn't appear to do this, or if it does, it doesn't properly include in the headers everything that it should.
difference between make and make bzImage commands as both are used to build source code.
View 1 Replies View Relatedcan anyone tell me the difference between "sudo shutdown now" and "sudo shutdown 0"
i know that "sudo shutdown 0" will shutdown the system in 0 seconds. but when i run sudo shutdown now my system goes into the maintenance mode?? what is maintenance mode??
I have down loaded: slapt-get-0.10.2h-i386-1.tgz I have read the install directions:
Quote:
- Using pkgtools: ----------------
To install:
$ make pkg
$ installpkg ./pkg/slapt-get-${VERSION}-${ARCH}-${RELEASE}.tgz
When I try make pkg, I get:
Code:
root@darkstar:/home/rob# make pkg
make: *** No rule to make target `pkg'. Stop.
I guess that I do not understand the instructions?