On Wed, Dec 17, 2014 at 08:04:38PM +0100, Lennart Poettering wrote:
This is important details, because if you use epoll file descriptor
in another epoll then you're correctly notified on the top-level epoll,
but you lost information about which underneath file descriptor is active
--
On Fri, Dec 12, 2014 at 08:11:54PM +0100, Lennart Poettering wrote:
I guess it's enough to add the 'fd' to systmed sd_event_add_io() and
call mnt_table_parse_mtab() when a change is detected. (As already
implemeted in the original Chris' patch.)
Karel, if I got this right, then the new
On Wed, 17.12.14 13:13, Karel Zak (k...@redhat.com) wrote:
On Fri, Dec 12, 2014 at 08:11:54PM +0100, Lennart Poettering wrote:
I guess it's enough to add the 'fd' to systmed sd_event_add_io() and
call mnt_table_parse_mtab() when a change is detected. (As already
implemeted in the
On Fri, 05.12.14 15:54, Karel Zak (k...@redhat.com) wrote:
I have added struct libmnt_monitor to make this new interface easy to
extend and usable for more resources (I'll probably also add mountinfo
fd for findmnt(8), but this is irrelevant for systemd;-)
All you need is:
mn =
On Fri, Dec 12, 2014 at 08:11:54PM +0100, Lennart Poettering wrote:
On Fri, 05.12.14 15:54, Karel Zak (k...@redhat.com) wrote:
I guess it's enough to add the 'fd' to systmed sd_event_add_io() and
call mnt_table_parse_mtab() when a change is detected. (As already
implemeted in the original
On Wed, Dec 10, 2014 at 01:53:09AM +0100, Lennart Poettering wrote:
On Tue, 09.12.14 12:30, Karel Zak (k...@redhat.com) wrote:
On Mon, Dec 08, 2014 at 08:10:08PM +0100, Lennart Poettering wrote:
Any idea when you intend to realease this new API in a release or even
in a stable one?
On Mon, Dec 08, 2014 at 08:10:08PM +0100, Lennart Poettering wrote:
Any idea when you intend to realease this new API in a release or even
in a stable one?
I'd like to have v2.26-rc1 this month.
Karel
--
Karel Zak k...@redhat.com
http://karelzak.blogspot.com
On Tue, 09.12.14 12:30, Karel Zak (k...@redhat.com) wrote:
On Mon, Dec 08, 2014 at 08:10:08PM +0100, Lennart Poettering wrote:
Any idea when you intend to realease this new API in a release or even
in a stable one?
I'd like to have v2.26-rc1 this month.
Hmm, OK, then I'll release 218
On Fri, 05.12.14 15:54, Karel Zak (k...@redhat.com) wrote:
On Fri, Dec 05, 2014 at 01:46:06AM +0100, Lennart Poettering wrote:
With such an API you have the liberty to change later on what
precisely you expose there. The fact that you watch a file would be
entirely opaque, it could one day
On Fri, Dec 05, 2014 at 01:46:06AM +0100, Lennart Poettering wrote:
With such an API you have the liberty to change later on what
precisely you expose there. The fact that you watch a file would be
entirely opaque, it could one day be a pipe or socket, or even an fd
on some kernel fd, where
On Mon, 01.12.14 16:47, Karel Zak (k...@redhat.com) wrote:
On Mon, Dec 01, 2014 at 02:28:33PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
Wouldn't be enough to use Chris' iSCSI and FCoE auto detection?
Please see previous discussion... Detecting network might not be trivial
if the devices
On Sun, 23.11.14 20:33, Chris Leech (cle...@redhat.com) wrote:
This adds auto detection for iSCSI and some FCoE drivers and treats
mounts to file-systems on those devices as remote-fs.
Hmm, I am not too fond of having such subsystem-specific complexity in
systemd.
Hmm, isn't this something
On Fri, Nov 28, 2014 at 09:27:43PM +0100, Lennart Poettering wrote:
On Fri, 28.11.14 20:50, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Sun, Nov 23, 2014 at 08:33:41PM -0800, Chris Leech wrote:
This adds auto detection for iSCSI and some FCoE drivers and treats
mounts to
On Mon, Dec 01, 2014 at 11:24:58AM +0100, Karel Zak wrote:
On Fri, Nov 28, 2014 at 09:27:43PM +0100, Lennart Poettering wrote:
On Fri, 28.11.14 20:50, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl)
wrote:
On Sun, Nov 23, 2014 at 08:33:41PM -0800, Chris Leech wrote:
This adds auto
On Mon, Dec 01, 2014 at 02:28:33PM +0100, Zbigniew Jędrzejewski-Szmek wrote:
Wouldn't be enough to use Chris' iSCSI and FCoE auto detection?
Please see previous discussion... Detecting network might not be trivial
if the devices are layered and there's a network-requiring device somewhere
On Fri, 28.11.14 20:50, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Sun, Nov 23, 2014 at 08:33:41PM -0800, Chris Leech wrote:
This adds auto detection for iSCSI and some FCoE drivers and treats
mounts to file-systems on those devices as remote-fs.
Signed-off-by: Chris
On Fri, Nov 28, 2014 at 09:27:43PM +0100, Lennart Poettering wrote:
On Fri, 28.11.14 20:50, Zbigniew Jędrzejewski-Szmek (zbys...@in.waw.pl) wrote:
On Sun, Nov 23, 2014 at 08:33:41PM -0800, Chris Leech wrote:
This adds auto detection for iSCSI and some FCoE drivers and treats
mounts to
This adds auto detection for iSCSI and some FCoE drivers and treats
mounts to file-systems on those devices as remote-fs.
Signed-off-by: Chris Leech cle...@redhat.com
---
src/core/mount.c | 168 +++
1 file changed, 158 insertions(+), 10
18 matches
Mail list logo
