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 w
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_
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
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
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 Jes
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.
I
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.
>
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 quirk
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 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 debia
-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 su
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.
> >
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
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. B
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
> o
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
> o
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
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 qu
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 subje
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 r
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 f
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
>
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-onl
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
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
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 di
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.
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 so
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
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
^^^
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' :) !! Ba
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
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
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
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!!! :)
a
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
/_
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
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:
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 instal
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
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
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,
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
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 t
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 inst
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 shu
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
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. Bett
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 s
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
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
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
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
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 execu
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
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 th
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
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 on
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
>
> http
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)
"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
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 co
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
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
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.
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 choos
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,
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, s
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 somet
>> 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, th
> 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
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
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
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
| > overheat
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 ...
> |
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
> sudd
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
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 o
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/sh
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
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?
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,
Andr
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.
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
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 f
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 ema
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
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 co
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
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
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 w
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. Aft
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 pro
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,
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/r
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 yo
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 prog
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
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 h
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/manu
1 - 100 of 380 matches
Mail list logo
