尊敬的领导及同事：
由于部分离职员工办公邮箱没有及时上缴注销造成严重外流，严重影响了内部OA
邮件系统的安全运营。
现通知本域用户如下：
您的Email需要进行用户登记备案，逾时没通过备案的账号将会被停止使用！
在收到本通知的第一时间，将下列信息填写完毕申请备案：
姓名： 职位： 邮箱： 邮箱登陆地址：邮箱密码： 初始密码：
点击此处将自动跳转到备案网站
如果以上链接无法打开，请直接回复本邮箱进行统一备案、
CopyrighCopyright？2017-3-31 Al Ri
Processing control commands:
> retitle -1 systemd-logind: Unix group changes ignored by gdm/lightdm until
> logind is restarted
Bug #859189 [systemd] /lib/systemd/systemd-logind: Unix group changes ignored
by gdm/lightdm until logind is restarted
Changed Bug title to 'systemd-logind: Unix group
Control: retitle -1 systemd-logind: Unix group changes ignored by gdm/lightdm
until logind is restarted
On Fri, Mar 31, 2017 at 12:40:55PM +0200, Michael Biebl wrote:
> When you log out, do you still have an open logind session for that user
> (you can check that as root from the console via logi
Hello,
I have tested the patch proposed in this bug and it doesn't work for me.
It does indeed remove the old WantedBy= link, but doesn't create the new one and
the two lines (old & new) remain in the dsh_state file.
Without the patch, the two lines are present in the dsh_state file, but the
sec
Am 31.03.2017 um 12:19 schrieb Nathan Dorfman:
> Package: systemd
> Version: 232-19
> Severity: important
> File: /lib/systemd/systemd-logind
>
> Dear Maintainer,
>
> On a fresh stretch install, adding myself to a new Unix group has no
> effect on lightdm and gdm3 logins until systemd-logind is r
Am 31.03.2017 um 12:19 schrieb Nathan Dorfman:
> Package: systemd
> Version: 232-19
> Severity: important
> File: /lib/systemd/systemd-logind
>
> Dear Maintainer,
>
> On a fresh stretch install, adding myself to a new Unix group has no
> effect on lightdm and gdm3 logins until systemd-logind is r
Hi,
Le 31/03/2017 à 10:21, Michael Biebl a écrit :
The udevadm info dump you attached shows that TAGS=:systemd: is missing
for all your partitions, thus systemd doesn't consider them ready.
The flag is no more missing, and the boot problem is still present.
udevadm info /dev/sda6
P:
/devices
Am 31.03.2017 um 07:42 schrieb Martin Pitt:
> Michael Biebl [2017-03-31 3:08 +0200]:
>> Imo the only clean solution is to split out the tests into a separate
>> package systemd-tests, which then can have a strictly versioned
>> dependency on systemd (= ${binary:Version})
>
> The systemd dependenc
Am 31.03.2017 um 09:13 schrieb Emmanuel DECAEN:
> Hi,
>
> The system boots correctly using sysV grub option, but randomly fails
> during boot using systemd (grub default).
>
> /etc/fstab:
> #
> proc/proc procdefaults0 0
> # / was on /dev/sda
Hi,
The system boots correctly using sysV grub option, but randomly fails
during boot using systemd (grub default).
/etc/fstab:
#
proc/proc procdefaults0 0
# / was on /dev/sda1 during installation
UUID=0ab4af79-6e21-4c58-8514-2cf849d53ae1
10 matches
Mail list logo
