On 27 July 2015 at 15:58, Lennart Poettering wrote:
> On Mon, 27.07.15 15:37, Felipe Sateler (fsate...@debian.org) wrote:
>
>> On 27 July 2015 at 12:36, Lennart Poettering wrote:
>> > On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote:
>> >
>> >> On Mon, 27 Jul 2015 16:51:02 +0200
On Mon, 27.07.15 15:37, Felipe Sateler (fsate...@debian.org) wrote:
> On 27 July 2015 at 12:36, Lennart Poettering wrote:
> > On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote:
> >
> >> On Mon, 27 Jul 2015 16:51:02 +0200, Lennart Poettering wrote:
> >>
> >> > Coming back to your
On 27 July 2015 at 12:36, Lennart Poettering wrote:
> On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote:
>
>> On Mon, 27 Jul 2015 16:51:02 +0200, Lennart Poettering wrote:
>>
>> > Coming back to your original question, there are two options:
>> >
>> > 1) nfs-common becomes a norma
On Mon, 27.07.15 13:25, Rich Freeman (r-syst...@thefreemanclan.net) wrote:
> On Mon, Jul 27, 2015 at 10:51 AM, Lennart Poettering
> wrote:
> >
> > If you are looking for a way to start this service only when an NFS
> > mount is attempted, then I must disappoint you: there's currently no
> > way t
On Mon, Jul 27, 2015 at 10:51 AM, Lennart Poettering
wrote:
>
> If you are looking for a way to start this service only when an NFS
> mount is attempted, then I must disappoint you: there's currently no
> way to do this nicely, as you can neither express "applies only to
> NFS", nor is there a way
On Mon, 27.07.15 15:19, Felipe Sateler (fsate...@debian.org) wrote:
> On Mon, 27 Jul 2015 16:51:02 +0200, Lennart Poettering wrote:
>
> > Coming back to your original question, there are two options:
> >
> > 1) nfs-common becomes a normal multi-user.target service, but adds
> >Before=remote-
On Mon, 27 Jul 2015 16:51:02 +0200, Lennart Poettering wrote:
> Coming back to your original question, there are two options:
>
> 1) nfs-common becomes a normal multi-user.target service, but adds
>Before=remote-fs-pre.target. This way, the service is started at
>boot, and not only on fir
On Sun, 26.07.15 00:08, Andrei Borzenkov (arvidj...@gmail.com) wrote:
> В Sat, 25 Jul 2015 12:50:39 +0200
> Michael Biebl пишет:
>
> > 2015-07-25 3:18 GMT+02:00 Rich Freeman :
> > > I noticed that mount units for nfs shares created by the generator do
> > > not Want=nfs-client.target or similar.
В Sat, 25 Jul 2015 12:50:39 +0200
Michael Biebl пишет:
> 2015-07-25 3:18 GMT+02:00 Rich Freeman :
> > I noticed that mount units for nfs shares created by the generator do
> > not Want=nfs-client.target or similar.
> >
> > That means that if you don't explicitly want nfs-client in your
> > config
2015-07-25 3:18 GMT+02:00 Rich Freeman :
> I noticed that mount units for nfs shares created by the generator do
> not Want=nfs-client.target or similar.
>
> That means that if you don't explicitly want nfs-client in your
> configuration then nfs shares will get mounted, but services like
> rpc-sta
I noticed that mount units for nfs shares created by the generator do
not Want=nfs-client.target or similar.
That means that if you don't explicitly want nfs-client in your
configuration then nfs shares will get mounted, but services like
rpc-statd-notify.service won't run.
Would it make sense to
11 matches
Mail list logo
