On Sun, Jun 26, 2016 at 2:27 PM, Ralf Recktenwald
wrote:
> Smb.conf:
>
>
>
> [global]
>
> workgroup = smb
>
> security = share
>
> share modes = yes
>
>
>
> [homes]
>
> comment = Home Directories
>
> browsable = no
>
> read only = no
>
> create mode = 0750
>
>
>
>
On Mon, Jun 27, 2016 at 5:34 AM, Kai Hendry wrote:
> Hi there,
>
> I had a quick look at
> https://github.com/systemd/systemd/tree/master/src/timesync to try work
> out if /usr/lib/systemd/systemd-timesyncd had some sort of fallback if
> ntp UDP port 123 traffic is
Hi there,
I had a quick look at
https://github.com/systemd/systemd/tree/master/src/timesync to try work
out if /usr/lib/systemd/systemd-timesyncd had some sort of fallback if
ntp UDP port 123 traffic is blocked.
This happens all too often with my deployments of Webconverger and I was
wondering
Am 27.06.2016 um 04:34 schrieb Kai Hendry:
I had a quick look at
https://github.com/systemd/systemd/tree/master/src/timesync to try work
out if /usr/lib/systemd/systemd-timesyncd had some sort of fallback if
ntp UDP port 123 traffic is blocked.
This happens all too often with my deployments of
On Sun, Jun 26, 2016 at 8:09 AM, Reindl Harald wrote:
> Am 26.06.2016 um 13:27 schrieb Ralf Recktenwald:
>>
>> Smb.conf
>
> how is that a systemd problem?
>
> how do you imagine help without mention distrubition, software-versions,
> cotent of the systemd-unit, systemctl
Am 26.06.2016 um 14:16 schrieb Tom H:
On Sun, Jun 26, 2016 at 8:09 AM, Reindl Harald wrote:
Am 26.06.2016 um 13:27 schrieb Ralf Recktenwald:
Smb.conf
how is that a systemd problem?
how do you imagine help without mention distrubition, software-versions,
cotent of
Am 26.06.2016 um 13:27 schrieb Ralf Recktenwald:
Smb.conf
how is that a systemd problem?
how do you imagine help without mention distrubition, software-versions,
cotent of the systemd-unit, systemctl status servicename and so on?
it's really tiresome:
Smb.conf:
[global]
workgroup = smb
security = share
share modes = yes
[homes]
comment = Home Directories
browsable = no
read only = no
create mode = 0750
[public]
path = /media/storage/
public = yes
writable = yes
comment = smb share
printable = no
guest ok = yes
26.06.2016 11:29, Michael Biebl пишет:
> 2016-06-26 7:21 GMT+02:00 Andrei Borzenkov :
>> You obviously cannot deactivate crypto container that has your root. The
>> only fix here is to exempt it from stopping on shutdown or return to
>> initramfs to do it.
>
> Would you say
2016-06-26 7:21 GMT+02:00 Andrei Borzenkov :
> You obviously cannot deactivate crypto container that has your root. The
> only fix here is to exempt it from stopping on shutdown or return to
> initramfs to do it.
Would you say it's a bug in systemd then?
--
Why is it that
10 matches
Mail list logo