Re: [systemd-devel] Antw: [EXT] Re: [dm-devel] RFC: one more time: SCSI device identification

2021-05-04 Thread Hannes Reinecke
On 4/27/21 12:52 PM, Ulrich Windl wrote: Hannes Reinecke schrieb am 27.04.2021 um 10:21 in Nachricht <2a6903e4-ff2b-67d5-e772-6971db844...@suse.de>: On 4/27/21 10:10 AM, Martin Wilck wrote: On Tue, 2021‑04‑27 at 13:48 +1000, Erwin van Londen wrote: Wrt 1), we can only hope tha

Re: [systemd-devel] [dm-devel] RFC: one more time: SCSI device identification

2021-04-27 Thread Hannes Reinecke
g. But actually I like the idea from Martin Petersen to expose the parsed VPD identifiers to sysfs; that would allow us to drop sg_inq completely from the udev rules. Cheers, Hannes -- Dr. Hannes Reinecke Kernel Storage Architect h...@suse.de

Re: [systemd-devel] [PATCH] md: Drop sending a change uevent when stopping

2016-02-17 Thread Hannes Reinecke
nt when it becomes inactive. (Would be pretty pointless, too, as what exactly is one supposed to do here?) The current usage has it that CHANGE events are only ever sent if a device becomes active. Cheers, Hannes - -- Dr. Hannes ReineckeTeamlead Storage & Networking h...@suse.de

Re: [systemd-devel] [PATCH 2/2] Manage: Inform udev about device removal when stopping

2016-02-16 Thread Hannes Reinecke
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 02/16/2016 09:46 PM, NeilBrown wrote: > On Wed, Feb 17 2016, Jes Sorensen wrote: > >> Hannes Reinecke <h...@suse.de> writes: >>> On 02/16/2016 07:03 PM, Sebastian Parschauer wrote: >>>> On 16.02.2016 18:

Re: [systemd-devel] [PATCH 2/2] Manage: Inform udev about device removal when stopping

2016-02-16 Thread Hannes Reinecke
e 'OFFLINE' got dropped completely. Or that was the plan. So it looks as if the conversion to 'CHANGE' got applied to the 'OFFLINE' event, too. Hence I strongly recommend to drop it completely, and let the kernel or the MD module decide if and when a uevent should be send. Cheers, Hannes -- Dr. Hannes

[systemd-devel] [PATCH 0/2] Scalability fixes for large machines

2015-03-04 Thread Hannes Reinecke
as it will just silently drop events on the floor. AFAICS both caps are totally arbitrary, so I've removed the cap on the number of epoll events and raise the number of concurrent dbus connections to 4096. Hannes Reinecke (2): Remove the cap on epoll events Allow up to 4096 simultaneous connections src

[systemd-devel] [PATCH 1/2] Remove the cap on epoll events

2015-03-04 Thread Hannes Reinecke
Currently the code will silently blank out events if there are more then 512 epoll events, causing them never to be handled at all. This patch removes the cap on the number of events for epoll_wait, thereby avoiding this issue. Signed-off-by: Hannes Reinecke h...@suse.de --- src/libsystemd/sd

[systemd-devel] [PATCH 1/2] Remove the cap on epoll events

2015-03-04 Thread Hannes Reinecke
Currently the code will silently blank out events if there are more then 512 epoll events, causing them never to be handled at all. This patch removes the cap on the number of events for epoll_wait, thereby avoiding this issue. Signed-off-by: Hannes Reinecke h...@suse.de --- src/libsystemd/sd

[systemd-devel] [PATCH 2/2] Allow up to 4096 simultaneous connections

2015-03-04 Thread Hannes Reinecke
On large system we hit the limit on 512 simultaneous dbus connections, resulting in tons of annoying messages: Too many concurrent connections, refusing This patch raises the limit to 4096. Signed-off-by: Hannes Reinecke h...@suse.de --- src/core/dbus.c | 2 +- 1 file changed, 1 insertion

[systemd-devel] [PATCH 2/2] Allow up to 4096 simultaneous connections

2015-03-04 Thread Hannes Reinecke
On large system we hit the limit on 512 simultaneous dbus connections, resulting in tons of annoying messages: Too many concurrent connections, refusing This patch raises the limit to 4096. Signed-off-by: Hannes Reinecke h...@suse.de --- src/core/dbus.c | 2 +- 1 file changed, 1 insertion

[systemd-devel] [PATCHv2 0/2] Scalability fixes for large machines

2015-03-04 Thread Hannes Reinecke
as it will just silently drop events on the floor. AFAICS both caps are totally arbitrary, so I've removed the cap on the number of epoll events and raise the number of concurrent dbus connections to 4096. Changes to v1: - Fix typo in the first patch Hannes Reinecke (2): Remove the cap on epoll events

Re: [systemd-devel] [dm-devel] multipath breaks with recent udev/systemd

2014-12-18 Thread Hannes Reinecke
On 12/18/2014 11:04 PM, Benjamin Marzinski wrote: On Wed, Dec 17, 2014 at 01:04:54PM +0100, Hannes Reinecke wrote: On 12/16/2014 11:18 PM, Benjamin Marzinski wrote: On Tue, Dec 16, 2014 at 04:10:44PM -0600, Benjamin Marzinski wrote: On Mon, Dec 15, 2014 at 10:31:44AM +0100, Hannes Reinecke

Re: [systemd-devel] [dm-devel] multipath breaks with recent udev/systemd

2014-12-17 Thread Hannes Reinecke
On 12/16/2014 11:18 PM, Benjamin Marzinski wrote: On Tue, Dec 16, 2014 at 04:10:44PM -0600, Benjamin Marzinski wrote: On Mon, Dec 15, 2014 at 10:31:44AM +0100, Hannes Reinecke wrote: [ .. ] So during bootup it's anyone's guess who's first, multipath or udev. And depending on the timing either

[systemd-devel] multipath breaks with recent udev/systemd

2014-12-15 Thread Hannes Reinecke
it rather be retried? What is the supposed recovery here? Cheers, Hannes -- Dr. Hannes ReineckezSeries Storage h...@suse.de +49 911 74053 688 SUSE LINUX GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: F. Imendörffer, J. Smithard, J. Guild, D

Re: [systemd-devel] [PATCH] udevd: add --event-timeout commandline option

2014-07-30 Thread Hannes Reinecke
On 07/29/2014 04:13 PM, Kay Sievers wrote: On Tue, Jul 29, 2014 at 9:06 AM, Hannes Reinecke h...@suse.de wrote: On large configurations some events take longer than the default 30 seconds. Killing those events will leave the machine halfway configured. So add a commandline option '--event

[systemd-devel] [PATCH] Fixup commit dd5eddd28a74a49607a8fffcaf960040dba98479

2014-07-30 Thread Hannes Reinecke
Commit dd5eddd28a74a49607a8fffcaf960040dba98479 accidentally removed one line too many. Signed-off-by: Hannes Reinecke h...@suse.de --- src/udev/udev-rules.c | 1 + 1 file changed, 1 insertion(+) diff --git a/src/udev/udev-rules.c b/src/udev/udev-rules.c index 59bc124..cc56215 100644 --- a/src

[systemd-devel] [PATCHv3] use systemd.debug on the kernel command line, not debug

2014-04-03 Thread Hannes Reinecke
, and the opposite as well so make everyone happy. Signed-off-by: Greg KH gre...@linuxfoundation.org Signed-off-by: Hannes Reinecke h...@suse.de --- man/kernel-command-line.xml | 4 ++-- src/core/main.c | 19 ++- 2 files changed, 12 insertions(+), 11 deletions(-) diff --git a/man

Re: [systemd-devel] [PATCHv3] use systemd.debug on the kernel command line, not debug

2014-04-03 Thread Hannes Reinecke
On 04/03/2014 01:02 PM, Colin Guthrie wrote: 'Twas brillig, and Hannes Reinecke at 03/04/14 07:52 did gyre and gimble: systemd.restore_state=0|1 Restore backlight/rfkill state at boot\n); + systemd.debug

[systemd-devel] [PATCH v4] use systemd.debug on the kernel command line, not debug

2014-04-03 Thread Hannes Reinecke
, and the opposite as well so make everyone happy. Signed-off-by: Greg KH gre...@linuxfoundation.org Signed-off-by: Hannes Reinecke h...@suse.de --- man/kernel-command-line.xml | 4 ++-- src/core/main.c | 21 +++-- 2 files changed, 13 insertions(+), 12 deletions(-) diff --git a/man

Re: [systemd-devel] [PATCHv3] use systemd.debug on the kernel command line, not debug

2014-04-03 Thread Hannes Reinecke
On 04/03/2014 05:17 PM, Greg KH wrote: On Thu, Apr 03, 2014 at 08:52:06AM +0200, Hannes Reinecke wrote: From: Greg KH gre...@linuxfoundation.org If the kernel is started with debug, that's for the kernel to switch into debug mode. We should rely on a namespace for our options, like

[systemd-devel] [PATCH] systemd: powerd initctl support

2014-03-07 Thread Hannes Reinecke
Old versions of powerd will be using the initctl fifo to signal state changes. To maintain backward compability systemd should be interpreting these messages, too. Signed-off-by: Hannes Reinecke h...@suse.de --- src/initctl/initctl.c | 71 ++- 1

[systemd-devel] [PATCHv3] tty: Set correct tty name in 'active' sysfs attribute

2014-02-07 Thread Hannes Reinecke
', not the console names. Cc: Lennart Poettering lenn...@poettering.net Cc: Kay Sievers k...@vrfy.org Cc: Greg Kroah-Hartmann gre...@linuxfoundation.org Cc: Jiri Slaby jsl...@suse.cz Cc: David Herrmann dh.herrm...@gmail.com Signed-off-by: Werner Fink wer...@suse.de Signed-off-by: Hannes Reinecke h

Re: [systemd-devel] [PATCH] tty: Set correct tty name in 'active' sysfs attribute

2014-02-06 Thread Hannes Reinecke
On 02/05/2014 01:53 PM, David Herrmann wrote: Hi On Wed, Feb 5, 2014 at 11:11 AM, Hannes Reinecke h...@suse.de wrote: The 'active' sysfs attribute should refer to the currently active tty devices the console is running on, not the currently active console. The console structure doesn't

Re: [systemd-devel] [PATCHv2] tty: Set correct tty name in 'active' sysfs attribute

2014-02-06 Thread Hannes Reinecke
On 02/06/2014 04:29 PM, Greg Kroah-Hartman wrote: On Thu, Feb 06, 2014 at 03:27:43PM +0100, Hannes Reinecke wrote: The 'active' sysfs attribute should refer to the currently active tty devices the console is running on, not the currently active console. That's not what Documentation/ABI

[systemd-devel] [PATCH] tty: Set correct tty name in 'active' sysfs attribute

2014-02-05 Thread Hannes Reinecke
', not the console names. Cc: Lennart Poettering lenn...@poettering.net Cc: Kay Sievers k...@vrfy.org Signed-off-by: Werner Fink wer...@suse.de Signed-off-by: Hannes Reinecke h...@suse.de --- drivers/tty/tty_io.c | 14 -- 1 file changed, 12 insertions(+), 2 deletions(-) diff --git a/drivers

Re: [systemd-devel] [PATCH] s390/getty-generator: initialize essential system terminals/consoles

2014-02-03 Thread Hannes Reinecke
the driver to adhere to the (broken) current behaviour? Or modify 'active' to return the corrent tty name? Or add a workaround to systemd? Cheers, Hannes -- Dr. Hannes Reinecke zSeries Storage h...@suse.de +49 911 74053 688 SUSE LINUX Products GmbH

Re: [systemd-devel] udev rules environment variable

2013-12-17 Thread Hannes Reinecke
On 12/17/2013 11:52 AM, Kay Sievers wrote: On Tue, Dec 17, 2013 at 8:56 AM, Hannes Reinecke h...@suse.de wrote: On 12/17/2013 08:52 AM, Robert Milasan wrote: Hello, got a small question about creating a rule, like this: ACTION==add, , ENV{test_device}=1 ACTION==remove, , ENV

Re: [systemd-devel] udev rules environment variable

2013-12-16 Thread Hannes Reinecke
, Hannes -- Dr. Hannes Reinecke zSeries Storage h...@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg) ___ systemd

Re: [systemd-devel] Question about a udev rule

2013-12-08 Thread Hannes Reinecke
, Hannes -- Dr. Hannes Reinecke zSeries Storage h...@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg) ___ systemd

[systemd-devel] Hard-coded /bin/mount in systemd

2013-11-27 Thread Hannes Reinecke
-- Dr. Hannes Reinecke zSeries Storage h...@suse.de +49 911 74053 688 SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg GF: J. Hawn, J. Guild, F. Imendörffer, HRB 16746 (AG Nürnberg) ___ systemd-devel mailing

Re: [systemd-devel] Hard-coded /bin/mount in systemd

2013-11-27 Thread Hannes Reinecke
On 11/27/2013 02:58 PM, Mantas Mikulėnas wrote: On Wed, Nov 27, 2013 at 3:31 PM, Hannes Reinecke h...@suse.de wrote: Hi all, for some reason systemd has /bin/mount hardcoded in src/core/mount.c:mount_enter_mounting() Which is a bit odd, seeing that everyting moved to /usr/bin. So we