Re: Shutdown delay with LVM and disk encryption (SysV, buster)
On Sat Aug 31 2019 at 03:40 PM +0200, Stefan Krusche wrote: > Am Freitag, 30. August 2019 schrieb Bill Brelsford: > > My 64-bit buster installation was created using its installer, with > > / and /home partitions in an encrypted logical volume (sda3_crypt). > > On shutdown, it pauses near the end with > > > > Stopping remaining crypto disks... sda3_crypt (busy) sda3_crypt > > busy... > > > > The busy messages continue for about 30 seconds, after which it > > indicates "Failed" in red (I think, it happens fast) and shuts down > > in a second or two. > > > > If I change to systemd, shutdown is fast (no delay). > > > > This appears to be similar to earlier bugs, e.g. > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792552, > > except that they hung indefinitely. > > > > Anyone else seeing this? Any suggestions or workarounds (other > > than systemd)? Thanks.. > > Hello Bill, > > this behaviour had been discussed here, I think: > > https://dev1galaxy.org/viewtopic.php?pid=11522#p11522 > > In that thread and others on that forum there are a couple of links to > other threads etc. about this issue. > > The proposed solution is a patch which originated here: > > https://bugs.devuan.org//cgi/bugreport.cgi?bug=237 > > …which I have applied on my system (devuan/ascii) and never seen this > problem again. Thanks, Stefan -- that fixed it! The cryptdisks-functions file no longer contains the "local dst .." line, on buster anyway -- I inserted a "local vgs vg" line. Total shutdown time now about 7 seconds.. Regards.. Bill
Re: Shutdown delay with LVM and disk encryption (SysV, buster)
Am Freitag, 30. August 2019 schrieb Bill Brelsford: > My 64-bit buster installation was created using its installer, with > / and /home partitions in an encrypted logical volume (sda3_crypt). > On shutdown, it pauses near the end with > > Stopping remaining crypto disks... sda3_crypt (busy) sda3_crypt > busy... > > The busy messages continue for about 30 seconds, after which it > indicates "Failed" in red (I think, it happens fast) and shuts down > in a second or two. > > If I change to systemd, shutdown is fast (no delay). > > This appears to be similar to earlier bugs, e.g. > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792552, > except that they hung indefinitely. > > Anyone else seeing this? Any suggestions or workarounds (other > than systemd)? Thanks.. Hello Bill, this behaviour had been discussed here, I think: https://dev1galaxy.org/viewtopic.php?pid=11522#p11522 In that thread and others on that forum there are a couple of links to other threads etc. about this issue. The proposed solution is a patch which originated here: https://bugs.devuan.org//cgi/bugreport.cgi?bug=237 …which I have applied on my system (devuan/ascii) and never seen this problem again. HTH, Kind regards, Stefan
Re: shutdown fails to power off host
I had this issue in the past. Sometimes I could fix it by just reinstalling grub and the kernel. However, what that fixed? Dunno, but worked for me. Best Hans
Re: shutdown fails to power off host
On 1/17/2017 1:00 PM, Curt wrote: On 2017-01-17, wrote: Since it's a desktop I told the users that it's safe to power off the thing when in this state and filed it under "unsolved hardware/init system quirks". I suffer from one of these unsolved quirks. Occasionally my machine will shutdown correctly but will not power off. I have detected no discernible pattern (or discerned no detectable pattern). I power the machine off manually when the quirk occurs. regards - -- tomás +1 - I have a win 8 vm that currently exhibits this lovely feature - i boot the host, bring up the vm, log in, and get a black (blank) session window. I can force it to shut down by selecting "shut down" for the virtual machine and then closing the session window. I can also suspend the machine through normal action function. But either resuming the machine or shutting down and re-initializing brings the login and post-login brings the black hole of nothing. I've been scratching my head as to how this machine got into this state since it did seem to work the first 5 or 6 times I brought it up. Virtual machines seem (sometimes) to have their moments just as hosts do. --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus
Re: shutdown fails to power off host
Am 18.01.2017 um 08:44 schrieb Joerg Desch: > Am Wed, 04 Jan 2017 22:59:46 -0800 schrieb Bob McGowan: > >> When I shutdown my desktop system, the screen displays messages from >> systemd (I presume), the last of which is "Reached target Shutdown". > > Just a thought... > > I'm running Debian Jessie and I see the same behavior with my Thinkpad > T500. > > In my case the reason is the Network Manager. I have 2 NFS shares mounted > over Wifi. The Network Manager stops Wifi before unmounting the NFS > shares. This leads to a long time out. After that, I see the "Reached > target Shutdown" message and the system in still powered. > > I have to unmount the NFS volumes first and than I can shutdown the > system. You could unmount the NFS shares via a dispatcher hook See man NetworkManager → pre-down -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: shutdown fails to power off host
Am Wed, 04 Jan 2017 22:59:46 -0800 schrieb Bob McGowan: > When I shutdown my desktop system, the screen displays messages from > systemd (I presume), the last of which is "Reached target Shutdown". Just a thought... I'm running Debian Jessie and I see the same behavior with my Thinkpad T500. In my case the reason is the Network Manager. I have 2 NFS shares mounted over Wifi. The Network Manager stops Wifi before unmounting the NFS shares. This leads to a long time out. After that, I see the "Reached target Shutdown" message and the system in still powered. I have to unmount the NFS volumes first and than I can shutdown the system.
Re: shutdown fails to power off host
On 01/17/2017 02:39 AM, Hans wrote: > I remember this discussion from sime time ago. Debian has changed a real > poweroff from "halt" to "halt -p". The second one is according to the manual. > > As far as I remeber, "shutdown" is just a wrapper fpr the halt command, but I > am not quite sure. > > But one thing was cleared: To poweroff a debian systenm, the command "halt > -p" > is recommended. > > Besides: This behaviour is also now in kali linux integrated, which was also > using the command "halt" for a long time. But now it's "halt -p", too, also > on > the livefile. > > Best > > Hans > Hi, Thanks for the suggestions and insight to the problem. In my case: 1. The problem was with *any* "shutdown", from the command line, via halt or shutdown, or through menus of the window system. 2. The comment by j...@jretrading.com about unmount issues rings a bell, I think I saw something about failure to sync at one point. 3. I did try 'halt -p', same result. 4. There have been two or three updates since I sent my original question, and the system is now halting and powering off as expected. Bob
Re: shutdown fails to power off host
On Tue, 17 Jan 2017 18:00:00 + (UTC) Curt wrote: > On 2017-01-17, wrote: > > > > Since it's a desktop I told the users that it's safe to power off > > the thing when in this state and filed it under "unsolved > > hardware/init system quirks". > > I suffer from one of these unsolved quirks. Occasionally my machine > will shutdown correctly but will not power off. I have detected no > discernible pattern (or discerned no detectable pattern). > > I power the machine off manually when the quirk occurs. > Me too. Sid on LVM2, AMD video on Giga MB, fails maybe 10%-20% of shutdowns. The small amount of evidence suggests trouble dismounting the hard drive, with the device mapper showing an unknown number of devices having failed to clear, and no sound of the heads parking. Replacing the hard drive (just age, not for this problem) has improved speeds of some actions, and not changed this behaviour at all. There is also trouble booting sometimes, which appears not to correlate at all with the shutdown trouble. I think that is something to do with video driving, but I can't get any kind of evidence for that, either, other than that it always crashes when the display switches from low-res text to high-res text. Nothing in any log, nothing at all to put in a bug report. Hey, it's sid. -- Joe
Re: shutdown fails to power off host
On 2017-01-17, wrote: > > Since it's a desktop I told the users that it's safe to power off the thing > when in this state and filed it under "unsolved hardware/init system quirks". I suffer from one of these unsolved quirks. Occasionally my machine will shutdown correctly but will not power off. I have detected no discernible pattern (or discerned no detectable pattern). I power the machine off manually when the quirk occurs. > regards > - -- tomás > > -- “It is enough that the arrows fit exactly in the wounds that they have made.” Franz Kafka
Re: shutdown fails to power off host
I remember this discussion from sime time ago. Debian has changed a real poweroff from "halt" to "halt -p". The second one is according to the manual. As far as I remeber, "shutdown" is just a wrapper fpr the halt command, but I am not quite sure. But one thing was cleared: To poweroff a debian systenm, the command "halt -p" is recommended. Besides: This behaviour is also now in kali linux integrated, which was also using the command "halt" for a long time. But now it's "halt -p", too, also on the livefile. Best Hans
Re: shutdown fails to power off host
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, Jan 17, 2017 at 11:35:28AM +0200, Johann Spies wrote: > On 5 January 2017 at 09:09, Bob McGowan wrote: > > > On 01/04/2017 10:59 PM, Bob McGowan wrote: > > > I have done a search of the debian-user archive, using the same text as > > > the subject, and found several references to emails with similar > > > problems. However, no exact solution was proposed. > > > > > > And this actually only happens on one of the two systems I have Debian > > > installed on. > > > > > > I'm using testing (stretch). > > > > > > When I shutdown my desktop system, the screen displays messages from > > > systemd (I presume), the last of which is "Reached target Shutdown". > > > > > > > I get that when I use 'sudo halt' > > When I use 'sudo halt -p' it powers off. "halt" is "shutdown" -- at least from where you are shooting. From halt's man page: If halt or reboot is called when the system is not in runlevel 0 or 6, in other words when it's running normally, shutdown will be invoked instead (with the -h or -r flag). For more info see the shutdown(8) manpage. > So I would suggest you look at the underlying command on the button of the > computer which do not power off and change the command. > > Look at 'man shutdown' for the options when you use 'shutdown' in stead > of 'halt'. I agree, it should be in the options. That said, one of the systems I take care of *sometimes* ends up in this state (i.e. "Reached target ..."), but most of the time actually powers off. Since it's a desktop I told the users that it's safe to power off the thing when in this state and filed it under "unsolved hardware/init system quirks". regards - -- tomás -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.12 (GNU/Linux) iEYEARECAAYFAlh98ooACgkQBcgs9XrR2kYHnwCdEUocDUqU6+ZCEKaVwVnhFRp0 yFwAn2t/TFQNikQsV+Y+79RWUWXr7Xp0 =7fMt -END PGP SIGNATURE-
Re: shutdown fails to power off host
On 5 January 2017 at 09:09, Bob McGowan wrote: > On 01/04/2017 10:59 PM, Bob McGowan wrote: > > I have done a search of the debian-user archive, using the same text as > > the subject, and found several references to emails with similar > > problems. However, no exact solution was proposed. > > > > And this actually only happens on one of the two systems I have Debian > > installed on. > > > > I'm using testing (stretch). > > > > When I shutdown my desktop system, the screen displays messages from > > systemd (I presume), the last of which is "Reached target Shutdown". > > > I get that when I use 'sudo halt' When I use 'sudo halt -p' it powers off. So I would suggest you look at the underlying command on the button of the computer which do not power off and change the command. Look at 'man shutdown' for the options when you use 'shutdown' in stead of 'halt'. Regards Johann
Re: shutdown fails to power off host
On 01/04/2017 10:59 PM, Bob McGowan wrote: > I have done a search of the debian-user archive, using the same text as > the subject, and found several references to emails with similar > problems. However, no exact solution was proposed. > > And this actually only happens on one of the two systems I have Debian > installed on. > > I'm using testing (stretch). > > When I shutdown my desktop system, the screen displays messages from > systemd (I presume), the last of which is "Reached target Shutdown". > > It then just sits there. I have taken to using a power strip with a > switch as a way to quickly turn the host off, once it has reached the > target. > > On my laptop, I see the same message, followed by powering off the system. > > Tonight, I happened to take longer than usual to get to my desktop > system, and while writing down the exact wording of the message, the > kernel panicked. > > My laptop is around ten years old, an HP Pavilion dv9000, the desktop is > about half that age, a home built "gamer" level hardware system. > > Any ideas what I should be looking for? The fact the kernel panics on > my desktop would imply to me there is a kernel configuration issue of > some sort, but I have no idea where to start. > > Thanks, > > Bob > My apologies, I failed to mention: I'm using Xfce4 as my windowing system on both hosts. And I'm using the 'shutdown' menu option from the "Action Buttons" panel plugin. Bob
Re: shutdown icon changed
On 3/20/15, Matthias Bodenbinder wrote: > Am 18.03.2015 um 07:07 schrieb Matthias Bodenbinder: >> Hi, >> >> I am running debian testing and kde4. The icon theme is oxygen. But the >> shutdown icon which is shown in the taskbar and in the menu is the >> shutdown icon from the high-contrast theme. Basically this is >> black-and-white instead of the red shutdowen icon from the oxygen theme. I >> opened the systemsettings and switch back and forth through the different >> icon themes. All icons are changed according to my selection except for >> the shutdown icon. It always stays the same. >> >> What is happening here? >> > > I found the root cause: KDE is taking the icons from > /usr/share/icons/hicolor/ regardless which theme is actually being used. I > neeed to rename the corresponding icons to get it working again: > > cd /usr/share/icons/hicolor/ > find . | grep weg > ./scalable/apps/system-shutdown.svg.weg > ./48x48/apps/system-reboot.png.weg > ./48x48/apps/system-log-out.png.weg > ./48x48/apps/system-hibernate.png.weg > ./48x48/apps/system-shutdown.png.weg > ./48x48/apps/system-suspend.png.weg > > Those icons got installed by xfce4-session from debian experimental. From my > pijnt of view this is a bug in KDE. It should stick to the icons from the > selected theme and not go into hicolor. Am coming really late into the conversation here. I've seen "similarly different" since I started doing installs via debootstrap. I'm using unstable and Xfce. Last debootstrap was couple days ago, and I still saw what I'm seeing here. The classic fallback "x box" that you normally see in some/many browsers pops up in when icons are *apparently* missing. My setup is extremely basic but some one of those very few subsequent package installs done post debootstrap each time corrects the problem here. Because it does, it's the old "out of sight, out of mind" kind of deal so I hadn't addressed it yet to determine the core cause. I know, I know *my bad* KDE4 pulling high contrast icons might be its version of using the "x box" as default. Maybe KDE4 developers have instructed it to roll down the list of available icon directories if it encounters missing icons whereas Xfce's fix is to turn to the classic x icon. Given the two options, I like what yours is doing because yours still visually distinguishes between apps, etc.. Mine becomes self-corrected early on with no intentional intervention from me. Two ways that could happen are 1) one of my few installed packages brings with it an entire new set of icon directories and/or 2) one of those few installed packages maybe overwrites core, errant system icon paths somewhere. Just thinking out loud. :) Cindy -- Cindy-Sue Causey Talking Rock, Pickens County, Georgia, USA * kinda just strolling with those plastic sporks today * -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/CAO1P-kDyJDcpjh3uwmVYTL=K=X0eS0F+yWRP_=g4alvrc0f...@mail.gmail.com
Re: shutdown icon changed
Am 18.03.2015 um 07:07 schrieb Matthias Bodenbinder: > Hi, > > I am running debian testing and kde4. The icon theme is oxygen. But the > shutdown icon which is shown in the taskbar and in the menu is the shutdown > icon from the high-contrast theme. Basically this is black-and-white instead > of the red shutdowen icon from the oxygen theme. I opened the systemsettings > and switch back and forth through the different icon themes. All icons are > changed according to my selection except for the shutdown icon. It always > stays the same. > > What is happening here? > > Thanks > Matthias > > I found the root cause: KDE is taking the icons from /usr/share/icons/hicolor/ regardless which theme is actually being used. I neeed to rename the corresponding icons to get it working again: cd /usr/share/icons/hicolor/ find . | grep weg ./scalable/apps/system-shutdown.svg.weg ./48x48/apps/system-reboot.png.weg ./48x48/apps/system-log-out.png.weg ./48x48/apps/system-hibernate.png.weg ./48x48/apps/system-shutdown.png.weg ./48x48/apps/system-suspend.png.weg Those icons got installed by xfce4-session from debian experimental. From my pijnt of view this is a bug in KDE. It should stick to the icons from the selected theme and not go into hicolor. Matthias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/megi78$hh4$1...@ger.gmane.org
Re: shutdown icon changed
Am 18.03.2015 um 07:07 schrieb Matthias Bodenbinder: > Hi, > > I am running debian testing and kde4. The icon theme is oxygen. But the > shutdown icon which is shown in the taskbar and in the menu is the shutdown > icon from the high-contrast theme. Basically this is black-and-white instead > of the red shutdowen icon from the oxygen theme. I opened the systemsettings > and switch back and forth through the different icon themes. All icons are > changed according to my selection except for the shutdown icon. It always > stays the same. > > What is happening here? > > Thanks > Matthias > > Actually, it is 3 icons that always stay the same: shutdown, logoff and restart. Matthias -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/meb5ok$pgp$1...@ger.gmane.org
Re: shutdown hangs 4+ minutes at "Stopping enhanced syslogd: rsyslog."
On 2014-08-29, Michael Biebl wrote: > But yeah, isn't it great if you can everything on systemd. > Systemd is wonderful. I made a "little" mistake. I'll shoot myself at dawn. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnm01n3o.2ve.cu...@einstein.electron.org
Re: shutdown hangs 4+ minutes at "Stopping enhanced syslogd: rsyslog."
Am 29.08.2014 10:24, schrieb Curt: > On 2014-08-29, Devrin Talen wrote: > >> Since it's related to the /etc/rc0.d scripts, maybe start with a bug >> against the sysv-rc package? >> >> $ dpkg --search /etc/rc0.d/ >> sysv-rc: /etc/rc0.d >> >> You can check if your bug is already there (a quick search didn't show >> anything): >> > > Looks rather like this bug (maybe samba, maybe systemd in its troubled > relationship to samba or sumthin'). Well, since he is using wheezy and sysvinit apparently, this is certainly not a systemd issue. But yeah, isn't it great if you can everything on systemd. Michael -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth? signature.asc Description: OpenPGP digital signature
Re: shutdown hangs 4+ minutes at "Stopping enhanced syslogd: rsyslog."
On 2014-08-29, Curt wrote: > > Looks rather like this bug (maybe samba, maybe systemd in its troubled > relationship to samba or sumthin'). > Forgot the bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=739887 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnm018ea.2ve.cu...@einstein.electron.org
Re: shutdown hangs 4+ minutes at "Stopping enhanced syslogd: rsyslog."
On 2014-08-29, Devrin Talen wrote: > Since it's related to the /etc/rc0.d scripts, maybe start with a bug > against the sysv-rc package? > > $ dpkg --search /etc/rc0.d/ > sysv-rc: /etc/rc0.d > > You can check if your bug is already there (a quick search didn't show > anything): > Looks rather like this bug (maybe samba, maybe systemd in its troubled relationship to samba or sumthin'). -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/slrnm00e62.2a4.cu...@einstein.electron.org
Re: shutdown hangs 4+ minutes at "Stopping enhanced syslogd: rsyslog."
David Christensen writes: > If I manually unmount Samba shared folders imported by this machine > prior to shutdown, shutdown proceeds without delay. So, the problem > appears to be related to the order in which things happen at shutdown > (?). > > Any ideas on how to troubleshoot and properly fix this? Bug report? > Which package? Since it's related to the /etc/rc0.d scripts, maybe start with a bug against the sysv-rc package? $ dpkg --search /etc/rc0.d/ sysv-rc: /etc/rc0.d You can check if your bug is already there (a quick search didn't show anything): https://bugs.debian.org/sysv-rc -- Devrin Talen -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/87iolcuido@cornell.edu
Re: Shutdown computer after a specific command has been executed
On Fri, 2013-12-13 at 14:28 +0100, Ralf Mardorf wrote: > On Fri, 2013-12-13 at 11:07 +0200, Andrei POPESCU wrote: > > Simple: > > > > sudo sh -c "apt-get update && apt-get --download-only -y dist-upgrade ; > > poweroff" > > > > and do the upgrade the next day, under human supervision. > > +1 > > Perhaps then directly > > sudo sh -c "apt-get update ; apt-get --download-only -y dist-upgrade ; > poweroff" Nonsense, my apologies. Just +1, nothing to change. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386941475.688.133.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On Fri, 2013-12-13 at 11:07 +0200, Andrei POPESCU wrote: > Simple: > > sudo sh -c "apt-get update && apt-get --download-only -y dist-upgrade ; > poweroff" > > and do the upgrade the next day, under human supervision. +1 Perhaps then directly sudo sh -c "apt-get update ; apt-get --download-only -y dist-upgrade ; poweroff" -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386941312.688.132.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On Jo, 12 dec 13, 16:15:44, Ralf Mardorf wrote: > On Thu, 2013-12-12 at 16:10 +0100, Ralf Mardorf wrote: > > sudo sh -c "apt-get update && apt-get dist-upgrade -y ; poweroff" > > sudo sh -c "apt-get update && apt-get dist-upgrade --dry-run ; apt-get > dist-upgrade -y ; poweroff" > > -y without a dry run :S, OTOH, the OP want's to go to sleep, so the > dry-run first doesn't improve something. > > It's simply a bad idea to automate an upgrade. Simple: sudo sh -c "apt-get update && apt-get --download-only -y dist-upgrade ; poweroff" and do the upgrade the next day, under human supervision. Kind regards, Andrei -- http://wiki.debian.org/FAQsFromDebianUser Offtopic discussions among Debian users and developers: http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic http://nuvreauspam.ro/gpg-transition.txt signature.asc Description: Digital signature
Re: Shutdown computer after a specific command has been executed
On Thu, 12 Dec 2013 16:21:34 +0100 Ralf Mardorf wrote: > On Thu, 2013-12-12 at 19:17 +0400, Reco wrote: > > Still, if one has desire to blow legs off: > > :D > > > sudo sh -c "apt-get update && apt-get upgrade -y ; poweroff" > > but I would recommend > > sudo sh -c "apt-get update && apt-get dist-upgrade -y ; poweroff" And I'd don't. 'dist-upgrade' can install new packages (and _usually_ nothing breaks from installing new packages), but more important - it can _remove_ existing ones (and that _surely_ can break things). 'apt-get upgrade' on the other hand is usually considered safe enough. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131212193112.2734b3fb98bbe5b3fb4e1...@gmail.com
Re: Shutdown computer after a specific command has been executed
On Thu, 2013-12-12 at 16:21 +0100, Ralf Mardorf wrote: > On Thu, 2013-12-12 at 19:17 +0400, Reco wrote: > > Still, if one has desire to blow legs off: > > :D > > > sudo sh -c "apt-get update && apt-get upgrade -y ; poweroff" > > but I would recommend > > sudo sh -c "apt-get update && apt-get dist-upgrade -y ; poweroff" PS: Suggestion: Before running it, burning a live media and reading how to use chroot, resp. making a backup of the whole Debian install and reading how to restore it might be a good idea. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386861844.1257.306.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On Thu, 2013-12-12 at 19:17 +0400, Reco wrote: > Still, if one has desire to blow legs off: :D > sudo sh -c "apt-get update && apt-get upgrade -y ; poweroff" but I would recommend sudo sh -c "apt-get update && apt-get dist-upgrade -y ; poweroff" -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386861694.1257.304.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On Thu, 12 Dec 2013 16:10:44 +0100 Ralf Mardorf wrote: > On Thu, 2013-12-12 at 18:57 +0400, Reco wrote: > > sudo sh -c "apt-get update && apt-get upgrade -y && poweroff" > > > > That's more like it. Depending on a hardware, 'shutdown -h now' can > > leave the power on. > > :D We are close to solve it :D. > > && apt-get upgrade -y && poweroff > if the upgrade fails, it won't shutdown, then > it won't go off-line and be a big issue for the OP. That's intentional. Failed upgrade needs human intervention, and that trick is hard to accomplish if the box goes down. Still, if one has desire to blow legs off: sudo sh -c "apt-get update && apt-get upgrade -y ; poweroff" Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131212191705.e9b01b72dd06919e5302f...@gmail.com
Re: Shutdown computer after a specific command has been executed
On Thu, 2013-12-12 at 16:10 +0100, Ralf Mardorf wrote: > sudo sh -c "apt-get update && apt-get dist-upgrade -y ; poweroff" sudo sh -c "apt-get update && apt-get dist-upgrade --dry-run ; apt-get dist-upgrade -y ; poweroff" -y without a dry run :S, OTOH, the OP want's to go to sleep, so the dry-run first doesn't improve something. It's simply a bad idea to automate an upgrade. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386861344.1257.302.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On Thu, 2013-12-12 at 18:57 +0400, Reco wrote: > sudo sh -c "apt-get update && apt-get upgrade -y && poweroff" > > That's more like it. Depending on a hardware, 'shutdown -h now' can > leave the power on. :D We are close to solve it :D. && apt-get upgrade -y && poweroff if the upgrade fails, it won't shutdown, then it won't go off-line and be a big issue for the OP. sudo sh -c "apt-get update && apt-get dist-upgrade -y ; poweroff" -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386861044.1257.298.camel@archlinux
Re: Shutdown computer after a specific command has been executed
Hi. On Thu, 12 Dec 2013 14:58:35 +0100 "Gian Uberto Lauri" wrote: > Osamu Aoki writes: > > But I want one line solution :-) > > > > sudo sh -c "apt-get update && apt-get upgrade; shutdown -h now" > > But there is the case where apt-get want a reply for the user and that > is 'N' :) !! Baka!!! :) sudo sh -c "apt-get update && apt-get upgrade -y && poweroff" That's more like it. Depending on a hardware, 'shutdown -h now' can leave the power on. Reco -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131212185745.23235a8cb651c7d9cced0...@gmail.com
Re: Shutdown computer after a specific command has been executed
Ralf Mardorf writes: > On Thu, 2013-12-12 at 15:33 +0100, Gian Uberto Lauri wrote: > > Sorry, it may ask if it has to preserve or not a configuration file > > modified locally when a new version arrives with the package. > > Good point, I don't use apt that often, because my "main" distro isn't > Debian. I guess there's an option to always confirm. Indeed, and is -Y, but there are some cases where it's bad, i.e. when the answer must be no :) > Btw. dist-upgrade > anyway might be better than upgrade. Thank you for sending me back to the man page to check the real meaning of dist-upgrade! I thought it was for hot distribution level upgrade but it has also an use for normal software packet updating. I thik I will stick to upgrade and accept to have some packet held back. My work was not hindered by that, at least until now... O.K. for work I use almost non-debian distributed software... -- /\ ___Ubuntu: ancient /___/\_|_|\_|__|___Gian Uberto Lauri_ African word //--\| | \| | Integralista GNUslamicomeaning "I can \/ coltivatore diretto di software not install già sistemista a tempo (altrui) perso...Debian" Warning: gnome-config-daemon considered more dangerous than GOTO -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21161.52771.153839.857...@mail.eng.it
Re: Shutdown computer after a specific command has been executed
On Thu, 2013-12-12 at 15:33 +0100, Gian Uberto Lauri wrote: > Sorry, it may ask if it has to preserve or not a configuration file > modified locally when a new version arrives with the package. Good point, I don't use apt that often, because my "main" distro isn't Debian. I guess there's an option to always confirm. Btw. dist-upgrade anyway might be better than upgrade. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386859389.1257.286.camel@archlinux
Re: Shutdown computer after a specific command has been executed
Ralf Mardorf writes: > On Thu, 2013-12-12 at 14:58 +0100, Gian Uberto Lauri wrote: > > Osamu Aoki writes: > > > But I want one line solution :-) > > > > > > sudo sh -c "apt-get update && apt-get upgrade; shutdown -h now" > > > > But there is the case where apt-get want a reply for the user and that > > is 'N' :) !! Baka!!! :) > > apt-get upgrade will ask the user to upgrade or not and that is wanted, > assumed the update was successful. Sorry, it may ask if it has to preserve or not a configuration file modified locally when a new version arrives with the package. -- /\ ___Ubuntu: ancient /___/\_|_|\_|__|___Gian Uberto Lauri_ African word //--\| | \| | Integralista GNUslamicomeaning "I can \/ coltivatore diretto di software not install già sistemista a tempo (altrui) perso...Debian" Warning: gnome-config-daemon considered more dangerous than GOTO -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21161.51499.194568.966...@mail.eng.it
Re: Shutdown computer after a specific command has been executed
On Thu, 2013-12-12 at 14:58 +0100, Gian Uberto Lauri wrote: > Osamu Aoki writes: > > But I want one line solution :-) > > > > sudo sh -c "apt-get update && apt-get upgrade; shutdown -h now" > > But there is the case where apt-get want a reply for the user and that > is 'N' :) !! Baka!!! :) apt-get upgrade will ask the user to upgrade or not and that is wanted, assumed the update was successful. This line is ok, I just have doubts if there is anything less good with using sudo sh, I will ask detailed about it in some minutes, since I have to reboot first. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386858386.1257.278.camel@archlinux
Re: Shutdown computer after a specific command has been executed
Osamu Aoki writes: > But I want one line solution :-) > > sudo sh -c "apt-get update && apt-get upgrade; shutdown -h now" But there is the case where apt-get want a reply for the user and that is 'N' :) !! Baka!!! :) -- /\ ___Ubuntu: ancient /___/\_|_|\_|__|___Gian Uberto Lauri_ African word //--\| | \| | Integralista GNUslamicomeaning "I can \/ coltivatore diretto di software not install già sistemista a tempo (altrui) perso...Debian" Warning: gnome-config-daemon considered more dangerous than GOTO -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21161.49419.238815.917...@mail.eng.it
Re: Shutdown computer after a specific command has been executed
Hi, On Mon, Dec 09, 2013 at 02:38:45PM +0100, Ralf Mardorf wrote: > One way would be to use a script that runs e.g. apt-get and then the > shutdown command. > > #!/bin/sh > apt-get update > apt-get upgrade > shutdown -h now # or poweroff or halt > > >> If you want it shut down regardless of the outcome of apt, then this > > >> should do it: > > >> > > >> sudo apt-get upgrade; sudo shutdown -h now > > > > > > Wrong, if the upgrade should take to long, then you need to type the > > > password after the upgrade. Better run > > > > > > $ sudo -i > > > # apt-get update ; apt-get upgrade ; shutdown -h now I think Ralf is right on everything he mentioned. But I want one line solution :-) sudo sh -c "apt-get update && apt-get upgrade; shutdown -h now" Osamu -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131212134904.GD6615@goofy
Re: Re: Shutdown computer after a specific command has been executed
Thank you everyone for joining me in this conversation. And sorry, my Internet wasn't Broadband. It's Dial-up indeed. Now, in a nutshell, what I have, is a command that would do the job for me, no matter how long it takes to execute the command. The following could be considered as an example: */$ sudo -i/**/ /**/# apt-get update; apt-get upgrade; shutdown -h now/**/ /*I would try it myself though. Hope this works. With thanks, Muntasim-Ul-Haque
Re: Shutdown computer after a specific command has been executed
Tony van der Hoff writes: > On 09/12/13 15:16, Lisi Reisz wrote: > > On Monday 09 December 2013 14:03:57 Muntasim-Ul-Haque wrote: > >> I'm a Broadband Internet user and I'm billed for the time > >> my Internet connection is active. Sometimes it happens that I've a > >> large software to install like the TeXworks, which is about 650MB, > >> I think. Or, the system up-gradation, if you may consider. In that > >> case, that would take 6Hrs+ for my Internet connection. > > > > I'm puzzled. How can broadband take six hours to do an upgrade? I > > would expect dial-up to do so, but broadband?? > > > > I even looked in Wiktionary to see whether it was another word which > > changes its meaning as it crosses the pond, but that appears not to > > be the case. :-? > > I don't think he meant broadband. Another scenario could be that: Muntasim-Ul-Haque [PC]###[BROADBAND]~~~[ANOTHER NET]###[DEBIAN MIRROR] where ### are high speed net (may be charged on traffic basis, i.e. UMTS) and ~~~ is a slw branch where the traffic to Debian Mirror is routed, to know exactly what happens one should be Mr. Ul-Haque (I hope I got the family name right) or at least do some inquiry from his computer. -- /\ ___Ubuntu: ancient /___/\_|_|\_|__|___Gian Uberto Lauri_ African word //--\| | \| | Integralista GNUslamicomeaning "I can \/ coltivatore diretto di software not install già sistemista a tempo (altrui) perso...Debian" Warning: gnome-config-daemon considered more dangerous than GOTO -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21157.60763.440493.300...@mail.eng.it
Re: Shutdown computer after a specific command has been executed
On Monday, December 09, 2013 03:56:12 PM Tony van der Hoff wrote: > On 09/12/13 15:16, Lisi Reisz wrote: > > On Monday 09 December 2013 14:03:57 Muntasim-Ul-Haque wrote: > >> I'm a Broadband Internet user and I'm billed for the time > >> my Internet connection is active. Sometimes it happens that I've a > >> large software to install like the TeXworks, which is about 650MB, > >> I think. Or, the system up-gradation, if you may consider. In that > >> case, that would take 6Hrs+ for my Internet connection. > > > > I'm puzzled. How can broadband take six hours to do an upgrade? I > > would expect dial-up to do so, but broadband?? > > > > I even looked in Wiktionary to see whether it was another word which > > changes its meaning as it crosses the pond, but that appears not to > > be the case. :-? > > I don't think he meant broadband. BB is always-on, and nobody gets > charged by the minute. By the byte, more likely. Shutting down the > computer won't disconnect the session. > This depends on the ISP. My ISP does flat fees for its standard connection. But if you go for their "uber fantastic awesome uber uber great awesome uber" plans they'll start charging for "overage" and usually set their cap unreasonably low. > Therefore one must conclude he's actually on dial-up, in which case both > of his concerns (connect time and transmission rate) are valid. > > As someone else said, the sensible thing to do would be to drop theline, > rather than kill the computer. Conrad -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1387432.NNSKksPXA6@twilight
Re: Shutdown computer after a specific command has been executed
On 09/12/13 15:16, Lisi Reisz wrote: > On Monday 09 December 2013 14:03:57 Muntasim-Ul-Haque wrote: >> I'm a Broadband Internet user and I'm billed for the time >> my Internet connection is active. Sometimes it happens that I've a >> large software to install like the TeXworks, which is about 650MB, >> I think. Or, the system up-gradation, if you may consider. In that >> case, that would take 6Hrs+ for my Internet connection. > > I'm puzzled. How can broadband take six hours to do an upgrade? I > would expect dial-up to do so, but broadband?? > > I even looked in Wiktionary to see whether it was another word which > changes its meaning as it crosses the pond, but that appears not to > be the case. :-? I don't think he meant broadband. BB is always-on, and nobody gets charged by the minute. By the byte, more likely. Shutting down the computer won't disconnect the session. Therefore one must conclude he's actually on dial-up, in which case both of his concerns (connect time and transmission rate) are valid. As someone else said, the sensible thing to do would be to drop theline, rather than kill the computer. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England | -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52a5e81c.7040...@vanderhoff.org
Re: Shutdown computer after a specific command has been executed
On Monday 09 December 2013 14:03:57 Muntasim-Ul-Haque wrote: > I'm a Broadband Internet user and I'm billed for the time > my Internet connection is active. Sometimes it happens that I've a > large software to install like the TeXworks, which is about 650MB, > I think. Or, the system up-gradation, if you may consider. In that > case, that would take 6Hrs+ for my Internet connection. I'm puzzled. How can broadband take six hours to do an upgrade? I would expect dial-up to do so, but broadband?? I even looked in Wiktionary to see whether it was another word which changes its meaning as it crosses the pond, but that appears not to be the case. :-? Lisi -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201312091516.42820.lisi.re...@gmail.com
Re: Re: Shutdown computer after a specific command has been executed
On Mon, 2013-12-09 at 20:03 +0600, Muntasim-Ul-Haque wrote: > Thanks Lars, Mardorf, Ashmore, Lauri and Jorgensen for your advice. I > needed it badly and your advice showed me the way. Thanks a lot. > To Jorgensen: I'm a Broadband Internet user and I'm billed for the time > my Internet connection is active. Sometimes it happens that I've a large > software to install like the TeXworks, which is about 650MB, I think. > Or, the system up-gradation, if you may consider. In that case, that > would take 6Hrs+ for my Internet connection. Sometimes I execute the > command and go to sleep. If the command execution completes and the > Internet is still on, then it would be a waste of my Internet. That's > why I needed a command that would shutdown the computer after the > command execution. That's it. And thanks for your concern. > With thanks, > Muntasim-Ul-Haque You could use a command to go off-line, instead of shutting down the computer. It depends how often, long the computer is in use. A shutdown and startup isn't good for the drives, OTOH turning a computer on, when it's just used half an hour a day, would be bad. Suspend etc. might nt work when e.g. using a special sound server, such as jackd. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386601609.14806.140.camel@archlinux
Re: Re: Shutdown computer after a specific command has been executed
Muntasim-Ul-Haque writes: > To Jorgensen: I'm a Broadband Internet user and I'm billed for the time ... > command and go to sleep. If the command execution completes and the > Internet is still on, then it would be a waste of my Internet. That's > why I needed a command that would shutdown the computer You could drop the internet connection only instead of shutting down the whole machine. I know that shutting down the machine saves electricity, but heating and cooling is the mechanical stress that hits the non-moving components of your computer, computer that turn off less often live longer. Now it's all to see what is cheaper (computer or power) and/or pollutes less (computer waste components or power plant)... -- /\ ___Ubuntu: ancient /___/\_|_|\_|__|___Gian Uberto Lauri_ African word //--\| | \| | Integralista GNUslamicomeaning "I can \/ coltivatore diretto di software not install già sistemista a tempo (altrui) perso...Debian" Warning: gnome-config-daemon considered more dangerous than GOTO -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21157.54083.1078.947...@mail.eng.it
Re: Re: Shutdown computer after a specific command has been executed
Thanks Lars, Mardorf, Ashmore, Lauri and Jorgensen for your advice. I needed it badly and your advice showed me the way. Thanks a lot. To Jorgensen: I'm a Broadband Internet user and I'm billed for the time my Internet connection is active. Sometimes it happens that I've a large software to install like the TeXworks, which is about 650MB, I think. Or, the system up-gradation, if you may consider. In that case, that would take 6Hrs+ for my Internet connection. Sometimes I execute the command and go to sleep. If the command execution completes and the Internet is still on, then it would be a waste of my Internet. That's why I needed a command that would shutdown the computer after the command execution. That's it. And thanks for your concern. With thanks, Muntasim-Ul-Haque -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52a5cdcd.1000...@inventati.org
Re: Shutdown computer after a specific command has been executed
On Mon, 2013-12-09 at 15:34 +0200, Lars Noodén wrote: > On 12/09/2013 03:30 PM, Ralf Mardorf wrote: > > On Mon, 2013-12-09 at 14:48 +0200, Lars Noodén wrote: > >> If you want it shut down regardless of the outcome of apt, then this > >> should do it: > >> > >> sudo apt-get upgrade; sudo shutdown -h now > > > > Wrong, if the upgrade should take to long, then you need to type the > > password after the upgrade. Better run > > > > $ sudo -i > > # apt-get update ; apt-get upgrade ; shutdown -h now > > > > Regards, > > Ralf > > It depends on how you have sudoers configured. On some systems certain > combinations of programs+options need no password. It's up to the > sysadmin and the users. That's correct, but the default for most distros usually is to have a timeout for sudo command , but not for sudo -i . As already pointed out, you also can give su a timeout, IIRC it's possible to have a timeout only if the computer is idle, as long as something happens the timeout won't start. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386596325.14806.112.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On 12/09/2013 03:30 PM, Ralf Mardorf wrote: > On Mon, 2013-12-09 at 14:48 +0200, Lars Noodén wrote: >> If you want it shut down regardless of the outcome of apt, then this >> should do it: >> >> sudo apt-get upgrade; sudo shutdown -h now > > Wrong, if the upgrade should take to long, then you need to type the > password after the upgrade. Better run > > $ sudo -i > # apt-get update ; apt-get upgrade ; shutdown -h now > > Regards, > Ralf It depends on how you have sudoers configured. On some systems certain combinations of programs+options need no password. It's up to the sysadmin and the users. Regards, /Lars -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52a5c6eb.8060...@gmail.com
Re: Shutdown computer after a specific command has been executed
On Mon, 2013-12-09 at 14:48 +0200, Lars Noodén wrote: > If you want it shut down regardless of the outcome of apt, then this > should do it: > > sudo apt-get upgrade; sudo shutdown -h now Wrong, if the upgrade should take to long, then you need to type the password after the upgrade. Better run $ sudo -i # apt-get update ; apt-get upgrade ; shutdown -h now Regards, Ralf -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386595826.14806.109.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On Mon, 2013-12-09 at 14:10 +0100, Gian Uberto Lauri wrote: > If you execute as root (better than using sudo) you can > either issue from the # prompt Andrei already pointed out on another thread how to use sudo and I repeated it for this thread. You can configure su to have a timeout too, but su hasn't by default, neither has sudo -i. There is no need to run sudo again and again, simply run sudo -i one time, like you do when using su. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386595525.14806.106.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On Mon, 2013-12-09 at 14:16 +0100, Ralf Mardorf wrote: > On Mon, 2013-12-09 at 13:11 +, Karl E. Jorgensen wrote: > > Hi > > > > On Mon, Dec 09, 2013 at 05:42:17PM +0600, Muntasim-Ul-Haque wrote: > > > Hi, > > > I need a tool that would make sure that, my computer would shutdown after > > > a > > > specific command has been executed. This tool would just wait for the > > > Terminal > > > for executing a command, like 'sudo apt-get upgrade' and then after the > > > command > > > has been executed, my computer would shutdown. Is that possible? Is there > > > a > > > tool or anything out there that can do this for me? Let me know. It would > > > be of > > > great help. Thanks in advance. > > > > Others have given useful advice on how to achieve this, but I'm > > curious: WHY ? It appears non-sensical to upgrade a box and then > > switch it off? Not even reboot!? > > > > I may be a purist, but I find the whole notion of "shutdown" or > > "reboot" abhorrent. That's something you'd do before physically moving > > a desktop (perhaps: suspend-to-disk seems better here), or after a > > kernel upgrade (but then it is "reboot", not "shutdown"). > > Even a kernel upgrade doesn't need a real reboot, there's another way, > but it's OT. A reason to run an upgrade and after that to shutdown might > be that you want to leave home and only run an upgrade before you go > away and the computer should not be on, when you're not at home. I > wouldn't recommend it, IMO it's better to take care when upgrading. A good example, somebody want's to make a backup to a Green drive. The user likes gvfs, but when not at home, after the backup is finished gvfs shouldn't wake up the drive again and again. Nobody is there to unplug the Green drive, so a shutdown would be a good idea. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386595157.14806.103.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On Mon, 2013-12-09 at 13:11 +, Karl E. Jorgensen wrote: > Hi > > On Mon, Dec 09, 2013 at 05:42:17PM +0600, Muntasim-Ul-Haque wrote: > > Hi, > > I need a tool that would make sure that, my computer would shutdown after a > > specific command has been executed. This tool would just wait for the > > Terminal > > for executing a command, like 'sudo apt-get upgrade' and then after the > > command > > has been executed, my computer would shutdown. Is that possible? Is there a > > tool or anything out there that can do this for me? Let me know. It would > > be of > > great help. Thanks in advance. > > Others have given useful advice on how to achieve this, but I'm > curious: WHY ? It appears non-sensical to upgrade a box and then > switch it off? Not even reboot!? > > I may be a purist, but I find the whole notion of "shutdown" or > "reboot" abhorrent. That's something you'd do before physically moving > a desktop (perhaps: suspend-to-disk seems better here), or after a > kernel upgrade (but then it is "reboot", not "shutdown"). Even a kernel upgrade doesn't need a real reboot, there's another way, but it's OT. A reason to run an upgrade and after that to shutdown might be that you want to leave home and only run an upgrade before you go away and the computer should not be on, when you're not at home. I wouldn't recommend it, IMO it's better to take care when upgrading. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386594976.14806.100.camel@archlinux
Re: Shutdown computer after a specific command has been executed
Hi On Mon, Dec 09, 2013 at 05:42:17PM +0600, Muntasim-Ul-Haque wrote: > Hi, > I need a tool that would make sure that, my computer would shutdown after a > specific command has been executed. This tool would just wait for the Terminal > for executing a command, like 'sudo apt-get upgrade' and then after the > command > has been executed, my computer would shutdown. Is that possible? Is there a > tool or anything out there that can do this for me? Let me know. It would be > of > great help. Thanks in advance. Others have given useful advice on how to achieve this, but I'm curious: WHY ? It appears non-sensical to upgrade a box and then switch it off? Not even reboot!? I may be a purist, but I find the whole notion of "shutdown" or "reboot" abhorrent. That's something you'd do before physically moving a desktop (perhaps: suspend-to-disk seems better here), or after a kernel upgrade (but then it is "reboot", not "shutdown"). -- Karl E. Jorgensen -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20131209131139.GA23207@hawking
Re: Shutdown computer after a specific command has been executed
On Mon, 2013-12-09 at 13:02 +, Philip Ashmore wrote: > but I think sudo has a timeout sudo -i and then run a script, if you not explicitly configured it to have a timeout it has got no timeout. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386594696.14806.97.camel@archlinux
Re: Shutdown computer after a specific command has been executed
Muntasim-Ul-Haque writes: > Hi, > I need a tool that would make sure that, my computer would shutdown > after a specific command has been executed. This tool would just wait > for the Terminal for executing a command, like '/sudo apt-get upgrade/' > and then after the command has been executed, my computer would > shutdown. If you execute as root (better than using sudo) you can either issue from the # prompt command; shutdown -h now that shuts down the machine either if is successful or fails while command && shutdown -h now shuts down the machine only if is successful. On the other hand command || shutdown -h now shuts down the machine only if fails If you don't run as root you must either wait for to end (to type the password) or be sure that it completes before the validity of the sudo password cache expires. -- /\ ___Ubuntu: ancient /___/\_|_|\_|__|___Gian Uberto Lauri_ African word //--\| | \| | Integralista GNUslamicomeaning "I can \/ coltivatore diretto di software not install già sistemista a tempo (altrui) perso...Debian" Warning: gnome-config-daemon considered more dangerous than GOTO -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/21157.49468.366735.40...@mail.eng.it
Re: Shutdown computer after a specific command has been executed
On 09/12/13 11:42, Muntasim-Ul-Haque wrote:
> Hi,
> I need a tool that would make sure that, my computer would shutdown
> after a specific command has been executed. This tool would just wait
> for the Terminal for executing a command, like '/sudo apt-get upgrade/'
> and then after the command has been executed, my computer would
> shutdown. Is that possible? Is there a tool or anything out there that
> can do this for me? Let me know. It would be of great help. Thanks in
> advance.
> Muntasim-Ul-Haque
to shut down the computer from a script or command line use
shutdown -h now
It needs elevated(root) permissions so initially I was tempted to use
sudo shutdown -h now
but I think sudo has a timeout after which it prompts you to re-enter
your password, probably not what you want.
So the solution would be to "sudo" everything and drop to a regular user
to run your command, unless it too needs to be run as root.
My bash scripting isn't sharp enough to do it but here's a place to
start from for user "bob", uid=1001
sudo { su -l bob -c 'echo "$UID"' }; echo "$UID"
Yes it doesn't work, but if you can tweak it to output "1001" and "0"
then you've solved it.
Maybe it's easier to create a script file that takes your command then
shuts down.
There are also other ways to do this that depend on which desktop
environment you're using.
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/52a5bf4b.9030...@philipashmore.com
Re: Shutdown computer after a specific command has been executed
On Mon, 2013-12-09 at 17:42 +0600, Muntasim-Ul-Haque wrote: > Hi, > I need a tool that would make sure that, my computer would shutdown > after a specific command has been executed. This tool would just wait > for the Terminal for executing a command, like 'sudo apt-get upgrade' > and then after the command has been executed, my computer would > shutdown. Is that possible? Is there a tool or anything out there that > can do this for me? Let me know. It would be of great help. Thanks in > advance. > Muntasim-Ul-Haque One way would be to use a script that runs e.g. apt-get and then the shutdown command. #!/bin/sh apt-get update apt-get upgrade shutdown -h now # or poweroff or halt -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1386593547.14806.88.camel@archlinux
Re: Shutdown computer after a specific command has been executed
On 12/09/2013 01:42 PM, Muntasim-Ul-Haque wrote: > Hi, > I need a tool that would make sure that, my computer would shutdown > after a specific command has been executed. This tool would just wait > for the Terminal for executing a command, like '/sudo apt-get upgrade/' > and then after the command has been executed, my computer would > shutdown. Is that possible? Is there a tool or anything out there that > can do this for me? Let me know. It would be of great help. Thanks in > advance. > Muntasim-Ul-Haque This would do it, but only if apt succeeds: sudo apt-get upgrade && sudo shutdown -h now If you want it shut down regardless of the outcome of apt, then this should do it: sudo apt-get upgrade; sudo shutdown -h now regards, /Lars -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/52a5bc14.7030...@gmail.com
Re: shutdown and restart menu item disappeared from user menu
On Sunday 09 June 2013 04:43 PM, Greg wrote: Is there a way to install these extensions to all gnome users? On Sun, 2013-06-09 at 11:15 +0530, Kailash wrote: On Saturday 08 June 2013 03:04 PM, Antti Talsta wrote: On Sat, Jun 08, 2013 at 05:07:00AM -0400, A Fascilla wrote: On my system on one user (the other user are unaffected) there is no more a command to restart or shutdown the computer in the user menu in Gnome (I mean the one in the top-right corner). Press Alt and click your username. From some days the menu ends with the line suspend, while in the past (and still for the other users) I had to more lines: restart and shutdown. Difference between Gnome 3 and Classic AFAIK. Hi, You can install gnome-shell-extensions and you should have the power off option available. https://extensions.gnome.org/ Sincerely, Kailash Hi, This page gives you the bare bones of what needs to be done: https://live.gnome.org/GnomeShell/Extensions In short you need to do two things: 1. Install the extensions system-wide or per user 2. Enable the extensions Step 1. Install the extension system-wide or per user: If system wide then they need to be copied to the folders: /usr/share/gnome-shell/extensions and /usr/local/share/gnome-shell/extensions. If per user then in folder: ~/.local/share/gnome-shell/extensions The name of the folder is the extension name that you'll use in the next step. Step 2. Enable it. Enabling involves using gsettings like so: gsettings set org.gnome.shell enabled-extensions "['folder>','']" So on my machine, it is: gsettings set org.gnome.shell enabled-extensions "['ext-hel...@amanda.darkdna.net', 'd...@gnome-shell-extensions.gcampax.github.com']" Hope this helps! Kailash -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51b5ead3.3000...@gmail.com
Re: shutdown and restart menu item disappeared from user menu
On Sun, Jun 09, 2013 at 04:38:40AM -0400, A Fascilla wrote: > > "Kailash" wrote: > > >You can install gnome-shell-extensions and you should have the power off > >option available. > >https://extensions.gnome.org/ > > Now I have understood it is the "Alternative Status Menu" extension > > https://extensions.gnome.org/extension/5/alternative-status-menu/ > > and can be enable or disabled from the link above or from > > https://extensions.gnome.org/local/ > > (I write this here so that who has the same problem can easily find how to > make the change.) > > > I have to conclude that I had it always been installed (since transition > from squeeze) and I had never realized that what I see was not the normal > plain gnome. > > I am pretty sure I have not turned it off, so it is a little strange that the > menu changed (the only thing I remember I have done was to use the suspend > function, while I usually use the shutdown). > > I have struggled to look in the gnome options, but with no luck. And now I > can understand the reason: it is an extension not an option. > Thank you very much, Kailash, this solve the mystery ... > and many thanks to Antti too If you install the "Advanced Settings" panel (Google for it re Gnome-Shell) you can enable/disable all installed Gnome-Shell extensions. I love Gnome-Shell -- Didn't at first, but it grows on you. :) > Sincerely, > > Andrea Fascilla > > -- Cheers, Stephen, Toronto My Google+ Profile | http://goo.gl/JbQsq -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130609113811.ga10...@thunkpad.gateway.2wire.net
Re: shutdown and restart menu item disappeared from user menu
Is there a way to install these extensions to all gnome users? On Sun, 2013-06-09 at 11:15 +0530, Kailash wrote: > On Saturday 08 June 2013 03:04 PM, Antti Talsta wrote: > > On Sat, Jun 08, 2013 at 05:07:00AM -0400, A Fascilla wrote: > >> On my system on one user (the other user are unaffected) there is no > >> more a command to restart or shutdown the computer in the user menu in > >> Gnome (I mean the one in the top-right corner). > > > > Press Alt and click your username. > > > >> > From some days the menu ends with the line suspend, while in the past > >>> (and still for the other users) I had to more lines: restart and > >>> shutdown. > > > > Difference between Gnome 3 and Classic AFAIK. > > > Hi, > > You can install gnome-shell-extensions and you should have the power off > option available. > https://extensions.gnome.org/ > > Sincerely, > Kailash > > -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1370776411.4560.1.ca...@fast.cercy.net
Re: shutdown and restart menu item disappeared from user menu
"Kailash" wrote: >You can install gnome-shell-extensions and you should have the power off >option available. >https://extensions.gnome.org/ Now I have understood it is the "Alternative Status Menu" extension https://extensions.gnome.org/extension/5/alternative-status-menu/ and can be enable or disabled from the link above or from https://extensions.gnome.org/local/ (I write this here so that who has the same problem can easily find how to make the change.) I have to conclude that I had it always been installed (since transition from squeeze) and I had never realized that what I see was not the normal plain gnome. I am pretty sure I have not turned it off, so it is a little strange that the menu changed (the only thing I remember I have done was to use the suspend function, while I usually use the shutdown). I have struggled to look in the gnome options, but with no luck. And now I can understand the reason: it is an extension not an option. Thank you very much, Kailash, this solve the mystery ... and many thanks to Antti too Sincerely, Andrea Fascilla -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130609043840.22...@web003.roc2.bluetie.com
Re: shutdown and restart menu item disappeared from user menu
On Saturday 08 June 2013 03:04 PM, Antti Talsta wrote: On Sat, Jun 08, 2013 at 05:07:00AM -0400, A Fascilla wrote: On my system on one user (the other user are unaffected) there is no more a command to restart or shutdown the computer in the user menu in Gnome (I mean the one in the top-right corner). Press Alt and click your username. > From some days the menu ends with the line suspend, while in the past (and still for the other users) I had to more lines: restart and shutdown. Difference between Gnome 3 and Classic AFAIK. Hi, You can install gnome-shell-extensions and you should have the power off option available. https://extensions.gnome.org/ Sincerely, Kailash -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/51b41661.6010...@gmail.com
Re: shutdown and restart menu item disappeared from user menu
On Sat, Jun 08, 2013 at 05:07:00AM -0400, A Fascilla wrote: > On my system on one user (the other user are unaffected) there is no > more a command to restart or shutdown the computer in the user menu in > Gnome (I mean the one in the top-right corner). Press Alt and click your username. > >From some days the menu ends with the line suspend, while in the past > >(and still for the other users) I had to more lines: restart and > >shutdown. Difference between Gnome 3 and Classic AFAIK. -- Antti Talsta -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20130608093417.ga6...@criss.dnsalias.org
Re: Shutdown Problem
On Mon 08 Oct 2012 at 10:27:05 -0400, Stephen P. Molnar wrote: > Debian 6.0.6 (64 bit)/KDE 4.4.5 > > For some reason when I shutdown the system, either as a user or as > root, the process hangs on: > > Currently running process (pstree): > > The only recourse I seem to have is to hit the reset button. > Reinstalling psmisc did not solve the problem. Everything you see on the screen when the hang occurs can only be of help. pstree itself is probably not the problem. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121008204020.GG30872@desktop
Re: Shutdown and suspend not working on laptop
On 16 July 2012 01:34, DJ Amireh wrote: > I am having trouble with power management on my laptop. I cannot get suspend > or shutdown to work, attempting either causes my laptop to have a black > screen and not respond to any input and I am forced to manually shutdown by > holding the power button. I am running Debian Squeeze with KDE. Shutting > down I attempt through KDE's menu and through running "shutdown." Suspending > I attempt by shutting my laptop lid on battery which causes it to "Suspend > to RAM." My laptop is a Compaq Presario CQ61. I would appreciate any help. > > Thanks I run Wheezy on an Acer Aspire One where wake-up from suspend does not work, it just crashes horribly (kernel panic?). Same with Debian Stable and several other Linux distributions I've tried on that particular notebook. /Helgi Örn -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/cakulek7bxlp5rxjnpkjv0gu5mawkhuy+-ndc0c+ck2mdc0s...@mail.gmail.com
Re: shutdown not working in Gnome / KDE
On Mon, 19 Mar 2012 20:15:58 +0100, Peter Baranyi wrote: > On Mon, 2012-03-19 at 11:20 +, Camaleón wrote: >> On Sun, 18 Mar 2012 21:44:35 +0100, Peter Baranyi wrote: > >> If it used to work, I would report it. >> > you mean with the reportbug program? Or manually (by e-mail), you can choose what's best way for you: http://www.debian.org/Bugs/Reporting.en.html > I don't know in which package this bug is. (I never reported any Debian > bugs before) As the problem it presents when you're inside X (you can shutdown the system on a tty) you can register the bug against gnome or kde package. Don't worry for a bad assignation, devels/packagers will correct it should needed. >> > Debian unstable, 3.1.0-1-686-pae >> >> Unstable and GNOME2? :-? > I didn't do a dist upgrade, so some packages are older. I wanted to keep > gnome2 because I won't use gnome3. This can be also a source for problems and a big can of worms... GNOME 2 (and its associated libraries) will be dropped sooner or later and keeping it up-to-date from wheezy onwards it does not have to be an easy task. >> Anyway, that kernel is old. Try to update it (now 3.2.10). > OK I will try it, thanks. It sounds more a DE issue than nothing but who knows, it may help. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jk893r$6c2$3...@dough.gmane.org
Re: shutdown not working in Gnome / KDE
On Mon, 2012-03-19 at 11:20 +, Camaleón wrote: > On Sun, 18 Mar 2012 21:44:35 +0100, Peter Baranyi wrote: > If it used to work, I would report it. > you mean with the reportbug program? I don't know in which package this bug is. (I never reported any Debian bugs before) > > Debian unstable, 3.1.0-1-686-pae > > Unstable and GNOME2? :-? I didn't do a dist upgrade, so some packages are older. I wanted to keep gnome2 because I won't use gnome3. > Anyway, that kernel is old. Try to update it (now 3.2.10). OK I will try it, thanks. Regards, Peter -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1332184558.4994.11.camel@timeout
Re: shutdown not working in Gnome / KDE
On Sun, 18 Mar 2012 21:44:35 +0100, Peter Baranyi wrote: > I can only shut down my pc from a root terminal with 'poweroff' (or > shutdown) but not from graphical environments. > > From Gnome2, sometimes it shuts down, sometimes I get back to gdm. From > gdm, the shutdown action sometimes works, sometimes it just quits gdm. GNOME2? What Debian flavour are you running? > In KDE 4.7.4, shutdown in the application launcher menu does nothing, or > dims the screen. > > How do I fix this? I do not see any error messages. If it used to work, I would report it. > Debian unstable, 3.1.0-1-686-pae Unstable and GNOME2? :-? Anyway, that kernel is old. Try to update it (now 3.2.10). Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jk74pu$6c2$6...@dough.gmane.org
Re: Shutdown problem -- cron job related?
On Sun, May 9, 2010 at 18:42, David Baron wrote:
> >> At certain times, seems Friday noontime, I am unable to shutdown the
> >> system. Instead of the usual scripts to killing all processes,
> unmounting
> >> everything and will now halt, goodby, I get:
> >>
> >> process running pstree (or something like that)
> >> shutdown aborted
> >>
> >> At this point, the system (or at least any console or UI) is dead.
> >>
> >> What it this?
>
>
> > Just see which process is running pstree.
> > "ps -eaf | grep pstree"
> > You could find the parent pid of pstree (second column).
> > Look at the parent of pstree, and the process started this one.
> > If you go back that way, finally you will reach init, but before that you
> > could find which system process started these processes.
> I'll have to try it when I know the thing is running.
>
> > As I recall, pstree is not part of basic installation.
> > It was put to do some scripting, regarding found, in
> > perl/python?
> > My first bet would be to remove offensive cron line and
> > shutdown normally. Than to do filesystem checks. Next,
> > to set cron to use pstree as a regular user. I think that
> > shutdown was done in some parts, aka closed network. What
> > has to wait, hangs the system.
> > Otherwise, there is a chance that some housekeeping pro-
> > cesses are started at noon every day. You could always
> > look at /etc directory and find them. Some unices have
> > it in /etc/periodic/daily. It starts with #!/bin/sh.
> > Another clue may be in /var/log, as a result of newsyslog.conf.
>
> I have no /etc/periodic and no logs for pstree
>
> I manually ran it (x11 variant) and this is what I got:
> init-+-Xprt
> |-akonadi_control-+-akonadi_ical_re
> | |-8*[akonadi_kabc_re]
> | |-4*[akonadi_kcal_re]
> | |-42*[akonadi_maildir]
> | |-akonadi_maildis
> | |-akonadi_nepomuk---{akonadi_nepomu}
> | |-akonadi_vcard_r
> | |-akonadiserver-+-mysqld---74*[{mysqld}]
> | | `-66*[{akonadiserver}]
> | `-4*[{akonadi_contro}]
> |-apmd
> |-atd
> |-avahi-daemon---avahi-daemon
> |-boinc
> |-clamd---2*[{clamd}]
> |-console-kit-dae---63*[{console-kit-da}]
> |-cron
> |-cupsd
> |-das_watchdog---{das_watchdog}
> |-3*[dbus-daemon]
> |-2*[dbus-launch]
> |-ddclient
> |-dirmngr
> |-dovecot-+-2*[dovecot-auth]
> | |-imap
> | |-3*[imap-login]
> | `-3*[pop3-login]
> |-exim4
> |-fail2ban-server---6*[{fail2ban-serve}]
> |-fetchmail
> |-2*[getty]
> |-gpm
> |-hald-+-hald-runner-+-hald-addon-inpu
> | | `-hald-addon-stor
> | `-{hald}
> |-in.tftpd
> |-inetd
> |-jackdbus
> |-kaccess
> |-kded4---{kded4}
> |-kdeinit4-+-kio_file
> | |-kio_http_cache_
> | |-kio_imap4
> | |-klauncher
> | |-ksmserver-+-kwin
> | | `-{ksmserver}
> | |-python---python---python
> | `-qjackctl---{qjackctl}
> |-kdm-+-Xorg
> | `-kdm---startkde-+-kwrapper4
> | `-2*[ssh-agent]
> |-kget
> |-kglobalaccel
> |-klipper
> |-klogd
> |-kmail---{kmail}
> |-kmix
> |-knemo
> |-knotify4
> |-korgac---{korgac}
> |-krunner---{krunner}
> |-kxkb---{kxkb}
> |-nepomukserver
> |-plasma-desktop-+-ksysguardd
> |`-7*[{plasma-desktop}]
> |-portmap
> |-postmaster-+-postmaster
> |`-postmaster---postmaster
> |-preload
> |-proftpd
> |-rpc.mountd
> |-rpc.statd
> |-smartd
> |-spamd---2*[spamd]
> |-sshd
> |-svscanboot-+-readproctitle
> |`-svscan
> |-syslogd
> |-tinyproxy---11*[tinyproxy]
> |-udevd---2*[udevd]
> |-xfs
> |-xfstt
> `-yakuake-+-bash---pstree.x11
> `-{yakuake}
> Press return to close
>
> Which would basically reflect what init ran and what kde4 is doing when I
> did
> it. Why would this be stuck at the end?
>
>
> --
> To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact
> listmas...@lists.debian.org
> Archive: http://lists.debian.org/201005091612.7.d_ba...@012.net.il
>
>
pstree is used to list a tree of processes and it should not take much time.
I think your problem is arising from the originator of pstree. Have you
tried using "top" to see any other process is taking cpu/memory? Also take
a look
at all cron related directories and files, all files in /etc/cron.dailly,
/etc/crontab
Re: Shutdown problem -- cron job related?
>> At certain times, seems Friday noontime, I am unable to shutdown the
>> system. Instead of the usual scripts to killing all processes, unmounting
>> everything and will now halt, goodby, I get:
>>
>> process running pstree (or something like that)
>> shutdown aborted
>>
>> At this point, the system (or at least any console or UI) is dead.
>>
>> What it this?
> Just see which process is running pstree.
> "ps -eaf | grep pstree"
> You could find the parent pid of pstree (second column).
> Look at the parent of pstree, and the process started this one.
> If you go back that way, finally you will reach init, but before that you
> could find which system process started these processes.
I'll have to try it when I know the thing is running.
> As I recall, pstree is not part of basic installation.
> It was put to do some scripting, regarding found, in
> perl/python?
> My first bet would be to remove offensive cron line and
> shutdown normally. Than to do filesystem checks. Next,
> to set cron to use pstree as a regular user. I think that
> shutdown was done in some parts, aka closed network. What
> has to wait, hangs the system.
> Otherwise, there is a chance that some housekeeping pro-
> cesses are started at noon every day. You could always
> look at /etc directory and find them. Some unices have
> it in /etc/periodic/daily. It starts with #!/bin/sh.
> Another clue may be in /var/log, as a result of newsyslog.conf.
I have no /etc/periodic and no logs for pstree
I manually ran it (x11 variant) and this is what I got:
init-+-Xprt
|-akonadi_control-+-akonadi_ical_re
| |-8*[akonadi_kabc_re]
| |-4*[akonadi_kcal_re]
| |-42*[akonadi_maildir]
| |-akonadi_maildis
| |-akonadi_nepomuk---{akonadi_nepomu}
| |-akonadi_vcard_r
| |-akonadiserver-+-mysqld---74*[{mysqld}]
| | `-66*[{akonadiserver}]
| `-4*[{akonadi_contro}]
|-apmd
|-atd
|-avahi-daemon---avahi-daemon
|-boinc
|-clamd---2*[{clamd}]
|-console-kit-dae---63*[{console-kit-da}]
|-cron
|-cupsd
|-das_watchdog---{das_watchdog}
|-3*[dbus-daemon]
|-2*[dbus-launch]
|-ddclient
|-dirmngr
|-dovecot-+-2*[dovecot-auth]
| |-imap
| |-3*[imap-login]
| `-3*[pop3-login]
|-exim4
|-fail2ban-server---6*[{fail2ban-serve}]
|-fetchmail
|-2*[getty]
|-gpm
|-hald-+-hald-runner-+-hald-addon-inpu
| | `-hald-addon-stor
| `-{hald}
|-in.tftpd
|-inetd
|-jackdbus
|-kaccess
|-kded4---{kded4}
|-kdeinit4-+-kio_file
| |-kio_http_cache_
| |-kio_imap4
| |-klauncher
| |-ksmserver-+-kwin
| | `-{ksmserver}
| |-python---python---python
| `-qjackctl---{qjackctl}
|-kdm-+-Xorg
| `-kdm---startkde-+-kwrapper4
| `-2*[ssh-agent]
|-kget
|-kglobalaccel
|-klipper
|-klogd
|-kmail---{kmail}
|-kmix
|-knemo
|-knotify4
|-korgac---{korgac}
|-krunner---{krunner}
|-kxkb---{kxkb}
|-nepomukserver
|-plasma-desktop-+-ksysguardd
|`-7*[{plasma-desktop}]
|-portmap
|-postmaster-+-postmaster
|`-postmaster---postmaster
|-preload
|-proftpd
|-rpc.mountd
|-rpc.statd
|-smartd
|-spamd---2*[spamd]
|-sshd
|-svscanboot-+-readproctitle
|`-svscan
|-syslogd
|-tinyproxy---11*[tinyproxy]
|-udevd---2*[udevd]
|-xfs
|-xfstt
`-yakuake-+-bash---pstree.x11
`-{yakuake}
Press return to close
Which would basically reflect what init ran and what kde4 is doing when I did
it. Why would this be stuck at the end?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005091612.7.d_ba...@012.net.il
Re: Shutdown problem -- cron job related
> At certain times, seems Friday noontime, I am unable to shutdown the system. > Instead of the usual scripts to killing all processes, unmounting everything > and will now halt, goodby, I get: > process running pstree (or something like that) > shutdown aborted > At this point, the system (or at least any console or UI) is dead. As I recall, pstree is not part of basic installation. It was put to do some scripting, regarding found, in perl/python? My first bet would be to remove offensive cron line and shutdown normally. Than to do filesystem checks. Next, to set cron to use pstree as a regular user. I think that shutdown was done in some parts, aka closed network. What has to wait, hangs the system. Otherwise, there is a chance that some housekeeping pro- cesses are started at noon every day. You could always look at /etc directory and find them. Some unices have it in /etc/periodic/daily. It starts with #!/bin/sh. Another clue may be in /var/log, as a result of newsyslog.conf. Best regards Zoran -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100509044319.ga1...@faust.net
Re: Shutdown problem -- cron job related?
On Sun, May 9, 2010 at 01:22, David Baron wrote: > At certain times, seems Friday noontime, I am unable to shutdown the > system. > Instead of the usual scripts to killing all processes, unmounting > everything > and will now halt, goodby, I get: > > process running pstree (or something like that) > shutdown aborted > > At this point, the system (or at least any console or UI) is dead. > > What it this? > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/201005082252.52352.d_ba...@012.net.il > > Just see which process is running pstree. "ps -eaf | grep pstree" You could find the parent pid of pstree (second column). Look at the parent of pstree, and the process started this one. If you go back that way, finally you will reach init, but before that you could find which system process started these processes.
Re: shutdown after kernel upgrade
Dear John, you was right. After investigating I found that the ACPI subsystem isn't measuring CPU temperature. The command 'cat /proc/acpi/thermal_zone/TZ01/temperature' returns zero celsius degrees when the new kernel is loaded, so the fan never runs. This is why the symptom doesn't happen on the old desktop machine, which don't have fan control. By while, I removed the new kernel and I'm using the old kernel, which reads the real temperature and controls the fan correctly, and I will wait for a new kernel update to see if the bug was fixed. Regards, 2010/1/28 John > On 28/01/10, ?? (gp...@ccf.auth.gr) wrote: > | > Same here with both Debian and vanilla versions of all 2.6.32 kernels, > | > home-compiled, running sid on an old IBM Thinkpad A31, with cpufreqd > | > and cpufrequtils. On my machine, the shutdown is caused by runaway > | > overheating after only a few minutes, so there's not much time for > | > diagnosing. 2.6.31.6 with same basic .config runs fine. > | > > | > > | > | how did you understand it was due to heating?? > > cat /proc/acpi/ibm/fan && cat /proc/acpi/ibm/thermal > > -- > johnrchamp...@columbus.rr.com > > GPG key 1024D/99421A63 2005-01-05 > EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63 > gpg --keyserver subkeys.pgp.net --recv-keys 99421A63 > > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.4.10 (GNU/Linux) > > iEYEARECAAYFAkth19UACgkQeBOf6ZlCGmNAaACdGAlVdb7s4U/QOXIfSpl2vKjo > YPgAoJKAAaHiFVOecxywPmEqn1r735Vt > =ZAeK > -END PGP SIGNATURE- > > -- Marcio H. Parreiras GNU/Linux Professional Tel.: (31)9632-0320 Pedro Leopoldo - MG - Brasil *** As melhores soluções em Informática *** - Monitoramento e filtragem de Internet - - Servidores e Estações de Trabalho - - Controladores de Rede - - Sistemas Virtuais - "A caixa dizia: Requer MS Windows ou superior, então eu instalei Debian/GNU Linux!" http://www.debian.org/index.pt.html "The box said: Requires MS Windows or better, then I installed Debian/GNU Linux!" http://www.debian.org/index.en.html Codificação de caracteres / Character encoding: Unicode (UTF-8) .
Re: shutdown after kernel upgrade
On 28/01/10, ?? (gp...@ccf.auth.gr) wrote: | > Same here with both Debian and vanilla versions of all 2.6.32 kernels, | > home-compiled, running sid on an old IBM Thinkpad A31, with cpufreqd | > and cpufrequtils. On my machine, the shutdown is caused by runaway | > overheating after only a few minutes, so there's not much time for | > diagnosing. 2.6.31.6 with same basic .config runs fine. | > | > | | how did you understand it was due to heating?? cat /proc/acpi/ibm/fan && cat /proc/acpi/ibm/thermal -- johnrchamp...@columbus.rr.com GPG key 1024D/99421A63 2005-01-05 EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63 gpg --keyserver subkeys.pgp.net --recv-keys 99421A63 signature.asc Description: Digital signature
Re: shutdown after kernel upgrade
John wrote: > On 28/01/10, ?? (gp...@ccf.auth.gr) wrote: > | Márcio H. Parreiras wrote: > | > ... Acer Aspire 5315 laptop ... kernel 2.6.32-trunk-686 ... > | > powering off suddenly, few minutes after boot. If I > | >choose the old kernel the symptom do not happen ... > | same symptom here on a Dell studio laptop (amd64) and on a classical > | pentium pc... > > Same here with both Debian and vanilla versions of all 2.6.32 kernels, > home-compiled, running sid on an old IBM Thinkpad A31, with cpufreqd > and cpufrequtils. On my machine, the shutdown is caused by runaway > overheating after only a few minutes, so there's not much time for > diagnosing. 2.6.31.6 with same basic .config runs fine. > > how did you understand it was due to heating?? smime.p7s Description: S/MIME Cryptographic Signature
Re: shutdown after kernel upgrade
On Thursday 28 January 2010 13:43:59 Márcio H. Parreiras wrote: > Hi, > > I have an Acer Aspire 5315 laptop, Intel GMA965 chipset, with Debian > Testing installed. Today morning I've made an system upgrade. Since then, > when kernel 2.6.32-trunk-686 is loaded, the laptop is powering off > suddenly, few minutes after boot. If I choose the old kernel the symptom > do not happens. Is any bug or there are some config to do? > In time: another machine, a desktop, with the same distro, was upgraded too > and didn't show any problem with the new kernel. > > Best regards, > I had the same symptom long ago on a change of kernel (don't remember which one). I solved the problem doing a bios upgrade.(Acer aspire 5712Z) Thierry -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: shutdown after kernel upgrade
On 28/01/10, ?? (gp...@ccf.auth.gr) wrote: | Márcio H. Parreiras wrote: | > ... Acer Aspire 5315 laptop ... kernel 2.6.32-trunk-686 ... | > powering off suddenly, few minutes after boot. If I | >choose the old kernel the symptom do not happen ... | same symptom here on a Dell studio laptop (amd64) and on a classical | pentium pc... Same here with both Debian and vanilla versions of all 2.6.32 kernels, home-compiled, running sid on an old IBM Thinkpad A31, with cpufreqd and cpufrequtils. On my machine, the shutdown is caused by runaway overheating after only a few minutes, so there's not much time for diagnosing. 2.6.31.6 with same basic .config runs fine. Nothing amiss that I can spot in syslog, dmesg or lsmod. ACPI shows fan running. Powertop shows unceasing and repeated instances of "flush-254" attributed to "bdi_writeback_task." I googled those messages, but couldn't find anything helpful. Clues, anyone? -- johnrchamp...@columbus.rr.com GPG key 1024D/99421A63 2005-01-05 EE51 79E9 F244 D734 A012 1CEC 7813 9FE9 9942 1A63 gpg --keyserver subkeys.pgp.net --recv-keys 99421A63 signature.asc Description: Digital signature
Re: shutdown after kernel upgrade
Márcio H. Parreiras wrote: Hi, I have an Acer Aspire 5315 laptop, Intel GMA965 chipset, with Debian Testing installed. Today morning I've made an system upgrade. Since then, when kernel 2.6.32-trunk-686 is loaded, the laptop is powering off suddenly, few minutes after boot. If I choose the old kernel the symptom do not happens. Is any bug or there are some config to do? In time: another machine, a desktop, with the same distro, was upgraded too and didn't show any problem with the new kernel. same symptom here on a Dell studio laptop (amd64) and on a classical pentium pc, but shutdown does not happen in 2 minutes but needs a couple of hours... No trace left in syslog and kernel log though... smime.p7s Description: S/MIME Cryptographic Signature
Re: shutdown in Xfce
On Tue,05.May.09, 20:42:13, Peter Crawford wrote: > > Andrei wrote, > > exec startxfce4 > > > > in .xinitrc and run startx. > > No improvement. The Log Out button quits the X > session. The Shut Down and Reboot buttons > produce a complaint and then quit the X session. > > Does the reboot/shutdown gadget work properly > for everyone else using Xfce in Squeeze? No, I'm having troubles as well, see #525909 and #526009. Can you please follow-up on #525909. Please also include output of dpkg -l xfce4* dpkg -l consolekit dpkg -l policykit from within an X session: ck-list-sessions polkit-auth and your .xinitrc and .xsession Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: shutdown in Xfce
No improvement. The Log Out button quits the X session. The Shut Down and Reboot buttons produce a complaint and then quit the X session. Does the reboot/shutdown gadget work properly for everyone else using Xfce in Squeeze? I'm using Sid, and it is working just fine. The behavior you're getting happens to me if I am logged in more than once -- say, in X and on a virtual terminal. After investigating this new behavior, I discovered that it is a new feature instead of a bug, and has to do with the new dependency on PolicyKit. I read the docs (and Googled) until I learned how to configure my system to allow shutdowns from my ordinary user's account even if others were logged in. Then I removed all of my changes to allow that... because I thought about it and realized the default PolicyKit behavior actually would prevent me from forgetting to finish things that I had started (bug had forgotten to finish). If I were you, I would make sure all of the dependencies for 'xserver-xorg' are installed correctly. XOrg now depends on 'hal', which brings in stuff like 'policykit' and 'consolekit', and the problem you're describing sounds like it has to do with those things. HTH eventually, DW -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
RE: shutdown in Xfce
Andrei wrote, > exec startxfce4 > > in .xinitrc and run startx. No improvement. The Log Out button quits the X session. The Shut Down and Reboot buttons produce a complaint and then quit the X session. Does the reboot/shutdown gadget work properly for everyone else using Xfce in Squeeze? Thanks, ... p. c. _ Internet explorer 8 lets you browse the web faster. http://go.microsoft.com/?linkid=9655582 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: shutdown in Xfce
On Sat,02.May.09, 10:57:22, Peter Crawford wrote: > > Andrei P. wrote, > > Do you have hal, consolekit and policykit installed? > > All of them. > > > How do you start X? > > startxfce4 for a few years now. Ok, the new way is to put exec startxfce4 in .xinitrc and run startx. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
RE: shutdown in Xfce
Andrei P. wrote, > Do you have hal, consolekit and policykit installed? All of them. > How do you start X? startxfce4 for a few years now. > ... at least 10 days ... to migrate to testingIf there is no simple answer I > can shelve it for a week or two. Thanks, ... p. c. _ One at a time or all at once? Get updates from your friends in one place. http://go.microsoft.com/?linkid=9660827 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Re: shutdown in Xfce
On Sat,02.May.09, 08:53:24, Peter Crawford wrote: > > At Wed, 28 Jan 2009 23:05:41 -0500 Dave Witbrodt wrote, > 'I decided that > adding myself to the "powerdev" group > made more sense ... than > needing ... root permissions > just to power off.' That's not needed anymore (AFAIK). > Worked until the big update of Xfce this past week. > Now there is a complaint mentioning > "org.freedesktop.hal.power-management.reboot no". > > dw> "Have you read '/usr/share/doc/xfce4-session/README.Debian'?" > > My last update in squeeze was yesterday, 2009-05-01. > The README is dated 2009-04-19 with no mention of a > pending change in shutdown behavior. Well, packages are uploade to unstable first. It takes at least 10 days for them to migrate to testing ;) Do you have hal, consolekit and policykit installed? How do you start X? Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: shutdown firewall
On Mon,27.Apr.09, 17:58:56, Erik Xavior wrote: > Hi > How to shut down a firewall "officaly"? shutdown -h now ;) That was a joke! As the firewall is integral part of the linux kernel you probably don't want to shut it down, but clear all rules. See the manual page of iptables, the tool used for controlling the kernel firewall (netfilter). Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: shutdown -r hangs
On Wed November 26 2008, François Cerbelle wrote: > > why won't it reboot, or what can I look at? > > Do you have the acpi module loaded in kernel ? > > I have similar problems (for halt) and solved it with the acpi module. It > might be the apm module too. oops, I didn't get to finish my last email.. http://www.linuxquestions.org/questions/linux-software-2/linux-acpi-and-bios-acpi-problem-to-understand-and-giving-out-bugs-469366/ I had a similar problem with my Shuttle ak31 v2 motherboard . First off, this motherboard must not handle ACPI correctly. Ever since FC2 I've had to use "acpi=off" in the grub.conf which disables ACPI in Linux, but everything worked fine (it uses APM instead) in FC2, FC3, FC4 and FC5. Once I upgraded to FC6, however, Fedora would no longer turn off the power on my PC when I shut it down. It would just stop, with the last message on the screen being "System halted.". After much googling I found this page, http://mandrivausers.org/index.php?showtopic=38210 which recommended adding "acpi=off apm=on apm=power-off" to the grub.conf. Since my acpi was already off, and I new my APM was already on I simply had to add "apm=power-off" to my grub.conf and now Linux will shut the power off on my PC after it shuts down! My relevant grub.conf entry now looks like this: title Fedora Core (2.6.19-1.2895.fc6) root (hd0,1) kernel /boot/vmlinuz-2.6.19-1.2895.fc6 ro root=/dev/hda2 selinux=0 vga=791 acpi=off apm=power-off elevator=anticipatory initrd /boot/initrd-2.6.19-1.2895.fc6.img savedefault Hope this info helps. - I'll try this and reboot.. I tried it with both off and both on, no change no reboot -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: shutdown -r hangs
On Wed November 26 2008, François Cerbelle wrote: > Do you have the acpi module loaded in kernel ? > > I have similar problems (for halt) and solved it with the acpi module. It > might be the apm module too. I found this: http://www.linuxquestions.org/questions/linux-software-2/linux-acpi-and-bios-acpi-problem-to-understand-and-giving-out-bugs-469366/ -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: shutdown -r hangs
On Wed November 26 2008, François Cerbelle wrote: > > why won't it reboot, or what can I look at? > > Do you have the acpi module loaded in kernel ? I think so, see daemon.log entries: Nov 23 11:00:33 paulandcilla acpid: client connected from 4576[0:0] Nov 23 11:00:34 paulandcilla acpid: client connected from 4576[0:0] Nov 23 11:20:25 paulandcilla acpid: client connected from 4162[0:0] Nov 23 11:20:25 paulandcilla acpid: client connected from 4162[0:0] Nov 23 11:26:14 paulandcilla smartd[3968]: Device: /dev/sda, SMART Usage Attribute: 190 Airflow_Temperature_Cel changed from 65 to 64 Nov 23 11:26:14 paulandcilla smartd[3968]: Device: /dev/sda, SMART Usage Attribute: 194 Temperature_Celsius changed from 115 to 114 Nov 23 13:00:45 paulandcilla ntpd[3456]: adjusting local clock by 0.129000s > > I have similar problems (for halt) and solved it with the acpi module. It > might be the apm module too. > apm ?? > If acpi is not loaded, try : > modprobe acpi did that, it just returned my prompt > then > shutdown -r now > no joy, same results. > If it works, add acpi in /etc/modules or install the acpi package hmm, the only line in /etc/modules that isn't commented out is a single line: loop -- Paul Cartwright Registered Linux user # 367800 Registered Ubuntu User #12459 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: shutdown -r hangs
Le Mer 26 novembre 2008 15:39, Paul Cartwright a écrit : > why won't it reboot, or what can I look at? Do you have the acpi module loaded in kernel ? I have similar problems (for halt) and solved it with the acpi module. It might be the apm module too. If acpi is not loaded, try : modprobe acpi then shutdown -r now If it works, add acpi in /etc/modules or install the acpi package Fanfan -- http://www.cerbelle.net - http://www.afdm-idf.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Shutdown hooks
On Mon, Oct 27, 2008 at 07:51:36AM -0500, green wrote: > On Sun, 2008.10.12, 286, Kumar Appaiah wrote: > > /etc/rc0.d and /etc/rc6.d should be where you should place hooks for > > running programs as you shut down or restart the machine > > respectively. The convention is to put the scripts in /etc/init.d and > > then create symlinks in /etc/rc.d, best handled with update-rc.d. > > The last statement directly contradicts the third paragraph of > update-rc.d(8), > which encourages administrators to edit the links dirctly (or use runlevel > editors like sysv-rc-conf); perhaps that should be changed...? No, I believe you are right with regard to using update.rc.d. Creating a symlink manually would do no harm, and, as you point out from the manual, may be the better way. Apologies for not having seen that earlier, and thanks for letting me know. Kumar -- Kumar Appaiah -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Shutdown hooks
On Sun, 2008.10.12, 286, Kumar Appaiah wrote: > /etc/rc0.d and /etc/rc6.d should be where you should place hooks for > running programs as you shut down or restart the machine > respectively. The convention is to put the scripts in /etc/init.d and > then create symlinks in /etc/rc.d, best handled with update-rc.d. The last statement directly contradicts the third paragraph of update-rc.d(8), which encourages administrators to edit the links dirctly (or use runlevel editors like sysv-rc-conf); perhaps that should be changed...? signature.asc Description: Digital signature
Re: shutdown failure
On Wed, Oct 15, 2008 at 08:05:18PM -0400, [EMAIL PROTECTED] wrote: > shutdown stopped working, in the sense that the shutdown command > produced the log entry > > Oct 13 20:01:02 aptiva shutdown[26745]: shutting down for system > reboot > > and wrote /fsckcheck > I finally pulled the plug. After reboot, shutdown works again. > > When this happens again, what should I look for in an attempt to > figure out what's going on? I don't know the ultimate cause, but I have a suggestion on what to do if it happens again (other than just pulling the plug). Manually run each script in /etc/rc0.d with the parameter "stop". This is what the shutdown command should be doing and you may see an error indication that gives a clue. If not, at least you may avoid mangling your filesystem (or some data on it). Doug. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Shutdown hooks
Tzafrir Cohen wrote: On Sun, Oct 12, 2008 at 09:56:00PM +0530, Bhasker C V wrote: Hi, I was trying to find out if there are any shutdown hooks. What i mean by this is that i must be able to have some conditions met before actual shutdown starts. Eg:- Suppose there is a very important process running, the hook must check this and if the hook returns non-zero, the system must refuse a requested shutdown. I can write a wrapper to /sbin/shutdown for doing this, but i am just trying to find out if there is any method already available for doing this ? aptitude install molly-guard From the man page: molly-guard attempts to prevent you from accidentally shutting down or rebooting machines. It does this by injecting a couple of checks before the existing commands: halt, reboot, shutdown, and poweroff. This happens via scripts with the same names in /usr/sbin, so it only works if you have /usr/sbin before /sbin in your PATH! Before molly-guard invokes the real command, all scripts in /etc/molly-guard/run.d/ have to run and exit successfully; else, it aborts the command. run-parts(1) is used to process the directory. It is intended to prevent you from easily rebooting a remote server (thinking it were your own). But I figure it can be easily adapted. I learn something new every day. Hugo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Shutdown hooks
On Sun, Oct 12, 2008 at 09:56:00PM +0530, Bhasker C V wrote: > Hi, > > I was trying to find out if there are any shutdown hooks. > What i mean by this is that i must be able to have some conditions met > before actual shutdown starts. > > Eg:- Suppose there is a very important process running, the hook must > check this and if the hook returns non-zero, the system must > refuse a requested shutdown. > > I can write a wrapper to /sbin/shutdown for doing this, but i am just > trying to find out if there is any method already available for doing > this ? aptitude install molly-guard >From the man page: molly-guard attempts to prevent you from accidentally shutting down or rebooting machines. It does this by injecting a couple of checks before the existing commands: halt, reboot, shutdown, and poweroff. This happens via scripts with the same names in /usr/sbin, so it only works if you have /usr/sbin before /sbin in your PATH! Before molly-guard invokes the real command, all scripts in /etc/molly-guard/run.d/ have to run and exit successfully; else, it aborts the command. run-parts(1) is used to process the directory. It is intended to prevent you from easily rebooting a remote server (thinking it were your own). But I figure it can be easily adapted. -- Tzafrir Cohen | [EMAIL PROTECTED] | VIM is http://tzafrir.org.il || a Mutt's [EMAIL PROTECTED] || best ICQ# 16849754 || friend -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Shutdown hooks
On Sun, Oct 12, 2008 at 12:21:50PM -0500, Ron Johnson wrote: >> /etc/rc0.d and /etc/rc6.d should be where you should place hooks for >> running programs as you shut down or restart the machine >> respectively. The convention is to put the scripts in /etc/init.d and >> then create symlinks in /etc/rc.d, best handled with update-rc.d. > > But it's too late then. The shutdown can't be stopped, I think. > > I'd wrap /sbin/shutdown. Oh, you're right. I thought that he wanted to shut down the service as the shutdown occurred. I guess wrapping the command you use for shutting down is the simplest way then. Thanks. Kumar -- Kumar Appaiah signature.asc Description: Digital signature
Re: Shutdown hooks
On 10/12/08 11:56, Kumar Appaiah wrote: On Sun, Oct 12, 2008 at 09:56:00PM +0530, Bhasker C V wrote: I can write a wrapper to /sbin/shutdown for doing this, but i am just trying to find out if there is any method already available for doing this ? /etc/rc0.d and /etc/rc6.d should be where you should place hooks for running programs as you shut down or restart the machine respectively. The convention is to put the scripts in /etc/init.d and then create symlinks in /etc/rc.d, best handled with update-rc.d. But it's too late then. The shutdown can't be stopped, I think. I'd wrap /sbin/shutdown. -- Ron Johnson, Jr. Jefferson LA USA Help a man when he is in trouble and he will remember you when he is in trouble again. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Shutdown hooks
On Sun, Oct 12, 2008 at 09:56:00PM +0530, Bhasker C V wrote: > I can write a wrapper to /sbin/shutdown for doing this, but i am just > trying to find out if there is any method already available for doing > this ? /etc/rc0.d and /etc/rc6.d should be where you should place hooks for running programs as you shut down or restart the machine respectively. The convention is to put the scripts in /etc/init.d and then create symlinks in /etc/rc.d, best handled with update-rc.d. HTH. Kumar -- Kumar Appaiah signature.asc Description: Digital signature
Re: shutdown and reboot scripts
Daniel Dalton wrote: Hi, Can someone tell me what script I can edit so when my box shuts down or reboots all my mounted devices get pumounted? (I use pmount to mount everything) So, how can I pumount all devices on /media? So basically I have 2 questions: 1. What script can I place commands in that runs at shutdown/reboot... 2. How do I pumount all devices in /media? AFAIK you should not have to do anything. Everything (except /) is unmounted by default during shutdown. / is re-mounted ro. The default init scripts takes care of killing all processes before unmounting devices. -- If you can't explain it simply, you don't understand it well enough. -- Albert Einstein -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: shutdown and reboot scripts
On Wed, Jul 02, 2008 at 09:45:52AM +1000, Daniel Dalton wrote: > Hi, > > Can someone tell me what script I can edit so when my box shuts down or > reboots all my mounted devices get pumounted? > (I use pmount to mount everything) > So, how can I pumount all devices on /media? > > So basically I have 2 questions: > 1. What script can I place commands in that runs at shutdown/reboot... > 2. How do I pumount all devices in /media? Even though I use pmount as well I have entries for my external drive in fstab: LABEL=mirror/media/mirror ext3defaults,noatime,user,data=journal 0 LABEL=Elements /media/xbig vfatuid=amp,noatime,user,fmask=133 0 This way the standard scripts will take care of unmounting the device. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: shutdown and reboot scripts
On Tue, Jul 01, 2008 at 07:27:09PM -0500, Mumia W.. wrote: >> So basically I have 2 questions: >> 1. What script can I place commands in that runs at shutdown/reboot... >> 2. How do I pumount all devices in /media? >> > > Read "man update-rc.d" and this document: > > http://www.debian.org/doc/manuals/reference/ch-system.en.html#s-boot I'll have a look at those as soon as I get a chance. Thanks, -- Daniel Dalton http://members.iinet.net.au/~ddalton/ <[EMAIL PROTECTED]> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
