r Daan,
>
>
> Thank you very much for your reply.
>
>
> Am 04.03.24 um 15:52 schrieb Daan De Meyer:
>
> > Please see the config included in the mkosi repository itself:
> > https://github.com/systemd/mkosi/blob/main/mkosi.conf and
> > https://github.com/syst
Hi Nils,
Pretty sure nobody ever tried this. The root hash might be changing
because we format the verity hash partition with different parameters
than it was originally formatted with in your case. I assume the
roothash will only stay the same if the verity format arguments are
exactly the same.
Hi Aleksandar,
> I want to enable systemd-resolved in early boot so that `clevis` can
> resolve `tang` address by mdns. This will simplify local network
> configuration by not relying on static IP addresses.
> But it seems that is not enabled by default.
> Is there a way to tell dracut to also i
Hi Paul,
Please see the config included in the mkosi repository itself:
https://github.com/systemd/mkosi/blob/main/mkosi.conf and
https://github.com/systemd/mkosi/tree/main/mkosi.conf.d. This should
help you get started. https://mkosi.systemd.io/bootable.html shows how
to build a minimal bootable
> We have been working on a new initial filesystem called initoverlayfs.
> It is a new filesystem that provides a more scalable approach to
> initial filesystems as opposed to just using initrds. We are writing
> this RFC to the systemd and dracut mailing lists (feel free to forward
> to UAPI group
Note that we also have `InitrdPackages=` in the latest mkosi release
which allows you to add extra packages to the default initrd without
having to build one separately.
Cheers,
Daan
On Wed, 6 Dec 2023 at 14:26, Renjaya Raga Zenta wrote:
>
> Yes, I think now I understand that mkosi will build d
Unfortunately there's no ready made answer yet here. We're busy designing
and implementing a solution for these problems.
https://github.com/systemd/systemd/pull/27792 has more details.
Cheers,
Daan
On Fri, 18 Aug 2023, 19:44 Nils Kattenbeck, wrote:
> Hi,
>
> currently I am building a minimali
you I would ship 99-disable.preset and add 85-mydevice.preset
enabling only the services you want to be enabled.
Cheers,
Daan
On Sat, 29 Apr 2023, 17:47 Martin Petzold, wrote:
> Dear Daan,
> Am 29.04.23 um 17:43 schrieb Daan De Meyer:
>
> Systemd does a preset on first boot whe
Systemd does a preset on first boot when there's no machine ID yet. If no
preset from a preset file applies, the default is to enable it. Since
debian does not ship a 99-disable.preset with disable * in it, all services
are enabled on firstboot on Debian.
Cheers,
Daan
On Sat, 29 Apr 2023, 17:27
See the hacking guide, we depend on very latest mkosi from git.
On Fri, 17 Mar 2023, 22:55 William Roberts,
wrote:
> I am on Fedora 37, I did a dnf up and rebooted to make sure that's not
> the issue.
>
> With the mkosi from the pkg manager, I am getting:
> mkosi
> mkosi: error: unrecognized arg
Hi All,
I'm sending this to both systemd-devel and lkml since I'm not sure
what is causing this.
For some reason the msi-laptop module is not autoloading on a
MSI S270 (yes that is a very old laptop).
Here is some debugging info:
$ cat /sys/class/dmi/id/modalias
dmi:bvnAmericanMegatrendsInc.:bv
Hi,
On 6/27/22 21:50, Gwendal Grignou wrote:
> In 60-sensor.hwdb, we can specify a matrix to rotate sensor output to
> match the expected 'natural' orientation [1].
>
> When behind a screen, accelerometers are usually soldered upside down,
> so a rotation matrix is needed to rotate their raw outp
I'd also recommend opening an issue on the upstream issue tracker
(https://github.com/systemd/systemd/issues). It'd be great if you
could include a full journal (just zip up /var/log/journal) and the
contents of systemd-cryptsetup@myluksdev.service if possible to help
with debugging.
Cheers,
Daan
Hello Manuel,
my experience is that it is helpful for people new to systemd to "raise the
right question" that is answered by the corresponding relationship between
systemd units.
The question "*if* a unit shall be started/enqueued" is answered
Wants=/Requires=/BindsTo relation. I call this th
Hi,
On 8/31/21 3:08 PM, Hans de Goede wrote:
> Hi,
>
> I BCc-ed systemd-devel on this, to avoid reply-to-all from kernel folks
> getting bounces because of them not being subscribed, but it seems the
> list does not like being in the BCc, so hence this forward.
>
> Note
emd/issues/20550
Link: https://github.com/systemd/systemd/pull/20562
Fixes: e26f023e01ef ("firmware/dmi: Include product_sku info to modalias")
Cc: sta...@vger.kernel.org
Cc: Kai-Chuan Hsieh
Cc: Erwan Velu
Signed-off-by: Hans de Goede
---
drivers/firmware/dmi-id.c | 6 +-
1 file ch
ixing this on the systemd/hwdb side.
Regards,
Hans
Forwarded Message
Subject: [PATCH regression fix] firmware/dmi: Move product_sku info to the end
of the modalias
Date: Tue, 31 Aug 2021 15:05:08 +0200
From: Hans de Goede
To: Jean Delvare
CC: Hans de Goede , linu
imal overhead.
>
> Reported-and-tested-by: Matthias Schwarzott
> Signed-off-by: Alan Stern
> CC:
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede
Regards,
Hans
>
> ---
>
>
> [as1953]
>
>
> drivers/usb/storage/transport.c|7
Hi,
On 3/17/21 6:56 PM, Matthias Schwarzott wrote:
> Am 17.03.21 um 16:17 schrieb Alan Stern:
>> On Wed, Mar 17, 2021 at 01:21:50PM +0100, Hans de Goede wrote:
>>> Hi,
>>>
>>> On 3/16/21 6:04 PM, Alan Stern wrote:
>>>> I think it would be mildly bet
Hi,
On 3/16/21 6:04 PM, Alan Stern wrote:
> On Tue, Mar 16, 2021 at 05:43:34PM +0100, Hans de Goede wrote:
>> Hi,
>>
>> On 3/16/21 5:26 PM, Alan Stern wrote:
>>> On Tue, Mar 16, 2021 at 06:26:30AM +0100, Matthias Schwarzott wrote:
>>>> I implemented sol
Hi,
On 3/16/21 5:26 PM, Alan Stern wrote:
> On Tue, Mar 16, 2021 at 06:26:30AM +0100, Matthias Schwarzott wrote:
>> I implemented solution 3b. This is the pullrequest for udev (systemd
>> repository):
>>
>> https://github.com/systemd/systemd/pull/19002
>>
>> Now Lennart asks if udev is the be
Hi,
--repositories in mkosi is currently a bit limited. For Fedora and
CentOS, we only support passing names of existing repositories that
should be enabled. https://github.com/systemd/mkosi/issues/536
reported a similar problem. We should definitely make this work better
than it does now but it's
[Unit]
> StopWhenUnneeded=true
>
> [Service]
> Type=oneshot
> RemainAfterExit=yes
>
> # Not sure if SuccessAction works
> # probably does but you might need a dummy ExecStart=/sbin/true then
> ExecStop=systemctl poweroff
> #SuccessAction=exit
> ```
>
> Benjamin
>
s in, an instance of this template is
started to handle the connection. Now, what I want to achieve is that
when all instances of this sshd template exit after at least one
instance has started, the system shuts down.
Daan
On Sun, 23 Aug 2020 at 14:47, Daan De Meyer wrote:
>
> Hi,
Hi,
After following
http://0pointer.de/blog/projects/socket-activated-containers.html
which details how to set up a socket activated container, I'm looking
into ways to have the container automatically shut down when the last
ssh connection terminates.
My idea was to have each sshd instance take
nal via mkosi.
Daan
On Wed, 15 Jul 2020 at 17:09, Lennart Poettering
wrote:
> On Di, 14.07.20 22:15, Daan De Meyer (daan.j.deme...@gmail.com) wrote:
>
> > > About your other comments, systemd sits in user space and can query
> > (depend
> > > upon) terminfo
x27;t be too hard to
find out how to get them to work when using mkosi.
Thanks for all the info as well. It's always fun to read how stuff was done
back in the early days.
Daan
On Tue, 14 Jul 2020 at 21:04, Christopher Cox wrote:
> On 7/14/20 1:48 PM, Daan De Meyer wrote:
> > I just tri
I just tried vt241 and didn't get colorized output in konsole. I looked
around a bit and it doesn't really seem supported at all by terminal
emulators (or at least none that I found). I also tried TERM=xterm-256color
with 8 different terminal emulators and got colors with all of them. My
workflow i
Hi,
On 7/14/20 10:03 AM, Lennart Poettering wrote:
On Di, 30.06.20 12:17, Hans de Goede (hdego...@redhat.com) wrote:
1. The user has logged in successfully and the session lasts
at least 2 minutes (could be a bit shorter, we want to catch the
case where the session immediately exits / crashes
Hi again,
On 7/13/20 4:11 PM, Hans de Goede wrote:
Hi All,
$subject is somewhat misleading, what I actually want is to make:
systemctl reboot --boot-loader-menu=60
Work as a regular user (who is physically present at the console).
So I looked at:
/usr/share/polkit-1/actions
Hi All,
$subject is somewhat misleading, what I actually want is to make:
systemctl reboot --boot-loader-menu=60
Work as a regular user (who is physically present at the console).
So I looked at:
/usr/share/polkit-1/actions/org.freedesktop.login1.policy, which has:
R
Nevermind that, I just forgot to remove my override file that set
TERM=linux for serial-getty@ttyS0.
Daan
On Sat, 11 Jul 2020 at 20:31, Daan De Meyer
wrote:
> > TERM=linux means Linux console, but that's just too much, as it not
> > only implies a multitude of ESC sequence
context.
Daan
On Sat, 11 Jul 2020 at 20:04, Lennart Poettering
wrote:
> On Sa, 11.07.20 17:51, Daan De Meyer (daan.j.deme...@gmail.com) wrote:
>
> > Hi,
> >
> > I was playing around with mkosi's qemu support, more specifically adding
> > the -nographic option t
Hi,
I was playing around with mkosi's qemu support, more specifically adding
the -nographic option to have the virtual machine output in my terminal
instead of a separate window. After figuring out that I had to add
console=ttyS0 to mkosi's kernel command line, I got the output from the vm
in my t
Hi,
On 6/30/20 11:36 AM, Lennart Poettering wrote:
On Mo, 29.06.20 11:02, Hans de Goede (hdego...@redhat.com) wrote:
Hi All,
For Fedora 33 I would like to get rid of some ugly hacks we have
wrt the grub-hidden-menu feature Fedora has been shipping for a
while now.
One part of this will be
Hi All,
For Fedora 33 I would like to get rid of some ugly hacks we have
wrt the grub-hidden-menu feature Fedora has been shipping for a
while now.
One part of this will be setting SYSTEMD_REBOOT_TO_BOOT_LOADER_ENTRY
in logind's environment, and add /run/systemd/reboot-to-boot-loader-menu
suppor
Hi,
I've opened a pull request to clarify the return values of the callbacks
and their effect: https://github.com/systemd/systemd/pull/15253. It's not
complete yet but the idea is to add answers for all your questions to the
docs.
Regards,
Daan
On Tue, 24 Mar 2020 at 21:44, Stanislav Angelovič
Tue, 17 Mar 2020 at 20:17:05 +0100, Daan De Meyer wrote:
> > I'm documenting sd_bus_call and its async variant and I was wondering
> about the
> > sd_bus_error output parameter that's passed to it. [...] I don't
> > see immediately see the benefit of the sd_bus_
e initial D-Bus
method call? I don't see immediately see the benefit of the sd_bus_error
parameter in a D-Bus client since I can simply check the return value
instead which seems to contain the same information looking at the
implementation.
Reg
t if a unit is named a-b-c.service, systemd will look for
> dropins named a-b-.service and a-.service... there might be something to do
> with that, but I havn't given it much thought
>
> Le ven. 27 sept. 2019 à 18:28, Mantas Mikulėnas a
> écrit :
>
>> On Fri, Sep 27,
Hi,
On 30-09-2019 13:23, Hans de Goede wrote:
Hi,
On 29-09-2019 12:08, Lennart Poettering wrote:
On Fr, 27.09.19 16:00, Hans de Goede (hdego...@redhat.com) wrote:
Anyway, even if you insist that the Fedora desktop should care about
non-EFI, which I can accept, isn't the lesson to
Hi,
On 29-09-2019 12:08, Lennart Poettering wrote:
On Fr, 27.09.19 16:00, Hans de Goede (hdego...@redhat.com) wrote:
Anyway, even if you insist that the Fedora desktop should care about
non-EFI, which I can accept, isn't the lesson to learn to add some
concept like EFI vars to those
Hi,
On 9/27/19 1:59 PM, Lennart Poettering wrote:
On Fr, 27.09.19 10:20, Hans de Goede (hdego...@redhat.com) wrote:
"So my plan for regular Fedora for this is as follows:
1. Have a /boot/initramfs-config.img which for now will just contain
/etc/vconsole.conf (chances are this wil
hi all,
i'm looking for an "easy" way to set resource limits on a group of users.
we are lucky enough that this group of users is within a (although
large) high enough range, so a range of uids is ok for us.
generating a user-.slice file for every user (or symlink them or
whatever) looks a bit c
Hi,
On 9/27/19 1:49 PM, Lennart Poettering wrote:
On Mi, 25.09.19 16:50, Hans de Goede (hdego...@redhat.com) wrote:
Hi all,
Currently, at least in Fedora, but I do not believe that this problem is
unique to Fedora, there are 2 problems with keymap handling in the
initrd.
Hmm, why do you
ee if this will also
work for them. If they are happy with this then I plan to start implementing
this when I'm done with the plymouth keyboard layout indicator stuff.
Regards,
Hans
On Thu, Sep 26, 2019 at 12:43 PM Hans de Goede mailto:hdego...@redhat.com>> wrote:
Hi,
On
Hi,
On 26-09-2019 11:53, Michael Chapman wrote:
On Thu, 26 Sep 2019, Hans de Goede wrote:
Hi,
On 26-09-2019 11:10, Michael Chapman wrote:
On Thu, 26 Sep 2019, Hans de Goede wrote:
[...]
I believe that the best alternative is to have localed append / update
a rd.vconsole.keymap=foo argument
Hi,
On 26-09-2019 11:10, Michael Chapman wrote:
On Thu, 26 Sep 2019, Hans de Goede wrote:
[...]
I believe that the best alternative is to have localed append / update
a rd.vconsole.keymap=foo argument to the kernel commandline, to override
the vconsole.conf KEYMAP setting, but only in the
Hi all,
Currently, at least in Fedora, but I do not believe that this problem is
unique to Fedora, there are 2 problems with keymap handling in the initrd.
1: If the keymap in vconsole.conf is changed then this does not apply to the
initrd without rebuilding it. This means that any changes are o
Hi,
On 05-09-19 14:11, Hans de Goede wrote:
Hi,
On 05-09-19 13:28, Bastien Nocera wrote:
On Thu, 2019-09-05 at 13:13 +0200, Hans de Goede wrote:
Hi,
On 05-09-19 12:49, Bastien Nocera wrote:
On Thu, 2019-09-05 at 18:38 +0800, Daniel Drake wrote:
On Thu, Sep 5, 2019 at 6:07 PM Bastien
Hi,
On 05-09-19 13:28, Bastien Nocera wrote:
On Thu, 2019-09-05 at 13:13 +0200, Hans de Goede wrote:
Hi,
On 05-09-19 12:49, Bastien Nocera wrote:
On Thu, 2019-09-05 at 18:38 +0800, Daniel Drake wrote:
On Thu, Sep 5, 2019 at 6:07 PM Bastien Nocera
wrote:
I've read through this, an
Hi,
On 05-09-19 12:49, Bastien Nocera wrote:
On Thu, 2019-09-05 at 18:38 +0800, Daniel Drake wrote:
On Thu, Sep 5, 2019 at 6:07 PM Bastien Nocera
wrote:
I've read through this, and I'm happy blacklisting the hp_accel
driver
in code. For the other devices, I'd rather leave it as-is.
That wou
Hi Daniel,
On 05-09-19 11:05, Daniel Drake wrote:
Hi,
so sometimes we even apply the
wrong quirks. Two recent examples:
https://bugzilla.redhat.com/show_bug.cgi?id=1717712 (more on this case below)
I see the latest development of having the hwdb specify whether the
accelerometer is in
Hi,
On 02-09-19 07:17, Mantas Mikulėnas wrote:
On Mon, Sep 2, 2019 at 7:34 AM Chris Murphy mailto:li...@colorremedies.com>> wrote:
systemd-243~rc2-2.fc31.x86_64
kernel-5.3.0-0.rc6.git1.1.fc32.x86_64
This might be a regression, at least I don't remember this happening
before. I
Hi All,
I already filed a github issue for $subject:
https://github.com/systemd/systemd/issues/13437
But I'm not sure how close github issues are watched hence this email. It would
be nice if we can get this fixed for F31 beta, or if some more time is needed,
at least get this regression fixed
On 28-08-19 14:41, Lennart Poettering wrote:
On Mi, 28.08.19 09:33, Ulrich Windl (ulrich.wi...@rz.uni-regensburg.de) wrote:
Hi!
systemd in SLES 12 is causing endless frustration here:
Yesterday I was migrating some filesystems to a new device (multipath, MD-RAID,
LVM, filesystem, mountpoints
On 28-08-19 11:54, Reindl Harald wrote:
Am 28.08.19 um 11:24 schrieb Frans de Boer:
Unnecessary use of shaming and hurting words. Although the intention was
good, systemd is - in my view - overly complex. And yes, when starting
with it, one should read the manuals at least once, as a matter of
On 28-08-19 10:46, Reindl Harald wrote:
Am 28.08.19 um 09:33 schrieb Ulrich Windl:
systemd in SLES 12 is causing endless frustration here:
a good start for a discussion as always :-)
just the topic "/etc/fstab obsolete?" alone makes one puke given that
/etc/fstab is mentioned dozens of times
Hi Lennart,
On 31-07-19 14:07, Lennart Poettering wrote:
On Di, 30.07.19 10:49, Hans de Goede (hdego...@redhat.com) wrote:
I believe that the best way to fix is this is probably to specify the
keymap on the kernel commandline using vconsole.keymap= on the kernel
commandline.
As you found
Hi,
On 30-07-19 10:49, Hans de Goede wrote:
Hi All,
When using full-disk encryption the console keymap is used in the
initrd to enter the disk-crypt password.
There are a couple of issues with this:
1) keymap changes do not become effective until a new kernel
(which generated a new initrd
Hi All,
When using full-disk encryption the console keymap is used in the
initrd to enter the disk-crypt password.
There are a couple of issues with this:
1) keymap changes do not become effective until a new kernel
(which generated a new initrd which includes the updated vconsole.conf)
gets in
systemd-cryptsetup to crash
either when a single large password is used or when multiple passwords have
already been pushed to the keyring.
Signed-off-by: Thadeu Lima de Souza Cascardo
---
src/shared/ask-password-api.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/shared/ask
Hi,
On 28-02-19 10:27, Colin Guthrie wrote:
Hans de Goede wrote on 27/02/2019 19:12:
On 27-02-19 17:04, Lennart Poettering wrote:
Another option is to do this in your soruces btw:
```c
(void) kill(1, SIGRTMIN+21);
```
Sending SIGRTMIN+21 to PID 1 will disable the status output
explicitly
Hi,
On 27-02-19 17:04, Lennart Poettering wrote:
On Mi, 27.02.19 15:56, Hans de Goede (hdego...@redhat.com) wrote:
Hi,
On 27-02-19 12:50, Lennart Poettering wrote:
On Mi, 27.02.19 10:40, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Tue, Feb 26, 2019 at 7:29 PM Hans de Goede wrote:
Hi
Hi,
On 27-02-19 12:50, Lennart Poettering wrote:
On Mi, 27.02.19 10:40, Mantas Mikulėnas (graw...@gmail.com) wrote:
On Tue, Feb 26, 2019 at 7:29 PM Hans de Goede wrote:
Hi All,
As part of improving the boot experience:
https://fedoraproject.org/wiki/Changes/FlickerFreeBoot
https
Hi All,
As part of improving the boot experience:
https://fedoraproject.org/wiki/Changes/FlickerFreeBoot
https://hansdegoede.livejournal.com/20119.html
I took a look at how applying offline updates looks
when pressing ESC to get the detailed view, pk-offline-update
then prints "dnf update" like
Kenneth Porter:
OTOH, most of us learned from reading the writings of others in the
industry. So perhaps the wisdom of this thread should get captured in
a blog post by a security expert so it can be shared around on
multiple mailing lists and forums.
One can learn from the example of Daniel
On 07/20/2018 09:28 PM, Frans de Boer wrote:
Dear Reader,
I am building my own linux system with systemd, following the
directions given by de LFS (linux from scratch) project. Until some
time ago all went well, but after systemd 232 (i think) - anyhow right
at the time that they start using
Dear Reader,
I am building my own linux system with systemd, following the directions
given by de LFS (linux from scratch) project. Until some time ago all
went well, but after systemd 232 (i think) - anyhow right at the time
that they start using meson/ninja to build systemd - I could not
Hi,
On 13-06-18 17:05, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jun 13, 2018 at 04:55:27PM +0200, Hans de Goede wrote:
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
AFAIK the service actually doing the updates is
Hi,
On 13-06-18 17:05, Zbigniew Jędrzejewski-Szmek wrote:
On Wed, Jun 13, 2018 at 04:55:27PM +0200, Hans de Goede wrote:
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
AFAIK the service actually doing the updates is
Hi,
On 12-06-18 19:11, Lennart Poettering wrote:
On Di, 12.06.18 11:33, Hans de Goede (hdego...@redhat.com) wrote:
AFAIK the service actually doing the updates is supposed to call
systemctl reboot --force when it is done, so any targets after
system-update.target won't get started ?
Hi,
On 13-06-18 05:40, Alexander E. Patrakov wrote:
Hans de Goede :
Hi All,
So as you may have heard, I'm working on hiding the grub-menu
by default on single OS Fedora Workstation. Part of the plan
here is to detect if a previous boot was successful and
cleanly shutdown the machin
Hi,
The mention of "systemctl reboot --firmware" in the other thread
made me realize that it would be good to also have a
"systemctl reboot --bootmenu".
First a question about "systemctl reboot --firmware" is this
available to a normal user (through policykit and the user
being on a physical att
Hi,
On 12-06-18 10:24, Lennart Poettering wrote:
On Mo, 11.06.18 17:40, Hans de Goede (hdego...@redhat.com) wrote:
It am very sure it's not worth trying to maintain a shutdown_sucess
variable that is determined that early. That's a pointless excercise,
OB> > you won't
Hi,
On 11-06-18 17:48, Jérémy Rosen wrote:
We solve a problem which is kinda similar in the embedded world when we do A/B
update
I'll describe how we do it so you see if this can help
* Have a single "last boot went wrong" flag
When grub starts
* if the flag is set, show the boot menu (or a t
Hi,
On 11-06-18 16:37, Lennart Poettering wrote:
On Mo, 11.06.18 15:37, Hans de Goede (hdego...@redhat.com) wrote:
Uurks. Quite frankly, it appears strange to me to delay this for this
long. I mean we reworked most code that delayed worked to shutdown
like this these days to happen as early
Hi,
On 11-06-18 13:31, Lennart Poettering wrote:
On Mo, 11.06.18 12:48, Hans de Goede (hdego...@redhat.com) wrote:
Hi All,
So as you may have heard, I'm working on hiding the grub-menu
by default on single OS Fedora Workstation. Part of the plan
here is to detect if a previous boo
Hi All,
So as you may have heard, I'm working on hiding the grub-menu
by default on single OS Fedora Workstation. Part of the plan
here is to detect if a previous boot was successful and
cleanly shutdown the machine and show the menu (not hide the
menu) if the previous boot has failed to set eit
Mantas Mikulėnas:
Maybe socket-activation would work for you? (With Nginx it's also a
hack though.)
Accept=No
Environment=NGINX=3;
It is not terrifically complex. The documented way to stop the forking
is "daemon off", but an inherited listening socket also does it.
* https://bugs.debian.o
st...@goodey.org:
[Service]
Type=forking
Your program has an -f option to stop it from vainly trying to
re-daemonize itself. Use it; and do not use Type=forking in the first
place.
*
http://jdebp.eu./FGA/unix-daemon-design-mistakes-to-avoid.html#DoNotBackgroundise
The supplied systemd
Cecil Westerhof:
Other services I can enable and disable.
And with chmod a-x /etc/init.d/tomcat8 you should
be able to disable this one, too. (-:
Read https://unix.stackexchange.com/a/394191/5132 for why.
Tom H:
The usual reason for not having a native unit is that you can't
force developers to do that work.
Psst! This discussion is predicated upon a falsehood. There is
an abundance of service units for Tomcat, and has been for years.
Lennart Poettering:
Uh, I am not sure what celery is, but if celery is started but exitson
its own then I am not sure I can help you very much.
Does it detach on its own? i.e. double fork? if yes, then type=forking
is the right choice, otherwise you need a different Type=.
A tip from one
Warner Losh, FreeBSD and embedded systems developer, has just invented a
new shutdowngoal, in addition to the ones that we already know. In
addition to the conventional reset, power off, halt, and kexec goals; xe
has added a power-off-and-then-on-again goal. Xe has named it power
cycle, and i
On 04/10/17 13:09, Lennart Poettering wrote:
> Ah, uh, I forgot that your image is a block device. We are missing
> some support there for that. /var/lib/machines may only contain
> dirs/subvols and raw files right now, we don't support block
> devices. But adding support for that should be easy, t
On 04/10/17 11:31, Lennart Poettering wrote:
> The image dissection logic can deal with either. The GPT approach is a
> bit nicer I think since the root partition can be marked as such, and
All right, makes sense.
>> 2) machinectl list-images doesn't detect the images in LVs; am I
>> supposed to
rvice
instances. This way, a new enabled-after-boot vm would be started with
"systemctl restart xendomains". I could use the existence of
/etc/xen/auto/vm or /var/lib/xen/save/vm as requirement
for xendomains@vm.service, in order to avoid to start a disabled-after-boot
vm. However, this does
and launch it using a systemd timer if the
xendomains that depends on MD devices isn't started after 30s. It looks
ugly but it might work.
Regards,
--
Luiz Angelo Daros de Luca
luizl...@gmail.com
___
systemd-devel mailing list
s
Reindl Harald:
> at least fall back to “nobody”
Jonathan de Boyne Pollard:
> That idea is wrong.
>
> https://news.ycombinator.com/item?id=14681377#14682059
Reindl Harald:
> better than a stupid [...]
Not really, no. It's the same category of error, in fact: substituting a
Reindl Harald:
>
> at least fall back to "nobody"
>
That idea is wrong.
https://news.ycombinator.com/item?id=14681377#14682059___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/system
gotiation, server referrals, and
> named attributes.
> .BR rpc.idmapd (8),
> .BR rpc.gssd (8),
> .BR rpc.svcgssd (8),
> -.BR kerberos (1)
> +.BR kerberos (1),
> +.BR systemd.mount (5) .
> .sp
> RFC 768 for the UDP specification.
> .br
> --
> 2.12.2
>
"Igal @ Lucee.org" :
> Examples I see online use forking [...]
Jonathan de Boyne Pollard:
> ... because they are bad examples.
> Read http://jdebp.eu./FGA/systemd-house-of-horror/tomcat.html .
Andrei Borzenkov:
> Service type simple is the worst possible type as it d
"Igal @ Lucee.org" :
> Examples I see online use forking [...]
... because they are bad examples. Read
http://jdebp.eu./FGA/systemd-house-of-horror/tomcat.html .
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedeskto
Christian Rebischke:
> I would like to start ibus-daemon automatically on login in my user session.
The person who told you that this was unnecessary because ibus already has a way
to run the daemon via "bus activation" is wrong. There are various good reasons
to avoid bus activation, especially
Owens, Stephen:
The start script calls other scripts to start two application
components and then the start script exits.
One of the application components also spawns a couple of child processes.
There ends up being two pid files, one for each component, describing
the state of the applicat
Owens, Stephen:
UMask=0764
This is almost certainly wrong, by the way.
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Reindl Harald:
earlier systems (sysvinit) hat no concept like emergency mode
This is a falsehood. Emergency mode was invented in December 1995,
ironically for that very system.
* http://jdebp.eu./FGA/emergency-and-rescue-mode-bootstrap.html
___
sy
Lennart Poettering:
"nofail" has been around as long as fstab has been around really.
This is a falsehood. /etc/fstab has a history that goes back to the
20th century. It was in UNIX System 5 Release 3, 4.2BSD, and OSF/1, for
examples. In contrast, the "nofail" option was invented in Dece
Benoit SCHMID:
echo -n "Starting Oracle Listener: "
su - $ORA_OWNR -c "env ORACLE_HOME=/oracle/XXX/12102
/oracle/XXX/12102/bin/lsnrctl start LISTENER_XXX"
Don't abuse su for dropping privileges.
* http://jdebp.eu./FGA/dont-abuse-su-for-dropping-privileges.html
It's now 201
1 - 100 of 309 matches
Mail list logo
