This has probably nothing to do with systemd! CEPH finds his osd devices
automatically via udev somewhere here:
/usr/lib/udev/rules.d/95-ceph-osd.rules.
Did you ever try to manually activate the disks like in the rules? Should be
something like:
for o in {0..3}; do
i="\`echo \$o | tr 01234
Am 09.12.2015 um 11:03 schrieb Joachim von Thadden:
This has probably nothing to do with systemd! CEPH finds his osd devices
automatically via udev somewhere here:
/usr/lib/udev/rules.d/95-ceph-osd.rules.
Did you ever try to manually activate the disks like in the rules? Should be
something l
Hi,
I have created a systemd.unit(nfs-ganesha.service) file as below :
[Unit]
After=nfs-ganesha-config.service
Requires=nfs-ganesha-config.service
[Service]
EnvironmentFile=-/run/sysconfig/ganesha
ExecStart=/usr/bin/ganesha.nfsd $OPTIONS ${EPOCH}
...
My intention is to exe
On Wed, Dec 09, 2015 at 08:43:05AM +0200, Panu Matilainen wrote:
> On 12/08/2015 01:47 PM, Greg KH wrote:
> >On Tue, Dec 08, 2015 at 11:34:36AM +0200, Panu Matilainen wrote:
> >>>As was mentioned recently PCI bus numbers may change between reboots, so
> >>
> >>Hmm, got a pointer? I dont think PCI s
On 12/09/2015 04:26 PM, Greg KH wrote:
On Wed, Dec 09, 2015 at 08:43:05AM +0200, Panu Matilainen wrote:
On 12/08/2015 01:47 PM, Greg KH wrote:
On Tue, Dec 08, 2015 at 11:34:36AM +0200, Panu Matilainen wrote:
As was mentioned recently PCI bus numbers may change between reboots, so
Hmm, got a
On Tue, 08.12.15 19:35, Andrea Annoè (andrea.an...@iks.it) wrote:
> Hi,
> I try to test ceph 9.2 cluster.
I have no idea about ceph, and I don't really grok what the problem is
supposed to be, but I really looks like it's a Ceph problem. Please
contact the ceph folks for help.
Lennart
--
Lenna
On Wed, 09.12.15 18:27, Soumya Koduri (skod...@redhat.com) wrote:
> Hi,
>
> I have created a systemd.unit(nfs-ganesha.service) file as below :
>
> [Unit]
>
> After=nfs-ganesha-config.service
> Requires=nfs-ganesha-config.service
>
>
> [Service]
> EnvironmentFile=-/run/sysconfig/ganesha
>
Hello,
I've had problems getting systemd-logind to respect shutdown inhibitors when
I ask it over DBus to power off or reboot.
Here is what I've tried:
In one gnome-terminal as non-root, I type:
systemd-inhibit --what=shutdown --mode=block --who=unison unison-gtk2
...to set up the inhibitor.
T
On Wed, Dec 9, 2015 at 10:20 PM, Troels Mæhl Folke <
t.r.o.e.l.s@gmail.com> wrote:
> Hello,
>
> I've had problems getting systemd-logind to respect shutdown inhibitors
> when
> I ask it over DBus to power off or reboot.
>
> Here is what I've tried:
>
> In one gnome-terminal as non-root, I type
Am 09.12.2015 um 20:46 schrieb Lennart Poettering:
I probably should never have added EnvironmentFile= in the first
place. Packagers misunderstand that unit files are subject to admin
configuration and should be treated as such, and that spliting out
configuration of unit files into separate En
10.12.2015 03:08, Reindl Harald пишет:
>
>
> Am 09.12.2015 um 20:46 schrieb Lennart Poettering:
>> I probably should never have added EnvironmentFile= in the first
>> place. Packagers misunderstand that unit files are subject to admin
>> configuration and should be treated as such, and that split
On 12/10/2015 01:16 AM, Lennart Poettering wrote:
On Wed, 09.12.15 18:27, Soumya Koduri (skod...@redhat.com) wrote:
Hi,
I have created a systemd.unit(nfs-ganesha.service) file as below :
[Unit]
After=nfs-ganesha-config.service
Requires=nfs-ganesha-config.service
[Service]
Environment
12 matches
Mail list logo
