> 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 L
> 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
https://pubs.opengroup.org/onlinepubs/9
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
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.
>
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
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. Ke
> 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
, 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
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. O
ce fails to start with no log
messages (Ulrich Windl)
--
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; charse
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,
> > need
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 b
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 problem
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 li
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 u
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 ser
> 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 o
-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.
>
> Wit
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.
>> O
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 supervisor,
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 occur
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 LUKS
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 i
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. system
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 advanc
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 bu
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 bu
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 Chapma
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 fou
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 typic
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
speci
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 la
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 a
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 updating, a previously
> > operat
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
> st
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 pause
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 test
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 specific stop before the
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,
BRs,
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 is
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 there is any ways to
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 al
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 "s
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
systemd-halt.ser
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 "first"/
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
On Fri, 22.04.16 11:49, Michael Lipp (m...@mnl.de) 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
> loopback de
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 11:49:09AM +0200, Michael Lipp
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
> loopback
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.
Howeve
On Mon, Feb 23, 2015 at 1:33 PM, JB 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 of the serv
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
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 reply
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? W
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?
> >>>
> P
Nikolaus Rath writes:
> On 11/13/2014 12:54 PM, Nikolaus Rath wrote:
>> Nikolaus Rath writes:
>>> Lennart Poettering 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 w
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
t
Nikolaus Rath writes:
> On 11/13/2014 12:54 PM, Nikolaus Rath wrote:
>> Nikolaus Rath writes:
>>> Lennart Poettering 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 w
On 11/13/2014 12:54 PM, Nikolaus Rath wrote:
> Nikolaus Rath writes:
>> Lennart Poettering 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
Nikolaus Rath writes:
> Lennart Poettering 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
Lennart Poettering 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 for that her
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.
Lennart Poettering 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,
>>everythin
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 "sy
Am 2014-11-07 04:07, schrieb Nikolaus Rath:
$ cat /lib/systemd/system-shutdown/debug.sh
#!/bin/sh
exec > /shutdown.log
exec 2>&1
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
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 waitin
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
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
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 operat
sers
group? 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
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
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.
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 call
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.
.
On Sat, Mar 16, 2013 at 04:17:37PM +0400, Ilya Basin wrote:
> >> 1) I think the mount dependencies can't be made 100% reliable. systemd
> >> should use the combination of them and /proc/mounts, but only as a HINT
> >> In my case /proc/mounts contains the right order.
> >> 2) Instead of force umount
В Sat, 16 Mar 2013 16:17:37 +0400
Ilya Basin пишет:
> 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 t
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
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 t
'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 o
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
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 co
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
-
On Fri, Jul 22, 2011 at 4:41 AM, Lennart Poettering
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.
Thanks! Now it works
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_roo
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 min
85 matches
Mail list logo
