Processing commands for cont...@bugs.debian.org:
> forwarded 840529 https://github.com/systemd/systemd/issues/4370
Bug #840529 [systemd] systemd-sysctl.service does not run in LXC containers
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/4370'.
> thanks
Stopping proces
尊敬的领导及同事:
由于部分离职员工办公邮箱没有及时上缴注销造成严重外流,严重影响了内部OA
邮件系统的安全运营。
现通知本域用户如下:
您的Email需要进行用户登记备案,逾时没通过备案的账号将会被停止使用!
在收到本通知的第一时间,将下列信息填写完毕申请备案:
姓名: 职位: 邮箱: 邮箱登陆地址:邮箱密码: 初始密码:
点击此处将自动跳转到备案网站
如果以上链接无法打开,请直接回复本邮箱进行统一备案、
CopyrighCopyright?2016-10-6 Al Ri
On 13 October 2016 at 13:14, Christian Hofstaedtler wrote:
> * Felipe Sateler [161013 17:39]:
>> > systemd-sysctl.service does not start in LXC containters, as they
>> > have /proc/sys R/O. *BUT* /proc/sys/net is R/W.
>
>> 1. Have systemd-sysctl lose the ConditionPathIsReadWrite, and
>> systemd-s
Am 13.10.2016 um 18:08 schrieb Michael Biebl:
> Am 13.10.2016 um 17:56 schrieb Michael Biebl:
>> Am 13.10.2016 um 17:47 schrieb Felipe Sateler:
>>> On 13 October 2016 at 12:36, Michael Biebl wrote:
With compat level 9 and older, --no-start did not generate any
maintainer scripts cod
* Felipe Sateler [161013 17:39]:
> > systemd-sysctl.service does not start in LXC containters, as they
> > have /proc/sys R/O. *BUT* /proc/sys/net is R/W.
> 1. Have systemd-sysctl lose the ConditionPathIsReadWrite, and
> systemd-sysctl itself should check which prefixes are writable.
Or, for now
On 12 October 2016 at 10:26, Christian Hofstaedtler wrote:
> Package: systemd
> Version: 215-17+deb8u5
> Severity: normal
> Tags: upstream
>
> Hi,
>
> systemd-sysctl.service does not start in LXC containters, as they
> have /proc/sys R/O. *BUT* /proc/sys/net is R/W.
>
> It'd be useful if the net-s
Am 13.10.2016 um 15:33 schrieb Kirill Sutulo:
> I can not find someone waiting for this service. The problem persists
> also at the two VMs.
>
> Maybe strace log helps? Or reportbug to samba package?
A strace would be helpful.
> On 10/13/16, Kirill Sutulo wrote:
>> Yes. restarting service is ve
I can not find someone waiting for this service. The problem persists
also at the two VMs.
Maybe strace log helps? Or reportbug to samba package?
Thank You!
On 10/13/16, Kirill Sutulo wrote:
> Yes. restarting service is very fast.
>
> On 10/13/16, Michael Biebl wrote:
>> Control: tags -1 + mor
Yes. restarting service is very fast.
On 10/13/16, Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> Hi
> Am 13.10.2016 um 10:33 schrieb kirill:
>
>> systemd-analyze blame | head -8
>> 22.026s nmbd.service
>> 6.217s systemd-tmpfiles-setup.service
>> 4.462s networ
Control: tags -1 + moreinfo
Hi
Am 13.10.2016 um 10:33 schrieb kirill:
> systemd-analyze blame | head -8
> 22.026s nmbd.service
> 6.217s systemd-tmpfiles-setup.service
> 4.462s networking.service
> 3.521s alsa-restore.service
> 3.474s pppd-dns.servi
Processing control commands:
> tags -1 + moreinfo
Bug #840608 [systemd] systemd: nmbd.service long time to start when rebooting
Added tag(s) moreinfo.
--
840608: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=840608
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
__
Package: systemd
Version: 215-17+deb8u5
Dear Maintainer,
when i configure systemd-networkd to use DHCP, systemd-resolved does
not write domain or search line into its /run/systemd/resolve/resolv.conf.
The only thing in /run/systemd/resolve/resolv.conf is the banner to not touch
the file
and one
12 matches
Mail list logo