Before i wiped windows (and the dual-booted slackware on it to make a slackware only hdd) i (sort of) backed up my files. I put something into my /etc/fstab that wiped /tmp/ when i shutdown/rebooted.
View 4 Replies
I have done 3 clean installs for this problem and it remains, i don't want to do it from the terminal..(Buttons exists but they won't work...)
View 3 Replies View RelatedI search many hours on the web for wipe my ram in a secure way and i find nothing good/secure/work exept URL... and i think it's the best solution for wipe RAM at shutdown!Im a newbie user and i want to implement this solution on my debian system at shutdown, i think its very easy because TAILS is based on debian! Does someone can put the procedures for get that on a debian box please?
View 8 Replies View RelatedFurther 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 just happen to have a glitch with my newly rebuild slackware server. This morning everything was working fine. Then having recently setup raid arrays, I decided to try MrGoblin's rc.mdadm script to monitor the raid arrays.
I copied the rc script to rc.d & added lines in rc.local to start the script, and a line in rc.6 to stop the script when shutdown or reboot.
Now, I cant reboot neither I can shutdown...
If I issue the command "shutdown -r now", Slack execute the normal shutdown or reboot steps, unmount the local FS, turn off swap, remount the rootdev as readonly, and then I see:
Code:
Mdadm monitor not running:INIT: no more processes left in this runlevel & it stalls at this point forever...
Before the machine would have rebooted after this line. What could explain this? Now I have to hard power down or reset the machine, and of course, upon rebooting I get a REISERFS warning of unclean shutdown...
Content of the rc.local:
Code:
#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local startup commands in here. Also, if you have
code....
I have prepared a static lib(.a) comprising 2 function definitions. I have created a different shared library(.so) comprising 2 more functions. The two functions of .so use the functions defined in the .a file. That is, the .so file uses the services of the .a file. Next, I create an executable that uses the shared library(.so). When I build my executable, it needs to be linked with the .a file as well. it gives me undefined reference for the functions defined in the .a file. Why is that so? I am posing this question because, the .a file has already been included(static linking) while bulding the .so. Is there any workaround so that I need not link the .a file with my final executable?
View 2 Replies View RelatedI have this configuration on my Ubuntu server:
1. Physical HDD1, mounted in /media/MYDATA
2. Physical HDD2, mounted in /media/MYDATA/MYMOVIES
This works, and has all my information. Unfortunately I can not use CIFS to get my data, because of a bug with wireless connection and umounting at shutdown. Until yesterday, I have no problem at all, mounting my NFS unit automatically in /media/MYDATA perfectly. But, when I go to /media/MYDATA/MYMOVIES in my laptops, filesystem is empty. I've included /media/MYMOVIES in the exports file (server) and in the fstab (client) and...it worked!!
But...system does not shutdown at all. If I manually try to umount /media/MYDATA the message received is "resource busy". :/ so...I guess this is the problem. If I manually umount /media/MYDATA/MYMOVIES first, laptop shutdown perfectly.
I'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 have recently upgraded to the 10.04 Alpha and have been unable to reboot or shutdown. I know it's just an alpha and therefore problems are bound to exist, so I tried reinstalling from a live cd of Alpha 3. But I am still unable to reboot or shutdown.To clarify what happens, I click on shutdown or reboot, the pop-up appears, I click on the shutdown/reboot button and it seems to complete it. It says that processes have been killed and something has exited with 255. But my computer is still on. I am guessing that Ubuntu is shutting down, it's just not actually shutting my computer down or restarting it.
View 5 Replies View RelatedI have a remote server (Xubuntu 10.04) which suffered an electricity brownout yesterday. The server itself is backed with an ups, but it is connected to a external firewire disk, which is not, and this disk malfunctioned as a result of the brownout.
The problem: Now, any process trying to access the external disk freezes and ends up in eternal D state in the process list, including ls and umount. Even trying to ls a directory which contains a symbolic link to a file in that drive just causes ls to freeze. These processes cannot be killed even with SIGKILL, so I proceeded to reboot but...
None of the reboot commands work. Instead they just get added to the ever increasing list of D state processes. I tried (sudo) shutdown -r now, reboot -f now and finally plain shutdown -h now. Is there anything else to try other than ask somebody to actually go to the server and pull the plug (which is not at all trivial)? Some way to tell kernel not to worry about messing stuff up, and just reboot?
we've just bought 30 newest nettops ACER Aspire R3700 with ION 2. I've tried ubuntu, kubuntu, xubuntu. Everything works as expected, but... the first one freezes when trying to reboot, shutdown or enter sleep mode. Checked on several hardware units. The desktop just freezes and nothing happens (ubuntu 10.10, both x32 and amd64). Also no one installs the wi-fi drivers, only ethernet
View 4 Replies View RelatedNatty won't shutdown for me - the start up/shutting down graphic comes up and the 'light' go down from 5 to 3 then it just hangs there.
Is there a shutdown log? I've looked in /var/log/messages but there's nothing relevant there.
From a 11.04 Ubuntu, I installed the meta-package xfce4 (*). Now, in the xfce4 session, "suspend" and "logout" (from the xfce4-panel button) works, but "shutdowmn" and "reboot" not, they only lead to GDM. (the shutdowm option there works.)
I tried to solve that by installing the meta-package "xubuntu-desktop" (maybe there are some necessary settings included?), and in fact, the login-screen changed (it's still GDM, I suppose) and there is now a "xubuntu" session, but in that, the probem is just the same: shutdown only leads to the login screen.
In Gnome Classic or Unity, shutdowmn works as it shoulds, so it's not a general problem with my computer.
In Detail, in forst tried to install xfce4 with ubuntu-software-center, but although it seemed to succeed, there was no xfce session. In Synaptic, installing the xfce3 metapackage worked. In fact, software-center seemed to have overlooked some dependencies...
I am facing the issue that the PC not capable to shutdown or reboot; In order to debug that, htop tells me the running processes but all seems normal, I killed few but still cold reset is needed.There is certainly a problem somewhere. the best would be to know which process are weirdly hanging. It could make this testing debian bit better to know which package has these issues.
View 1 Replies View RelatedRecently I installed Fedora 12 64bit in my HP Compaq 6720s. Among many other problems that I had and I solved with your help, I have the following problem:When I restart or shut-down Fedora 12 it crushes and hangs and only thing that I can do is to stop and restart my laptop by means of ON/OFF button.My question is:Is there any way to see this error (maybe some log file or something) so I can send this message or log file here in this forum and get some help?
View 1 Replies View RelatedI hoping someone can point me in a direction. I installed F13 KDE from the live cd and now when I Shutdown or Reboot, it takes 2 minutes and 8 seconds for the machine to power off. Yes, I timed it.Happens everytime like that. Even when booting from both "mainstream" live cd and the KDE spin live cd. When I hit the Shutdown or Reboot, it goes through the daemons/services shutdown the flashes up the Halting System or Please wait while the system reboots messages (respectivley), turns off the LCD and then just... sits with the power light on and hard drive activity light on. I should mention this is on a Toshiba Laptop about 2 years old now. Intel Chipsets. (Satellite Pro S300M-S2142 if anyone is really curious). The hard drive light stays on for about 1:03 minutes and then it turns off, at 2:08 minutes - the Power light finally turns off and the thing finally shuts down or reboots. If this sounds familiar, it's because it is and I've posted about it with F12 and it's still there with F13. Running kernel-2.6.33.3-85.fc13.x86_64
View 1 Replies View RelatedAfter a couple of days, some commands related to the disk (df) or files (ls) or killing process (kill -9) doesn't respond. Even I can't reboot or shutdown my server. After an hard reboot, some files are not here anymore or the log files are not filled anymore until I restart.My disk are behind the RAID controller i6 and are configure in RAID 1. The disks are two HP SCSI 72,8GB 10k RPM.Maybe I am totally wrong to check the disk access side, so I am open to other explanation.I can also add that my CPU is running under 1% et my RAM under 10%.
View 14 Replies View RelatedI don't follow why the Suspend option is there and the Reboot and Shutdown is not. Can anyone guide me to the code needed to add the selections. I know I can use a Terminal to shutdown or reboot but a simpler solution would be nice. I expect there are methods to fix most of what I don't like about Gnome 3 but I haven't found them yet. Is there a central place for the solutions needed to deminimalize Gnome 3? I really prefer one click control.
View 4 Replies View RelatedI want to change the reboot of ctrl+alt+del for shutdown, how i can do this in Fedora 15 ?
View 1 Replies View RelatedA couple of little niggles seen with KDE4.6. On 32bit install, (openSUSE11.3 was clean install)
-- reboot and shut down do nothing but hibernate and sleep are ok, can only powerdown with su privileges,
-- order of applications in plasma bar change after reboot.
On 64bit install, (openSUSE11.3 was update of openSUSE11.2)
-- slow poweroff overcome with new user profile, (no longer a problem with latest update)
-- inconsistent mouse curser theme, over desktop theme is Oxygen White, over application windows its DMZ
(resolved mouse cursor theme issue on 64bit install.
-- /etc/sysconfig, parameter X_MOUSE_CURSOR="DMZ"
-- and
-- /usr/share/icons/default was a link to DMZ
-- /usr/share/icons/default.kde4 was a link to oxygen
-- changed so that both were linked to DMZ
-- mouse cursor now consistent within windows and across desktop.
On one of my computers that I upgraded from 11.3 to 11.4 with a SSD HDD, it no longer umounts any disks on reboot or shutdown, there are no errors shown, it goes from sending TERM and KILL to rebooting.here is my fstab:
Code:
/dev/disk/by-id/ata-OCZ_SOLID_SSD_MK0109030A6100011-part1 /boot ext4 acl,user_xattr,noatime 1 2
[code]...
I recently migrated from Hardy 8.04 LTS (32) to Karmic 9.10 (32) so that the restricted ATI drivers and CCC would work correctly - that part is basically fine.
The problem for the past couple of weeks has been Karmic randomly shutting down, and rebooting the system after 1 or 2 hours up-time.
Why would this be happening, it was fine for the first few weeks after installing Karmic.
My system currently consists of the following;
Gigabyte MA790FX-DS5 mainboard - Jan '08
AMD 3.0Ghz Phenom II X4 945 CPU - Oct '09
4GB DDR2 Kingston HyperX RAM (1066 MHz) - Jul '09
Sapphire ATI HD5770 1GB GDDR5 video - Dec '09
Cooler Master Extreme Power Plus 640 watt power supply - Nov '09
Cooler Master Centurion 5 CAC-T05 case - Jan '08
1 pata 500 GB, 3 sata 500 GB & 1 sata 640 GB drives
2 DVD burners (Pioneer and LG)
2 x 19" (4:3) Samsung SyncMaster 943N LCD monitors
I used to have lmsensors working with the Athlon 2.8GHz dual core in Hardy, but they wouldn't work with the new Phenom 3.0 GHz 945 CPU in Hardy (and they still won't work in Karmic).
Th upshot is that I don't have cpu, system, or graphics temps; nor do I have any fan speeds, so I don't know what temps or fan speeds my system is running without rebooting into BIOS (which isn't much good as I really need to know what's happening when I'm using the OS itself).
Does anyone know what could be causing this random shut-down/reboot problem?
I've added entries to my Openbox menu labeled Reboot and Shutdown. Problem is, reboot and shutdown h only work as root, and I never login as root. I've tried su-to-root -c reboot, but the menu entries remain unresponsive. I do not have sudo installed because I feel it is a security issue. However, I found that sudo reboot works with the menu entry, but only if my account is set to use sudo without a password in /etc/sudoers. I use tint2 as my panel, but have had no luck with finding a shutdown/reboot button.
View 4 Replies View Relatedi have a server which was halt on last Thursday(may be halt by some one). using Oracle Enterprise Linux 5.3.
View 2 Replies View RelatedI want to do a shutdown -rF 3:00 to reboot my RHEL server at 3am tomorrow and force an e2fsck on each volume. But I want the e2fsck to run with the -y switch so it automatically answers yes so it will fix any problems it find automatically.
I can't find anywhere where it says if it will do this or not. does anyone know or have proof? Or is there a better way to do what I'm trying to accomplish?
Every shutdown/reboot always hangs on
Code: Select allkvm: exiting hardware virtualization
I have tried rebooting/shutting down with
Code: Select allshutdown -h now
reboot
shutdown -r now
halt
init 0
init 6
And all hang on the same line. This is 100% reproducible. I am not actually running a virtual machine. I don't have qemu-kvm installed. I do have separate partitions on my system. I have a /boot, /, swap, and /home partition.
From looking at other posts: [URL] .....
Solutions tend to be across the board: not unmounting properly, acpi settings in grub, using a different shutdown command.
My fstab file is:
Code: Select all# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
[Code] ....
and the result of Code: Select allmount is
Code: Select allsysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
udev on /dev type devtmpfs (rw,relatime,size=10240k,nr_inodes=498135,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000)
tmpfs on /run type tmpfs (rw,nosuid,relatime,size=800408k,mode=755)
[Code] ....
How to run a script/command before shutdown/reboot in Debian Jessie.
I created a script myshutdown.sh in /etc/init.d/ to shutdown rTorrent if the reboot or shutdown now -h command was executed.
#!/bin/bash
#rTorrent Shutdown Script
echo "Shutting down rTorrent!"
kill -2 `pidof rtorrent`
I set the file as executable.
sudo chmod +x /etc/init.d/myshutdown.sh
I inserted a symlink in the rc0.d directory with the process order K04.
sudo ln -s /etc/init.d/myshutdown.sh /etc/rc0.d/K04myshutdown.sh
I also inserted a symlink in the rc6.d directory with the process order K04.
sudo ln -s /etc/init.d/myshutdown.sh /etc/rc6.d/K04myshutdown.sh
Apparently rc0.d is for shutdown and rc6.d if for reboot
After reboot it appears that rtorrent does not run (I cannot connect to rtorrent via rutorrent) but really what is going on. I am trying to do this because rtorrent does a hash check on all files if it is not shutdown properly. I just want it to shutdown automatically and safely, before the system shuts down.
Every time I reboot or shutdown my PC, the login window shortly pops up. The PC does shutdown or reboot normally afterwards. When I use the terminal to shutdown/reboot (sudo shutdown -h now or sudo reboot) all goes well. The PC is running Debian Squeeze with the GNOME desktop environment.
View 7 Replies View RelatedCome across with a situation where all methods of shutdown result in a restart/reboot? I've tried commands:
- shutdown
- halt
- poweroff
.. with various parameters, nothing works. The laptop seems to power off, but after a sec it restarts/reboots. I've Googled high and low, but there's very little on this topic. Maybe it is specific to the current kernel in Wheezy? I'm not suspecting a harware failure, since this was not happening with Windows installed.
This happens on me with Wheezy on a HP Elitebook 8530w.
Whenever I reboot or shut down my computer (running OpenSuse 11.2 on a Dell Studio 15), it makes a weird noise that sounds like very loud static, even if my sound was muted when I selected shut down.
View 9 Replies View Related
