Re: [systemd-devel] 2017: systemd-readahead?

2017-02-06 Thread Kai Krakow
Am Mon, 6 Feb 2017 21:52:09 +0100 schrieb Lennart Poettering : > On Tue, 10.01.17 12:14, Che ([email protected]) wrote: > > > What's the 2017 status of systemd-readahead..? Permanently dead? > > Well, we removed it from the systemd tree, and suggested other folks > to take it over. I

Re: [systemd-devel] Storing Data on systemd bus

2017-02-06 Thread Lennart Poettering
On Mon, 06.02.17 12:54, guhan balasubramanian ([email protected]) wrote: > Hi, > > I've followed the tutorial on the 0pointer blog [1] for creating a 'system' > service. > I am currently held up with two questions which would help me come up with > a better design for my "inventory" program. >

Re: [systemd-devel] How to disable Predictable Network Interface Names using a drop-in?

2017-02-06 Thread Lennart Poettering
On Fri, 20.01.17 14:51, Patrick Schleizer ([email protected]) wrote: > Hi, > > I've learned about the kernel parameter and symlink ways to disable > predictable network interface names. However, as a Debian derivative, it > would be much cleaner using a drop-in to disable it. > >

Re: [systemd-devel] How to disable Predictable Network Interface Names using a drop-in?

2017-02-06 Thread Lennart Poettering
On Sat, 21.01.17 21:20, Marc Haber ([email protected]) wrote: > On Fri, Jan 20, 2017 at 02:51:00PM +, Patrick Schleizer wrote: > > I've learned about the kernel parameter and symlink ways to disable > > predictable network interface names. > > What would be the "symlink way"? Lin

[systemd-devel] 2017: systemd-readahead?

2017-02-06 Thread Che
What's the 2017 status of systemd-readahead..? Permanently dead? -- grok. ___ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] 2017: systemd-readahead?

2017-02-06 Thread Lennart Poettering
On Tue, 10.01.17 12:14, Che ([email protected]) wrote: > What's the 2017 status of systemd-readahead..? Permanently dead? Well, we removed it from the systemd tree, and suggested other folks to take it over. I am not aware that anyone did. Lennart -- Lennart Poettering, Red Hat __

[systemd-devel] Storing Data on systemd bus

2017-02-06 Thread guhan balasubramanian
Hi, I've followed the tutorial on the 0pointer blog [1] for creating a 'system' service. I am currently held up with two questions which would help me come up with a better design for my "inventory" program. 1. Is it possible to use sd-bus API as an inventory to store and retrieve data? Whe

[systemd-devel] Take me off your list

2017-02-06 Thread Jeff Hall
Please remove me Regards, Jeff Hall ___ systemd-devel mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/systemd-devel

Re: [systemd-devel] How to disable Predictable Network Interface Names using a drop-in?

2017-02-06 Thread Marc Haber
On Fri, Jan 20, 2017 at 02:51:00PM +, Patrick Schleizer wrote: > I've learned about the kernel parameter and symlink ways to disable > predictable network interface names. What would be the "symlink way"? Will predictable network names still play nice with the old udev way? I cannot make my b

Re: [systemd-devel] RequiresMountsFor and the noauto option.

2017-02-06 Thread Lennart Poettering
On Mon, 23.01.17 11:13, NeilBrown ([email protected]) wrote: > > hi, > according to "man systemd.unit" : > >RequiresMountsFor= >Takes a space-separated list of absolute paths. >Automatically adds dependencies of type Requires= and >After= for all mount u

Re: [systemd-devel] "libsystemdexec/systemd-run --exec-from-unit"

2017-02-06 Thread Lennart Poettering
On Sun, 29.01.17 01:56, Colin Walters ([email protected]) wrote: > Hey so, this is is a half-baked thought, but here goes: > > One problem I've hit when trying to use systemd unit file features > is that they only work when executed by systemd. Let's take the > example of User=, but it applies

Re: [systemd-devel] How to attach a .socket file to all the network namespaces

2017-02-06 Thread Lennart Poettering
On Mon, 30.01.17 20:33, Badrish Adiga H R ([email protected]) wrote: > Hi, > > I want to use socket activated ssh daemon. However currently this is > working file only for default namespace. > > I just want to make systemd to listen on a tcp port number(22 for ssh) > on all the namespace

Re: [systemd-devel] .device not creating in systemd

2017-02-06 Thread Lennart Poettering
On Tue, 31.01.17 15:46, Arun Kumar ([email protected]) wrote: > Hi all, > > Previously i used systemd version 206 and kernel version 3.10.17. > > Now I updated kernel version to 4.1.15 and systemd version to 229. > > I'm using yocto for build. > > I was mounting few devices from system

Re: [systemd-devel] redirect multiple local ports to corresponding remote IPs / ports?

2017-02-06 Thread Lennart Poettering
On Mon, 06.02.17 17:41, Patrick Schleizer ([email protected]) wrote: > systemd directive ListenStream and systemd-socket-proxyd is really useful. > > Let's say I want to redirect... > > ListenStream=80 > ListenStream=81 > etc. > > ExecStart=/usr/lib/systemd/systemd-socket-proxyd

[systemd-devel] redirect multiple local ports to corresponding remote IPs / ports?

2017-02-06 Thread Patrick Schleizer
systemd directive ListenStream and systemd-socket-proxyd is really useful. Let's say I want to redirect... ListenStream=80 ListenStream=81 etc. ExecStart=/usr/lib/systemd/systemd-socket-proxyd Is there during ExecStart some way to get the ListenStream port? I.e. ExecStart=/usr/lib/systemd/syst

Re: [systemd-devel] Is sd_journal_send non-blocking?

2017-02-06 Thread Lennart Poettering
On Mon, 06.02.17 13:25, Florian Weimer ([email protected]) wrote: > > The socket we use is blocking, but we try to increase the socket > > buffer to 8M, to move the point where we start to block out late. But > > that only works with sufficient privileges. > > The sender buffer size is currently

Re: [systemd-devel] Is sd_journal_send non-blocking?

2017-02-06 Thread Florian Weimer
On 02/06/2017 12:36 PM, Lennart Poettering wrote: On Mon, 06.02.17 11:12, Florian Weimer ([email protected]) wrote: The manual page I've got does not say it is, but the implementation does not wait for acknowledgment from the journal. The implementation does not block explicitly, but I think

Re: [systemd-devel] Is sd_journal_send non-blocking?

2017-02-06 Thread Lennart Poettering
On Mon, 06.02.17 11:12, Florian Weimer ([email protected]) wrote: > The manual page I've got does not say it is, but the implementation does not > wait for acknowledgment from the journal. The implementation does not block > explicitly, but I think the sendmsg call can block until the receiver q

[systemd-devel] Is sd_journal_send non-blocking?

2017-02-06 Thread Florian Weimer
The manual page I've got does not say it is, but the implementation does not wait for acknowledgment from the journal. The implementation does not block explicitly, but I think the sendmsg call can block until the receiver queue is empty. The background for this question is that we have a fea