Package: systemd-cron
Version: 1.3.1+ds1-1
Severity: minor
Generally, crontabs are only visible by the owner.
After #766053 gets fixed, the issue still remains in the sense that the
generated units/timers (coming from crontabs) have root:root 644 permissions,
which are readable by everyone.
The current status of /var/spool/cron/crontabs is undetermined ...
users either inherit what was setup up by the previosu cron daemon or
get a vanilla 0755 folder
on fresh install.
e.g.: http://anonscm.debian.org/cgit/pkg-cron/pkg-cron.git/tree/debian/postinst
Having crontab translate on the fly
On 11/03/2014 12:43 PM, Alexandre Detiste wrote:
The current status of /var/spool/cron/crontabs is undetermined ...
users either inherit what was setup up by the previosu cron daemon or
get a vanilla 0755 folder
on fresh install.
e.g.:
On 11/03/2014 12:48 PM, Yuri D'Elia wrote:
e.g.:
http://anonscm.debian.org/cgit/pkg-cron/pkg-cron.git/tree/debian/postinst
Having crontab translate on the fly user crontabs into ~/.config/systemd/user
service timers (systemd --user) would avoid all these security problems.
This need a
It seems like it is unable to mount a zfs volume given in fstab during boot.
Strangely the presence of such an entry in fstab also seems to cause the
password entry problem. With no zfs in fstab I can enter the passwords and the
zfs volumes with non legacy mount points mount ok.
It sounds like
Am 03.11.2014 um 15:06 schrieb John Holland:
It seems like it is unable to mount a zfs volume given in fstab during boot.
Strangely the presence of such an entry in fstab also seems to cause the
password entry problem. With no zfs in fstab I can enter the passwords and
the zfs volumes with
#
# bts-link upstream status pull for source package systemd
# see http://lists.debian.org/debian-devel-announce/2006/05/msg1.html
#
user bts-link-upstr...@lists.alioth.debian.org
# remote status report for #766413 (http://bugs.debian.org/766413)
# Bug title: /lib/systemd/systemd-resolved:
Processing commands for cont...@bugs.debian.org:
found 767951 1.3.1+ds1-2
Bug #767951 [systemd-cron] systemd-cron: crontab -r user will remove root
crontab
Marked as found in versions systemd-cron/1.3.1+ds1-2.
thanks
Stopping processing here.
Please contact me if you need assistance.
--
Processing commands for cont...@bugs.debian.org:
notfound 767951 1.3.4-1
Bug #767951 [systemd-cron] systemd-cron: crontab -r user will remove root
crontab
There is no source info for the package 'systemd-cron' at version '1.3.4-1'
with architecture ''
Unable to make a source version for
FYI: The status of the systemd-cron source package
in Debian's testing distribution has changed.
Previous version: 1.3.1+ds1-1
Current version: 1.3.1+ds1-2
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day
Hello,
Am Samstag, den 11. Oktober schrieb Michael Biebl:
could you please remove your local service file again, add
systemd.log_level=debug to the kernel command line, enable verbose udev
debug logging via /etc/udev/udev.conf and then after a reboot, attach
the output of
journalctl -alb
My
Am 18.10.2014 um 21:49 schrieb John Goerzen:
Package: systemd
Version: 215-5+b1
Severity: grave
Justification: renders package unusable
On investigating why my 8GB system, which was suddenly running extremely
slow and maxed out on swap, I discovered numerous systemd-logind
processes
This is indeed an accurate summary.
One more data point - I rebooted without that change, and the problem
indeed persists. I will try with it, but it will take a bit of work to
make it ready. Give me a day or two.
John
___
Pkg-systemd-maintainers
On Mon, Nov 03, 2014 at 03:36:49PM +0100, Michael Biebl wrote:
http://changelog.complete.org/archives/9241-update-on-the-systemd-issue
might be relevant for you.
Yeah, this might be relevant. When I read that ZFS has init scripts
with carefully-planned dependencies, I shudder. They clearly have
14 matches
Mail list logo
