https://bugzilla.novell.com/show_bug.cgi?id=785701 https://bugzilla.novell.com/show_bug.cgi?id=785701#c1 --- Comment #1 from Frederic Crozat 2012-10-31 10:00:15 UTC --- Thanks, I'll try to integrate your solution -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785701 https://bugzilla.novell.com/show_bug.cgi?id=785701#c3 --- Comment #3 from Stanislav Brabec 2012-11-05 20:15:36 CET --- Well, there is a question: Do we need to support HALT_POWERDOWN_INSERT in systemd? (Not thinking the about the late powerdown command feature, just about the HALT_POWERDOWN_INSERT sysconfig variable.) I introduced HALT_POWERDOWN_INSERT several years ago, because there was no easy way to create init script running in the late halt sequence. (There was only /etc/init.d/halt.local, but its use is a bit complicated for packages. (The file is intended for admin, and it had to be auto-edited by rpm scriptlets.) And it is called before stopping software RAID.) If systemd has a clean way to perform action just before calling the final poweroff, then HALT_POWERDOWN_INSERT is no more needed, and packages can use standard systemd integration. If it is true, we can update HALT_POWERDOWN_INSERT description and say, that it is systemv specific. What it would mean? Do not introduce the service proposed by you in the core systemd package, but add needed service to apcupsd and nut. I think that there were no other packages using this feature. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785701 https://bugzilla.novell.com/show_bug.cgi?id=785701#c5 --- Comment #5 from Andrey Borzenkov 2012-11-06 16:58:51 UTC --- I think I was mistaken. When this issue was raised on forums I did not get clear picture where packages originated. But now I see that both apcupsd and nut are in standard openSUSE 12.2 repositories. That makes it really problem of packages integration which has to be fixed in respective packages, not in systemd. I will rebuild apcupsd with proper system-shutdown script and ask user to test it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785701 https://bugzilla.novell.com/show_bug.cgi?id=785701#c7 Ian Powell changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |ianseeks@dsl.pipex.com --- Comment #7 from Ian Powell 2012-12-13 18:14:00 UTC --- I'm not sure if this bug is related to my issue. I've got the problem of the PC never powering down even though I get the "System Halted" message ok (i escaped the shutdown splash to watch the shutdown). I expect the PC then to power off. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785701 https://bugzilla.novell.com/show_bug.cgi?id=785701#c9 --- Comment #9 from Ian Powell 2013-01-20 16:26:38 UTC --- (In reply to comment #8)

(In reply to comment #7)

...

I'm not sure if this bug is related to my issue. I've got the problem of the PC never powering down even though I get the "System Halted" message ok (i escaped the shutdown splash to watch the shutdown). I expect the PC then to power off.

This is unrelated, you need to use "halt -p" to shutdown your computer (as explained in the manual). With sysvinit, we had a patch which was injecting "-p" on x86/x86_64 hardware without you noticing.

Unfortunately that made no difference at all. There is "Bug 794889 - Shutdown does not power off machine" created by someone else which is more relevant but no-one has looked at it. I had also posted to that one. I installed Fedora on an old laptop to check another issue and noticed it used "poweroff". So i tried it as well but it did the same thing, shut everything down okay but did not power off. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785701 https://bugzilla.novell.com/show_bug.cgi?id=785701#c11 --- Comment #11 from Ian Powell 2013-01-21 11:34:56 UTC --- (In reply to comment #10)

if halt -p doesn't work, it is a kernel issue.

Unfortunatly it doesn't work either, nothing seems to power off the machine. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785701 https://bugzilla.novell.com/show_bug.cgi?id=785701#c13 --- Comment #13 from Ian Powell 2013-01-21 18:11:36 UTC --- (In reply to comment #12)

so, it is not about this bug report.

so it would appear. just hope someone gets time to look at logged fault to check to see if it affects 12.3 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.

https://bugzilla.novell.com/show_bug.cgi?id=785701 https://bugzilla.novell.com/show_bug.cgi?id=785701#c15 Borislav Petkov changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |bpetkov@suse.com --- Comment #15 from Borislav Petkov 2013-07-25 16:34:06 UTC --- So which systemd version has the fixes and how can I point people to it to try it out? I have a bug of two machines with similar symptoms (bnc#813244). Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.