Re: [systemd-devel] 回复: Is it possible to send a string to the journal of one specific systemd unit
On Fri, 2021-10-22 at 08:42 +, DHAIY DHAIY wrote: > But is there a way to insert one string from command-line into > myservice's journal so that it can be seen byjournalctl -u myservice > later Try this: $ echo "foo" | systemd-cat -t foobar Then you can access your string with: $ journalctl -t foobar S
Re: [systemd-devel] systemd-resolved only returns v6 addresses
On Wed, 2021-01-27 at 13:10 +0200, Mantas Mikulėnas wrote: > So it is entirely possible that when resolved makes two queries, one > for A records and another for , it receives conflicting > information about the target simultaneously being an alias and not > being an alias (due to your upstream resolver choosing different NS > each time), and I wouldn't be surprised if that causes resolved to > reject (or just overlook) some of the returned DNS records. Thanks for the analysis! I am wondering what's the issue here: Is * my upstream DNS resolver broken? * Microsoft's DNS setup broken? * has systemd-resolved a bug? For the first point I will see what I can do. Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] systemd-resolved only returns v6 addresses
Heya, I was confronted with a weird problem this morning. On my location there is only IPv4 available. My company uses the shiny new Office365 service for email. This morning I was not able to connect to my email account. The reason was systemd-resolved returning only IPv6 addresses for the email host: $ resolvectl query outlook.office365.com outlook.office365.com: 2603:1026:c0a:855::2-- link: enp3s0 2603:1026:c0a:857::2-- link: enp3s0 2603:1026:c0a:8b7::2-- link: enp3s0 2603:1026:c0a:850::2-- link: enp3s0 2603:1026:c0a:852::2-- link: enp3s0 2603:1026:c0a:851::2-- link: enp3s0 2603:1026:101:1::2 -- link: enp3s0 2603:1026:c0a:854::2-- link: enp3s0 (outlook.ha.office365.com) -- Information acquired via protocol DNS in 820us. -- Data is authenticated: no The `host` utility instead reports this: $ host outlook.office365.com outlook.office365.com is an alias for outlook.ha.office365.com. outlook.ha.office365.com is an alias for outlook.ms-acdc.office.com. outlook.ms-acdc.office.com is an alias for AMS-efz.ms-acdc.office.com. AMS-efz.ms-acdc.office.com has address 40.101.12.66 AMS-efz.ms-acdc.office.com has address 52.97.250.210 AMS-efz.ms-acdc.office.com has address 40.101.121.34 AMS-efz.ms-acdc.office.com has address 52.97.155.114 AMS-efz.ms-acdc.office.com has IPv6 address 2603:1026:c03:581b::2 AMS-efz.ms-acdc.office.com has IPv6 address 2603:1026:207:177::2 AMS-efz.ms-acdc.office.com has IPv6 address 2603:1026:207:64::2 AMS-efz.ms-acdc.office.com has IPv6 address 2603:1026:206:4::2 The problem was that systemd-resolved only returned ipv6 addresses although I have no ipv6 connectivity. Why does this happen? Is there an artificial max. addresses limit with the sorting rule ipv6 first in systemd-resolved? I work-arounded it with an entry in /etc/hosts for now. Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd.journald.forward_to doesn't forward all journal messages
On Wed, 2019-07-31 at 16:27 -0600, Chris Murphy wrote: > The Obi Wan quote seems to apply here. "Who's the more foolish, the > fool, or the fool who follows him?" > > You're invited to stop following me. Calm down folks. I am certain he wanted to be sure that's not an xy problem: http://xyproblem.info/ Sometimes it makes sense to ask these questions in order to potentially save everyone's time. Maybe without the “ass” word, but anyway… S ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd prerelease 243-rc1
On Wed, 2019-07-31 at 13:47 +0200, Lennart Poettering wrote: > > What is this “strict” mode exactly? > > It just means resolved will insist on DNS-over-TLS to talk to the > configured DNS servers, instead of trying to use it and falling back > automatically if it's not available. Ahh. Thanks for the explanation. I was just wondering if certificate checks have been implemented. IIRC resolved does not check/validate the certificate (chain) of the DNS server. S ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd prerelease 243-rc1
On Tue, 2019-07-30 at 17:09 +, systemd tag bot wrote: > * systemd-resolved gained support for a new 'strict' DNS-over-TLS > mode. What is this “strict” mode exactly? S ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] All Systems Go 2018 talks video recordins
On Thu, Oct 4, 2018 at 9:17 AM Daniele Nicolodi wrote: > > Hello, > > where the talks at All Systems Go this years recorded as in previous > editions? If so, when can we expect to see them published? > > Thank you. https://media.ccc.de/c/asg2018 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] systemd[1]: Stopped (with error) /dev/mapper/wxyz.
On 25.07.2016 05:11, Dave T wrote: > I have a fileserver with several HDDs (btrfs and dm-crypt for all except > one which is lvm2 and dm-crypt). > > Within the last week when I umount a USB drive, all my other mounts > immediately get unmounted too. I lose /home and almost everything else > except the system device. The USB drive is the ESP (EFI system > partition) mounted at /boot. It is intended to be unmounted after boot > and it worked appropriately until the last week. > > If I reboot, all is fine until I umount the USB device (ESP). > > I have *not* tried to reproduce the behavior by umounting other devices > as this is a live fileserver. However, I can trigger this behavior 100% > of the time if I umount /boot. > > journalctl shows a number of messages similar to this: > > Jul 24 20:25:41 myserver systemd[1]: Stopped (with error) > /dev/mapper/wxyz. > -- Subject: Unit dev-mapper-wxyz.device has finished shutting down > -- Defined-By: systemd > -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel > -- > -- Unit dev-mapper-wxyz.device has finished shutting down. > > As I said, the system has started, in the last week, unmounting all > these other devices. Why? > > I am not a developer and I am new to systemd. I am happy to provide > additional information upon request. > Could it be this? https://github.com/systemd/systemd/issues/1620 ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [HEADS-UP] resolved APIs fully documented
On 23.02.2016 14:29, Lennart Poettering wrote: > Heya, > > just wanted to let you know that I finished documenting resolved's bus > APIs: > > https://wiki.freedesktop.org/www/Software/systemd/resolved/ > https://wiki.freedesktop.org/www/Software/systemd/writing-network-configuration-managers/ > https://wiki.freedesktop.org/www/Software/systemd/writing-resolver-clients/ The Wiki seems to be down: stefan@kronos ~> ping wiki.freedesktop.org PING annarchy.freedesktop.org (131.252.210.176) 56(84) bytes of data. Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] HEADS-UP: splitting python-systemd out
On Di, 2015-07-07 at 15:49 +0200, Michael Biebl wrote: Regarding the documentation: I failed to generate the documentation with sphinx since it didn't find the python modules. Do you have some instructions how this can be done. You could e. g. install the module (with pip in edit mode) in a virtualenv[1] using virtualenvwrapper[2]: $ mkvirtualenv python-systemd $ git clone https://github.com/systemd/python-systemd.git $ cd python-systemd $ pip install -e . Stefan [1]: https://pypi.python.org/pypi/virtualenv [2]: http://virtualenvwrapper.readthedocs.org/en/latest/index.html ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] [ANNOUNCE] Git development moved to github
On Tue, 2015-06-02 at 14:49 +, Zbigniew Jędrzejewski-Szmek wrote: Merging manually is quite a bit of work, as you have to add a new remote every time, fetch that, and pull from it. But it does keep a cleaner git log history. I'd very much prefer to keep current look of the git tree, without gratuitous merge commits. For bigger changes, which are composed of a larger number of commits, merges are fine. But most patchsets to systmed are either a single commit or two or three. You could append .patch to any github commit [1] or pull request [2] url and pipe them into git am with curl or something. Maybe that would be a workaround for pull request consisting of only one or two patches. Stefan [1]: https://github.com/systemd/systemd/commit/2fd51106ee0d685ca1512a01 e6680142382586a7.patch [2]: https://github.com/systemd/systemd/pull/41.patch ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] machinectl login machine fails systemd 219
On Di, 2015-04-14 at 21:56 +, Keller, Jacob E wrote: Failed to get machine PTY: Message did not receive a reply (timeout by message bus) I get a notification on the machine itself that it started container getty and then stopped it. It worked earlier so I am not sure what changed. No one on google seems to have this specific error. There is a patch which fixes this problem: http://lists.freedesktop.org/archives/systemd-devel/2015 -February/028603.html git log --grep tells me that is has been already commited as f2273101c21bc59a390379e182e53cd4f07a7e71: http://cgit.freedesktop.org/systemd/systemd/commit/?id=f2273101c21bc59a 390379e182e53cd4f07a7e71 Stay tuned, Stefan ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
