[systemd-devel] shutdown journald-messages and the lack of such

> What "specs", "systemd specs"? > > Good question! I vaguely remember somebody boasting on youtube along the line of "since GNU/Linux nears world domination in terms of installations (where a million $ IBM mainframe counts as much as a $3 rental VM), UNIX specs are not necessarily relevant for

[systemd-devel] shutdown now --no-wall # messages & the lack thereof

> It appears that the systemctl implementation has changed the behaviour, > and the documentation. Whether there is a spec anywhere (POSIX or > whatever) I do not know - but certainly a man page is not a spec. systemd might still be UNIX compliant here, as

Re: [systemd-devel] Shutdown order in systemd

Hi, Thanks for the updates about systemd-inhibit! It will be a great enhancement. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] Shutdown order in systemd

Just FYI and for the sake of cross referencing, the inhibition logic was mentioned on the list today in a thread: "systemd-inhibit don't work". A developer says he will work on the patch for this RFE shortly. Col Zheng SHAO wrote on 04/08/2020 13:39: > Hello, > > First thanks for your advise. >

Re: [systemd-devel] Shutdown order in systemd

Zheng SHAO wrote on 03/08/2020 13:31: > Hello, > > We are finding a robust way to handle ACPI G2 soft off signal to graceful > shutdown our application. > To simplifier the problem, consider our instance is running with Nginx behind > a load balancer. > When the ACPI G2 soft off signal comes to

[systemd-devel] Shutdown order in systemd

Hello, We are finding a robust way to handle ACPI G2 soft off signal to graceful shutdown our application. To simplifier the problem, consider our instance is running with Nginx behind a load balancer. When the ACPI G2 soft off signal comes to the Nginx instance, we want to do these jobs 1.

Re: [systemd-devel] Shutdown behavior follow up

> Thanks in advance, > -Jay > > -Original Message- > From: Lennart Poettering > Sent: Monday, January 13, 2020 4:33 AM > To: Burger, Jay > Cc: systemd-devel@lists.freedesktop.org; Dang, James > ; Berger, Daniel ; > Mahabaleshwar, Niranjan > Subj

[systemd-devel] Shutdown behavior follow up

, Daniel ; Mahabaleshwar, Niranjan Subject: Re: [systemd-devel] Shutdown behavior On Fr, 10.01.20 10:56, Jay Burger (jay.bur...@us.fujitsu.com) wrote: > I made the same type of change in the emergency_action() function in v232. > > Question 1: Would this be considered a problem with t

Re: [systemd-devel] Shutdown Behavior

Jay Burger schrieb am 13.01.2020 um 17:36 in Nachricht <9f4dc083-18f7-ba68-cc96-1d3c9492e...@us.fujitsu.com>: ... Personally, I would think the initial shutdown should always be honored. Unrealistic dramatized example: I have another emergency at Chernobyl and need to power down my reactor.

Re: [systemd-devel] Shutdown behavior

--- Message: 1 Date: Mon, 13 Jan 2020 12:18:00 + From: Dave Howorth To: systemd-devel@lists.freedesktop.org Subject: Re: [systemd-devel] Shutdown behavior Message-ID: <20200113121800.338bc...@acer-suse.lan> Content-Type: text/plain; charset=US-ASCII On Mon, 13 Jan 2020 11:32:37 +0100

Re: [systemd-devel] Shutdown behavior

On Mon, 13 Jan 2020 11:32:37 +0100 Lennart Poettering wrote: > On Fr, 10.01.20 10:56, Jay Burger (jay.bur...@us.fujitsu.com) wrote: > > > I made the same type of change in the emergency_action() function > > in v232. > > > > Question 1: Would this be considered a problem with the design, > >

Re: [systemd-devel] Shutdown behavior

On Fr, 10.01.20 10:56, Jay Burger (jay.bur...@us.fujitsu.com) wrote: > I made the same type of change in the emergency_action() function in v232. > > Question 1: Would this be considered a problem with the design, needing an > upstream fix? Or would this be considered a particular user issue, to

[systemd-devel] Shutdown behavior

Hi, I have a couple of questions regarding systemd shutdown behavior. I first noticed this behavior using systemd v213, I am now on v232 and see the same problem. I found a fix in 213 and patched the service.c module, in 232 the change needed to move to the emergency-action.c module. The

Re: [systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes

27.08.2019 14:34, Lennart Poettering пишет: > be able to get away with adding a drop-in to > /etc/systemd/system/session-.scope.d/50-order.conf or so which just Thanks for the reminder, I completely forgot about this feature. ___ systemd-devel mailing

Re: [systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes

On So, 25.08.19 18:57, Hans-Dieter Doll (hans-dieter.d...@drb.insel.de) wrote: > On shutdown we need to stop a service before systemd begins to kill > all processes it does not know. All processes on the system are indirectly "known" by systemd. All processes (except kernel threads) belong to a

Re: [systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes

Can you please resolve it from your end actually I don't no exactly where the loop hole. Thanks and Regards Ram On Mon, 26 Aug 2019, 19:54 Hans-Dieter Doll, wrote: > > typically that issue is a sign of bad design and just worked by luck > > with a simple init system lacking of concepts for

Re: [systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes

> typically that issue is a sign of bad design and just worked by luck > with a simple init system lacking of concepts for service states well, the design is from last century :-) > you should split your stuff into multiple systemd units and pack them > into a target instead wrap a dozen of more

Re: [systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Am 26.08.19 um 00:19 schrieb Hans-Dieter Doll: > There are also interactive applications started as user sessions. > Some of these must not be killed but terminated by the supervisor, > otherwise we (i.e. our customers) run into trouble. > >

Re: [systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes

Am 25.08.19 um 22:02 schrieb Andrei Borzenkov: > 25.08.2019 19:57, Hans-Dieter Doll пишет: >> On shutdown we need to stop a service before systemd begins to kill all >> processes it does not know. >> The service is a process supervisor similar to init, which controls all our >> applications. >>

Re: [systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes

25.08.2019 19:57, Hans-Dieter Doll пишет: > On shutdown we need to stop a service before systemd begins to kill all > processes it does not know. > The service is a process supervisor similar to init, which controls all our > applications. > Our applications must be terminated by this

[systemd-devel] shutdown: how to tell systemd to stop a service before killing other processes

On shutdown we need to stop a service before systemd begins to kill all processes it does not know. The service is a process supervisor similar to init, which controls all our applications. Our applications must be terminated by this supervisor, otherwise data loss and inconsistencies will

Re: [systemd-devel] shutdown on service unit timeout?

On Mo, 19.08.19 08:54, Chris Murphy (li...@colorremedies.com) wrote: > Hi, > > Is it possible for a systemd service file to ask for a poweroff upon > service timeout? If not, could it be done; or suggest an alternative? > > Here's the use case: > > No Screensaver/Powerdown after Inactivity at

[systemd-devel] shutdown on service unit timeout?

Hi, Is it possible for a systemd service file to ask for a poweroff upon service timeout? If not, could it be done; or suggest an alternative? Here's the use case: No Screensaver/Powerdown after Inactivity at LUKS Password Prompt https://bugzilla.redhat.com/show_bug.cgi?id=1742953 The summary

Re: [systemd-devel] Shutdown/reboot problem: root hd powered off too early?

On Wed, 23.11.16 11:01, Johannes Maibaum (jmaib...@gmail.com) wrote: > ata2: exception Emask 0x10 SAct 0x0 SErr 0x199 action 0xe > frozenbd204ed5c > ata2: irq_stat 0x0040, PHY RDY changed > ata2: SError: { PHYRdyChg 10B8B Dispar LinkSeq TrStaTrns } This looks like a kernel problem.

[systemd-devel] Shutdown/reboot problem: root hd powered off too early?

Hi, I have a question concerning the shutdown/reboot phase that might be a problem with the kernel, but I was told in the Arch Linux forums to ask here too, as I have also problems with correctly logging the relevant information. I try to be as specific as I can, but I have to apologize in

Re: [systemd-devel] shutdown delayed by failure to start a service

Lennart Poettering composed on 2016-05-30 17:37 (UTC+0200): > Felix Miata wrote: >> Lennart Poettering composed on 2016-05-29 18:40 (UTC+0200): >> >Felix Miata wrote: >> >>The message I see is equivalent in form as during boot, e.g. when a >> >>filesystem not noauto in fstab is to be mounted

Re: [systemd-devel] shutdown delayed by failure to start a service

Lennart Poettering composed on 2016-05-30 17:37 (UTC+0200): > Felix Miata wrote: >> Lennart Poettering composed on 2016-05-29 18:40 (UTC+0200): >> >Felix Miata wrote: >> >>The message I see is equivalent in form as during boot, e.g. when a >> >>filesystem not noauto in fstab is to be mounted

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

Hi Michael, Thanks for your comments, looks like it will work. I will try it. Just adding a question, if my specific is written in old style (SystemVinit), it has LSB header, how can I modify it to make it depend on multi-user.target. Thanks, Brs On Wed, May 25, 2016 at 5:09 PM, Michael

Re: [systemd-devel] shutdown delayed by failure to start a service

On Sun, 29.05.16 13:28, Felix Miata (mrma...@earthlink.net) wrote: > Lennart Poettering composed on 2016-05-29 18:40 (UTC+0200): > > >Felix Miata wrote: > > >>The message I see is equivalent in form as during boot, e.g. when a > >>filesystem not noauto in fstab is to be mounted but cannot be

Re: [systemd-devel] shutdown delayed by failure to start a service

29.05.2016 20:28, Felix Miata пишет: > Lennart Poettering composed on 2016-05-29 18:40 (UTC+0200): > >> Felix Miata wrote: > >>> The message I see is equivalent in form as during boot, e.g. when a >>> filesystem not noauto in fstab is to be mounted but cannot be found, >>> so a >>> delay of

Re: [systemd-devel] shutdown delayed by failure to start a service

Lennart Poettering composed on 2016-05-29 18:40 (UTC+0200): Felix Miata wrote: The message I see is equivalent in form as during boot, e.g. when a filesystem not noauto in fstab is to be mounted but cannot be found, so a delay of typically 90sec, but sometimes much longer, occurs. Mount

Re: [systemd-devel] shutdown delayed by failure to start a service

On Sat, 28.05.16 04:42, Felix Miata (mrma...@earthlink.net) wrote: > Mantas Mikulėnas composed on 2016-05-27 20:05 (UTC+0300): > > >Lennart Poettering wrote: > > >>Felix Miata wrote: > > >>>Did this ever get fixed? IOW, sometimes a service will fail to start when a > >>>system is started, or

Re: [systemd-devel] shutdown delayed by failure to start a service

Mantas Mikulėnas composed on 2016-05-27 20:05 (UTC+0300): Lennart Poettering wrote: Felix Miata wrote: Did this ever get fixed? IOW, sometimes a service will fail to start when a system is started, or later, after a session of updating, a previously operating service fails to restart, or

Re: [systemd-devel] shutdown delayed by failure to start a service

On Fri, May 27, 2016 at 7:47 PM, Lennart Poettering wrote: > On Thu, 26.05.16 11:29, Felix Miata (mrma...@earthlink.net) wrote: > > > Did this ever get fixed? IOW, sometimes a service will fail to start > when a > > system is started, or later, after a session of

Re: [systemd-devel] shutdown delayed by failure to start a service

On Thu, 26.05.16 11:29, Felix Miata (mrma...@earthlink.net) wrote: > Did this ever get fixed? IOW, sometimes a service will fail to start when a > system is started, or later, after a session of updating, a previously > operating service fails to restart, or a newly installed service fails to >

[systemd-devel] shutdown delayed by failure to start a service

Did this ever get fixed? IOW, sometimes a service will fail to start when a system is started, or later, after a session of updating, a previously operating service fails to restart, or a newly installed service fails to start, or a service is removed. Then at shutdown/reboot time, systemd

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

On Thu, 19 May 2016, Bao Nguyen wrote: Hi everyone, When the system is shutdown, systemd will terminate all services in parallel manner, could you let me know if there is any ways to tell systemd to shutdown a specific service first, then shutdown all remaining services? Hello, I haven't

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

On Wed, May 25, 2016 at 9:59 AM, Bao Nguyen wrote: > Hi, > > Thanks for all your comments. > > How do you think if we create a custom target to include all remaining > services, then add this target to the dependency After= of the specific > services. This way can make the

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

Hi, Thanks for all your comments. How do you think if we create a custom target to include all remaining services, then add this target to the dependency After= of the specific services. This way can make the specific stop before the services in the target when the system shutdowns? Thanks,

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

On Sun, 22.05.16 15:24, Andrei Borzenkov (arvidj...@gmail.com) wrote: > 19.05.2016 11:57, Martin Pitt пишет: > > Hello Bao, > > > > Bao Nguyen [2016-05-19 15:52 +0700]: > >> When the system is shutdown, systemd will terminate all services in > >> parallel manner, could you let me know if there

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

On Sun, May 22, 2016 at 3:24 PM, Andrei Borzenkov wrote: > 19.05.2016 11:57, Martin Pitt пишет: > > Hello Bao, > > > > Bao Nguyen [2016-05-19 15:52 +0700]: > >> When the system is shutdown, systemd will terminate all services in > >> parallel manner, could you let me know if

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

19.05.2016 11:57, Martin Pitt пишет: > Hello Bao, > > Bao Nguyen [2016-05-19 15:52 +0700]: >> When the system is shutdown, systemd will terminate all services in >> parallel manner, could you let me know if there is any ways to tell systemd >> to shutdown a specific service first, then shutdown

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

On Fri, 20.05.16 11:24, Bao Nguyen (bao...@gmail.com) wrote: > Hi Martin, > > Thanks a lot for your answer. > > How about if my specific script is written by SysVinit, it has LSB headers, > can we still use in LSB header the property lAfter= as in systemd to make > it start/stop orderly? Our

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

Hi Martin, Thanks a lot for your answer. How about if my specific script is written by SysVinit, it has LSB headers, can we still use in LSB header the property lAfter= as in systemd to make it start/stop orderly? Another solution I think to make it shutdowns "order" when I read

Re: [systemd-devel] Shutdown a specific service in systemd shutdown

Hello Bao, Bao Nguyen [2016-05-19 15:52 +0700]: > When the system is shutdown, systemd will terminate all services in > parallel manner, could you let me know if there is any ways to tell systemd > to shutdown a specific service first, then shutdown all remaining services? The concept of

[systemd-devel] Shutdown a specific service in systemd shutdown

Hi everyone, When the system is shutdown, systemd will terminate all services in parallel manner, could you let me know if there is any ways to tell systemd to shutdown a specific service first, then shutdown all remaining services? Thanks, Best regards, Natsu

Re: [systemd-devel] Shutdown root fs on loop device

Or use a wrapper. #include #include int main(int argc, char *argv[]) { argv[0] = "@ntfs-3g"; execv("/usr/bin/ntfs-3g", argv); perror("ntfs-3g-wrapper"); return 1; 2016-04-22 13:02 GMT+02:00 Tomasz Torcz : > On Fri, Apr 22, 2016 at

Re: [systemd-devel] Shutdown root fs on loop device

On Fri, Apr 22, 2016 at 11:49:09AM +0200, Michael Lipp wrote: > Hi, > > I have some PCs where I have to store the Linux root file system as a > large file in Window's NTFS file system. Everything boots fine. The NTFS > file system is mounted as ntfs-3g in the initial ramfs as /host, the >

[systemd-devel] Shutdown root fs on loop device

Hi, I have some PCs where I have to store the Linux root file system as a large file in Window's NTFS file system. Everything boots fine. The NTFS file system is mounted as ntfs-3g in the initial ramfs as /host, the loopback device is created (using /host/Linux/image.img) and used as root.

[systemd-devel] shutdown from within a service

Hello, I've run into another side-effect of systemd's supervisory power over processes. The application is a simple ruby webrick daemon. It get's started just fine. It provides web service configuration to an appliance. One of the service calls gives clients the ability to power down

Re: [systemd-devel] shutdown from within a service

On Mon, Feb 23, 2015 at 1:33 PM, JB gene...@itpsg.com wrote: Hello, I've run into another side-effect of systemd's supervisory power over processes. The application is a simple ruby webrick daemon. It get's started just fine. It provides web service configuration to an appliance. One

Re: [systemd-devel] shutdown

On 12/04/2014 04:26 PM, Lennart Poettering wrote: On Fri, 31.10.14 18:50, Tom Deblauwe (deblauwe...@gmail.com) wrote: Hmm, this smells like 4b5d8d0f22ae61ceb45a25391354ba53b43ee992 might fix your issue? Could you verify that this is the issue you are running into? Hello, Thanks for the

Re: [systemd-devel] shutdown

On Fri, 31.10.14 18:50, Tom Deblauwe (deblauwe...@gmail.com) wrote: Hello, Heya, sorry for the late reply. In case this is still open: Which distribution is this? I'm using systemd, but can't seem to correctly shutdown. I have already: What does can't seem to correctly shutdown mean? What

Re: [systemd-devel] Shutdown problems

On Mon, 24.11.14 12:31, Nikolaus Rath (nikol...@rath.org) wrote: Sorry for the late reply, still have a huge backlog of mail which I am trying to process right now. If the latter hangs then it's a kernel bug. reboot -f works fine - could it still be a kernel bug? Please check if there

Re: [systemd-devel] Shutdown problems

Nikolaus Rath nikol...@rath.org writes: On 11/13/2014 12:54 PM, Nikolaus Rath wrote: Nikolaus Rath nikol...@rath.org writes: Lennart Poettering lenn...@poettering.net writes: On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote: Please boot with systemd.log_level=debug, then make

Re: [systemd-devel] Shutdown problems

Nikolaus Rath wrote on 16/11/14 16:54: No one able to help at all? Please be patient. You've only left it a couple days since your last reply and only one of those days was a weekday. People will likely reply soon enough. I would however recommend you disable things like plymouth and remove

Re: [systemd-devel] Shutdown problems

Nikolaus Rath nikol...@rath.org writes: On 11/13/2014 12:54 PM, Nikolaus Rath wrote: Nikolaus Rath nikol...@rath.org writes: Lennart Poettering lenn...@poettering.net writes: On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote: Please boot with systemd.log_level=debug, then make

Re: [systemd-devel] Shutdown problems

Nikolaus Rath nikol...@rath.org writes: Lennart Poettering lenn...@poettering.net writes: On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote: Please boot with systemd.log_level=debug, then make the machine hang and check what the last things in the logs say. Maybe then paste

Re: [systemd-devel] Shutdown problems

On 11/13/2014 12:54 PM, Nikolaus Rath wrote: Nikolaus Rath nikol...@rath.org writes: Lennart Poettering lenn...@poettering.net writes: On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote: Please boot with systemd.log_level=debug, then make the machine hang and check what the last

Re: [systemd-devel] Shutdown problems

On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote: Please boot with systemd.log_level=debug, then make the machine hang and check what the last things in the logs say. Maybe then paste that somewhere online and post the URL for that here, so that we can have a look.

Re: [systemd-devel] Shutdown problems

Lennart Poettering lenn...@poettering.net writes: On Sat, 08.11.14 11:16, Nikolaus Rath (nikol...@rath.org) wrote: Please boot with systemd.log_level=debug, then make the machine hang and check what the last things in the logs say. Maybe then paste that somewhere online and post the URL

Re: [systemd-devel] Shutdown problems

Lennart Poettering lenn...@poettering.net writes: On Thu, 06.11.14 19:07, Nikolaus Rath (nikol...@rath.org) wrote: Hello, I'm having some trouble shutting down my system with systemd. What happens is the following: * If I execute systemctl reboot while a text console is active,

Re: [systemd-devel] Shutdown problems

Am 2014-11-07 04:07, schrieb Nikolaus Rath: $ cat /lib/systemd/system-shutdown/debug.sh #!/bin/sh exec /shutdown.log exec 21 mount -o remount,rw / Well, you need to mount / rewrite *before* redirecting output into a file. Try putting the 'mount -o remount,rw /' line to the top of the script

Re: [systemd-devel] Shutdown problems

On Thu, 06.11.14 19:07, Nikolaus Rath (nikol...@rath.org) wrote: Hello, I'm having some trouble shutting down my system with systemd. What happens is the following: * If I execute systemctl reboot while a text console is active, everything works fine. * If I execute systemctl

[systemd-devel] Shutdown problems

Hello, I'm having some trouble shutting down my system with systemd. What happens is the following: * If I execute systemctl reboot while a text console is active, everything works fine. * If I execute systemctl reboot while the X11 console is active, the system hangs (I tried waiting

[systemd-devel] shutdown

Hello, I'm using systemd, but can't seem to correctly shutdown. I have already: - checked: reboot -f works - enabled the debug-shell on vt9 So I was hoping to issue the systemctl list-jobs command from the debug shell, however, it didn't allow me to type in commands. The debug shell allows

Re: [systemd-devel] Shutdown notify

? Note that I do NOT have PolicyKit in the system... BR, Michal -Original Message- From: Lennart Poettering [mailto:lenn...@poettering.net] Sent: Tuesday, August 19, 2014 1:40 PM To: Michal Witanowski Cc: systemd-devel@lists.freedesktop.org Subject: Re: [systemd-devel] Shutdown notify

Re: [systemd-devel] Shutdown notify

On Wed, 20.08.14 15:50, Michal Witanowski (m.witanow...@samsung.com) wrote: The inhibit locks mechanism seems to be the solution, but another problem appeared. I am unable to call Inhibit() method as non-root user. In the documentation I read Taking inhibitor locks is a privileged operation.

Re: [systemd-devel] Shutdown notify

Lennart Poettering wrote on 20/08/14 14:58: On Wed, 20.08.14 15:50, Michal Witanowski (m.witanow...@samsung.com) wrote: The inhibit locks mechanism seems to be the solution, but another problem appeared. I am unable to call Inhibit() method as non-root user. In the documentation I read

[systemd-devel] Shutdown notify

Hi all, I would like to know if there is a possibility to get notified about upcoming shutdown/restart. For example: . Somebody executes systemctl reboot / systemctl poweroff . A callback function is called in my service before SIGTERM is triggered on ANY service. .

Re: [systemd-devel] Shutdown notify

On Tue, 19.08.14 13:34, Michal Witanowski (m.witanow...@samsung.com) wrote: Hi all, I would like to know if there is a possibility to get notified about upcoming shutdown/restart. For example: . Somebody executes systemctl reboot / systemctl poweroff . A callback

Re: [systemd-devel] Shutdown notify

What if I'm using systemd built without logind? -Original Message- From: Lennart Poettering [mailto:lenn...@poettering.net] Sent: Tuesday, August 19, 2014 1:40 PM To: Michal Witanowski Cc: systemd-devel@lists.freedesktop.org Subject: Re: [systemd-devel] Shutdown notify On Tue, 19.08.14

Re: [systemd-devel] Shutdown notify

On Tue, 19.08.14 14:49, Michal Witanowski (m.witanow...@samsung.com) wrote: What if I'm using systemd built without logind? Not available then. Sorry. You only have the time between SIGTERM and your processes' exit(). It's pretty much logind's job to implement things like these inhibitors. If

Re: [systemd-devel] shutdown umount order

CG 'Twas brillig, and Ilya Basin at 04/01/13 22:22 did gyre and gimble: Hi list. On shutdown I have Buffer I/O error on device dm-... because the truecrypt disk is unmounted later than the usb disk containing the truecrypt image. I think this happens, because 1) systemd can't figure out

Re: [systemd-devel] shutdown umount order

В Sat, 16 Mar 2013 16:17:37 +0400 Ilya Basin basini...@gmail.com пишет: CG 'Twas brillig, and Ilya Basin at 04/01/13 22:22 did gyre and gimble: Hi list. On shutdown I have Buffer I/O error on device dm-... because the truecrypt disk is unmounted later than the usb disk containing

Re: [systemd-devel] shutdown umount order

On Sat, 05.01.13 02:22, Ilya Basin (basini...@gmail.com) wrote: Hi list. On shutdown I have Buffer I/O error on device dm-... because the truecrypt disk is unmounted later than the usb disk containing the truecrypt image. I think this happens, because 1) systemd can't figure out the

Re: [systemd-devel] shutdown umount order

'Twas brillig, and Ilya Basin at 04/01/13 22:22 did gyre and gimble: Hi list. On shutdown I have Buffer I/O error on device dm-... because the truecrypt disk is unmounted later than the usb disk containing the truecrypt image. I think this happens, because 1) systemd can't figure out the

Re: [systemd-devel] shutdown umount order

DR On Sat, Jan 05, 2013 at 02:22:11AM +0400, Ilya Basin wrote: Hi list. On shutdown I have Buffer I/O error on device dm-... because the truecrypt disk is unmounted later than the usb disk containing the truecrypt image. I think this happens, because 1) systemd can't figure out the

[systemd-devel] shutdown umount order

Hi list. On shutdown I have Buffer I/O error on device dm-... because the truecrypt disk is unmounted later than the usb disk containing the truecrypt image. I think this happens, because 1) systemd can't figure out the correct mount dependencies 2) umount is called with the force flag

Re: [systemd-devel] shutdown umount order

On Sat, Jan 05, 2013 at 02:22:11AM +0400, Ilya Basin wrote: Hi list. On shutdown I have Buffer I/O error on device dm-... because the truecrypt disk is unmounted later than the usb disk containing the truecrypt image. I think this happens, because 1) systemd can't figure out the correct

Re: [systemd-devel] shutdown pivot to /run/initramfs

On Fri, Jul 22, 2011 at 4:41 AM, Lennart Poettering lenn...@poettering.net wrote: On Fri, 22.07.11 01:56, Tom Gundersen (t...@jklm.no) wrote: I'm playing around with the new shutdown pivot mechanism (using v30), Try again with current git. I merged a patch from Harald now, that fixes this.

[systemd-devel] shutdown pivot to /run/initramfs

Hi guys, I'm playing around with the new shutdown pivot mechanism (using v30), and trying to make it work without using dracut (as Arch has its own initramfs implementation). I ran across a problem related to pivot_to_new_root(), and wondered if anyone could point me in the right direction. A

Re: [systemd-devel] shutdown pivot to /run/initramfs

On Fri, 22.07.11 01:56, Tom Gundersen (t...@jklm.no) wrote: Hi guys, I'm playing around with the new shutdown pivot mechanism (using v30), and trying to make it work without using dracut (as Arch has its own initramfs implementation). I ran across a problem related to pivot_to_new_root(),