hi Kevin ,
Thank you very much for you help. But how can I save this way of closing time
synchronization by command after system boot up? After I update the system, the
first time I start it, time synchronization is still enabled by default. It's
not appropriate if I close it alone every time.
Thank you very much!.
On Thu, Apr 16, 2020 at 3:28 AM Lennart Poettering
wrote:
> On Mi, 15.04.20 13:46, Tarun Chinmai Sekar (tse...@asu.edu) wrote:
>
> > Hello Lennart,
> > Thank you for the quick response. I'd love to submit a PR to increase the
> > limit. Can you please point me to right part
I have a working-well configuration using PowerDNS Recursive Resolver
(running locally in my network, not provided by my ISP or anyone
upstream).
On Thu, Apr 16, 2020 at 12:46 PM Fabian Bernhard Pack
wrote:
>
> Hi,
>
> I've been slowly integrating systemd-resolved more and more into my
> setups,
Hi,
I've been slowly integrating systemd-resolved more and more into my
setups, but I had always encountered stability issues whenever the
upstream DNS resolver has some kind of DNSSEC support. Setting
DNSSEC=true would result in periods of no name resolution at all,
leaving it at the default `all
Susant Sahani writes:
> Please move this to GitHub with all the informations. It’s easy there
> to keep track.
>
For posterity:
I opened an issue at https://github.com/systemd/systemd/issues/15455
___
systemd-devel mailing list
systemd-devel@lists.fre
On Thu, 16 Apr 2020 at 14:03:43 +, Luca Boccassi wrote:
> But I found at least one other use case where this is needed, and the
> solution there is to add a new directory /host/ which replicates part
> of the host's filesystem tree, including os-release:
>
> https://docs.netdata.cloud/packagin
Hi,
We find ourselves in a situation where application running
containerized (specifically as portable services, although this issue
is general) need to either find information about the host, or alter
their behaviour depending on the host's flavour.
At the same time, applications also need to fin
On Di, 14.04.20 20:00, Amit anand (amit.ta...@gmail.com) wrote:
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x4012BD1: ???
> (in /lib/ld-2.27.so)
> Apr 03 14:40:41 [xxx] valgrind[13179]: ==13179==by 0x5BFCC8B:
> _dl_catch_exception (in /lib/libc-2.27.so)
> Apr 03 14:40:41 [xxx] va
There is no need to modify systemd.
$ systemctl disable systemd-timesyncd
That command will stop the systemd-timesyncd service from being
started. It may also be necessary to mask it:
$ systemctl mask systemd-timesyncd
On Thu, Apr 16, 2020 at 6:22 AM www wrote:
>
> Dear all，
>
> I want to ask
On Mi, 15.04.20 13:46, Tarun Chinmai Sekar (tse...@asu.edu) wrote:
> Hello Lennart,
> Thank you for the quick response. I'd love to submit a PR to increase the
> limit. Can you please point me to right parts of the code?
Look for LINK_SEARCH_DOMAINS_MAX and MANAGER_SEARCH_DOMAINS_MAX in the
sourc
Dear all，
I want to ask a question，How to modify systemd so that the NTP function is
disabled when systemd is first started?
The default state of systend is to synchronize time from NTP. We can use
timedatectl command to disable NTP synchronize time. But if I flash the system,
the NTP sync
'git grep 32' would be more effective :-)
On Wed, Apr 15, 2020 at 4:50 PM Andy Pieters wrote:
>
> On Wed, 15 Apr 2020 at 21:46, Tarun Chinmai Sekar wrote:
> >
> > Hello Lennart,
> > Thank you for the quick response. I'd love to submit a PR to increase the
> > limit. Can you please point me to r
12 matches
Mail list logo
