Hello!
Try this one:
https://www.digitalocean.com/community/tutorials/how-to-use-journalctl-to-view-and-manipulate-systemd-logs
12.05.2016 15:19, P.R.Dinesh пишет:
I would like to understand the internals of journald, how does journal
works, could you please share some links on this
On Thu, 12.05.16 17:49, P.R.Dinesh (pr.din...@gmail.com) wrote:
> I would like to understand the internals of journald, how does journal
> works, could you please share some links on this subject.
Well, there are always the sources to consult.
In case you are looking for documentation of the
Thank you for the link. But I looking for journald internals as a
developer, like how journald is implemented, its design doc etc.,
On Thu, May 12, 2016 at 6:39 PM, Mikhail Kasimov
wrote:
> Hello!
>
> Try this one:
>
On Thu, 12.05.16 11:20, Chris Friesen (cbf...@mail.usask.ca) wrote:
> Hi,
>
> Could someone point me to the commit that removed support for assigning
> "ethX" names based on MAC addresses?
>
> Alternately, can someone suggest a way to get equivalent behaviour (the
> ability to set "ethX" names
On 05/12/2016 12:50 PM, James Hogarth wrote:
>
> On 12 May 2016 18:28, "Chris Friesen" > wrote:
> >
> > Hi,
> >
> > Could someone point me to the commit that removed support for assigning
"ethX" names based on MAC addresses?
> >
> >
Am 12.05.2016 um 20:34 schrieb Chris Friesen:
So I guess the question is, how do I rename a device to a name that
already exists? (Like supposing I want to swap the names of eth0 and
eth1.)
you don't - if it works - be lucky - i am on some machines
but you can't do that relieable on many
>
> On 12 May 2016 18:28, "Chris Friesen" wrote:
> >
> > Hi,
> >
> > Could someone point me to the commit that removed support for assigning
"ethX" names based on MAC addresses?
> >
> > Alternately, can someone suggest a way to get equivalent behaviour (the
ability to set
On 2 May 2016 18:58, "James Hogarth" wrote:
>
>
> On 24 Apr 2016 21:31, "poma" wrote:
> >
> > On 20.04.2016 22:42, Chris Murphy wrote:
> > > On Wed, Apr 20, 2016 at 1:50 PM, Tobias Hunger <
tobias.hun...@gmail.com> wrote:
> >
> > [...]
> >
> >
On Thu, 12.05.16 08:15, P.R.Dinesh (pr.din...@gmail.com) wrote:
> Thank you Lennart,
> I would like to explain my system scenario.
>
> We are using systemd version 219. (Updating to 229 is in progress).
>
> Configured for persistent storage for both Journal and Coredump (Coredump
> is stored
On 05/12/2016 11:35 AM, Reindl Harald wrote:
Am 12.05.2016 um 19:20 schrieb Chris Friesen:
Could someone point me to the commit that removed support for assigning
"ethX" names based on MAC addresses?
Alternately, can someone suggest a way to get equivalent behaviour (the
ability to set
On Thu, 12.05.16 11:52, Chris Friesen (cbf...@mail.usask.ca) wrote:
> On 05/12/2016 11:35 AM, Reindl Harald wrote:
> >
> >
> >Am 12.05.2016 um 19:20 schrieb Chris Friesen:
> >>Could someone point me to the commit that removed support for assigning
> >>"ethX" names based on MAC addresses?
> >>
>
On 05/12/2016 11:36 AM, Lennart Poettering wrote:
On Thu, 12.05.16 11:20, Chris Friesen (cbf...@mail.usask.ca) wrote:
Hi,
Could someone point me to the commit that removed support for assigning
"ethX" names based on MAC addresses?
Alternately, can someone suggest a way to get equivalent
On Thu, 12.05.16 12:04, Felix Schwarz (felix.schw...@oss.schwarz.eu) wrote:
>
> Am 11.05.2016 um 21:04 schrieb Lennart Poettering:
> > However, this all implies that there's an interface for each of these
> > DNS server "routes"... if you only have a single interface, and want
> > to route on
Hi,
Could someone point me to the commit that removed support for assigning "ethX"
names based on MAC addresses?
Alternately, can someone suggest a way to get equivalent behaviour (the ability
to set "ethX" names based on MAC address) using the current infrastructure?
(Preferably as of RHEL
Am 12.05.2016 um 19:20 schrieb Chris Friesen:
Could someone point me to the commit that removed support for assigning
"ethX" names based on MAC addresses?
Alternately, can someone suggest a way to get equivalent behaviour (the
ability to set "ethX" names based on MAC address) using the
Am 12.05.2016 um 09:17 schrieb liuxueping:
Hi:
It failed when i restarted ntpd service,the log showed:ntpd[3163]:
unable to bind to wildcard address 0.0.0.0 - another process may be
running - EXITING,and the ps command result showed:
ntp 3993 0.0 0.0 0 0 ?Ds 10:21
Heya!
I am happy to let you know that the systemd.conf 2016 Call for
Participation is now open:
We’d like to invite presentation and workshop proposals for systemd.conf 2016!
The conference will consist of three parts:
One day of workshops, consisting of in-depth (2-3hr) training and
Hi:
It failed when i restarted ntpd service,the log showed:ntpd[3163]:
unable to bind to wildcard address 0.0.0.0 - another process may be
running - EXITING,and the ps command result showed:
ntp 3993 0.0 0.0 0 0 ?Ds 10:21 0:00 [ntpd]
root 3995 0.0 0.0 0
On Thu, May 12, 2016 at 1:28 AM, Luke Shumaker
wrote:
>
> The only problem I have with this setup is that dunst (my desktop
> notification daemon) isn't happy running multiple instances on
> different displays. I think it's because it isn't happy sharing the
> dbus, but I
12.05.2016 21:34, Chris Friesen пишет:
>
> So I guess the question is, how do I rename a device to a name that
> already exists? (Like supposing I want to swap the names of eth0 and
> eth1.)
>
You cannot (using current udev). This is exactly the code that was removed.
Am 12.05.2016 um 21:46 schrieb Chris Friesen:
So...anyone have any ideas why this isn't working? Is it because I'm
trying to use the "eth" namespace which could possibly collide with the
kernel naming?
likely yes
the config below has a reason while using network.service and classical
Before i restart ntpd,ntpd process was running:
ntp 3993 0.0 0.0 7404 4156 ?Ss 10:21 0:00
/usr/sbin/ntpd -u ntp:ntp -g
root 3995 0.0 0.0 7404 2364 ?S10:21 0:00
/usr/sbin/ntpd -u ntp:ntp -g
so,it should be killed by systemctl and restart a new ntpd
On Thu, 12.05.16 17:46, liuxueping (liuxuepi...@huawei.com) wrote:
> Before i restart ntpd,ntpd process was running:
> ntp 3993 0.0 0.0 7404 4156 ?Ss 10:21 0:00
> /usr/sbin/ntpd -u ntp:ntp -g
> root 3995 0.0 0.0 7404 2364 ?S10:21 0:00
>
Am 11.05.2016 um 21:04 schrieb Lennart Poettering:
> However, this all implies that there's an interface for each of these
> DNS server "routes"... if you only have a single interface, and want
> to route on that single interface to different DNS servers then, nope,
> we don't support that
Am 12.05.2016 um 11:46 schrieb liuxueping:
Before i restart ntpd,ntpd process was running:
ntp 3993 0.0 0.0 7404 4156 ?Ss 10:21 0:00
/usr/sbin/ntpd -u ntp:ntp -g
root 3995 0.0 0.0 7404 2364 ?S10:21 0:00
/usr/sbin/ntpd -u ntp:ntp -g
so,it should be
sorry ,my description is so bad,i restart ntpd using systemctl restart
ntpd command,and if it failed,the ntpd process was in D status,and it
disappear in a moment,there is no ntpd process in system.The problem was
found in arm64.
在 2016/5/12 17:51, Reindl Harald 写道:
Am 12.05.2016 um 11:46
Hi,
I have a process (ISC DHCP) that has no reload or soft restart
mechanism. The only way to "reload" it is a stop and start.
I understand systemd's design choice of maintaining a clear
distinction between reload and restart based on whether the service is
interrupted or not, so it's clear that
I would like to understand the internals of journald, how does journal
works, could you please share some links on this subject.
Thank you
Regards
Dinesh
___
systemd-devel mailing list
systemd-devel@lists.freedesktop.org
28 matches
Mail list logo