[opensuse] systemd shutdown warning?
I recently upgraded to 12.1, including systemd. I have a machine configured that powers off automatically at certain types, using crontab. In the past, I could put in the crontab "shutdown -h +30", and then I would get warning messages on the console as the shutdown approaches. With systemd, shutdown gets scheduled, but no warnings appear anywhere. The system just shuts down when the time comes. Is there a way to reproduce this warning message behavior? The man page just says "shutdown is for compatibility only", and systemctl page does not offer any options about scheduling or warnings. Myrosia -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Mar 01, 2012 at 12:16:46AM +0000, Myrosia Dzikovska wrote:
I recently upgraded to 12.1, including systemd. I have a machine configured that powers off automatically at certain types, using crontab. In the past, I could put in the crontab "shutdown -h +30", and then I would get warning messages on the console as the shutdown approaches. With systemd, shutdown gets scheduled, but no warnings appear anywhere. The system just shuts down when the time comes.
Is there a way to reproduce this warning message behavior? The man page just says "shutdown is for compatibility only", and systemctl page does not offer any options about scheduling or warnings.
Either switch back to sysvinit. But be aware there is a sysvinit bug open which causes only some systems to need some extra time at the end of the shutdown process. Cf. https://bugzilla.novell.com/show_bug.cgi?id=730193 See also http://en.openSUSE.org/openSUSE:Most_annoying_bugs_12.1 section Bug #725917 Problem: System is switched from sysvinit to systemd during upgrade. Workaround: is to install the sysvinit-init package. As soon as its install gets acknowledged the removal of the systemd-sysvinit package will be suggested. Or consider to check the same with the recently released systemd packages to the 12.1 update channel. I got version 37 release 3.8.1 yesterday. If you have to file a bugreport be this nice to report the bug ID back to this thread to establish a cross reference. In the bug you might also add a pointer to the listarchive at http://lists.opensuse.org/opensuse/2012-03/msg00001.html And my congratulation for having filed message #1 in March 2012. :) Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Either switch back to sysvinit. But be aware there is a sysvinit bug open which causes only some systems to need some extra time at the end of the shutdown process.
Or consider to check the same with the recently released systemd packages to the 12.1 update channel. I got version 37 release 3.8.1 yesterday.
With the systemd update I got an improvement, but not a complete fix. It is now giving 15-minute warning; but it is not giving 5- and 1-minute warnings as the previous shutdown used to do. I found it really annoying to have my machine shut down in the middle of a document I had been trying to finish in a hurry just because I misjudged my 15-minute window.
If you have to file a bugreport be this nice to report the bug ID back to this thread to establish a cross reference. In the bug you might also add a pointer to the listarchive at http://lists.opensuse.org/opensuse/2012-03/msg00001.html
I am happy to file bugs (and post a link here as you suggested), what I am trying to figure out if this is upstream bug in systemd, in which case I should take it there, or it is a suse bug. Or does it matter? I could of course always file it on Novell bugzilla and let the developers decide. Myrosia -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Mon, Mar 05, 2012 at 12:56:52AM +0000, Myrosia Dzikovska wrote: [ 8< ]
I am happy to file bugs (and post a link here as you suggested), what I am trying to figure out if this is upstream bug in systemd, in which case I should take it there, or it is a suse bug. Or does it matter? I could of course always file it on Novell bugzilla and let the developers decide.
Please file it against https://bugzilla.novell.com/ Classification (Product Line): openSUSE Product: 12.1 Assign it straightly to Frederic <fcrozat at suse dot com>. He'll be able to decide if this is an openSUSE issue or if it has to be handled upstream as well. Or if it got fixed already and the code isn't yet published. You and we all will see. Please provide as much as possible information with the bug report including a reference to this thread as a link from the list archive at http://lists.openSUSE.org/opensuse/2012-03/msg00001.html Reply back to this thread with the resulting bug ID to allow others to follow the issue further. Thanks, Lars -- Lars Müller [ˈlaː(r)z ˈmʏlɐ] Samba Team SUSE Linux, Maxfeldstraße 5, 90409 Nürnberg, Germany
Thanks for your help with this. I bug 758045 in the novell bugzilla https://bugzilla.novell.com/show_bug.cgi?id=750845 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (2)
-
Lars Müller
-
Myrosia Dzikovska