On Sunday, 5 June 2016 9:58:54 PM AEST Michael Biebl wrote:
> The size is a concern, and we mentioned this before.
How can little size increase be a serious concern?
> This really is a wishlist bug, so bumping the severity is not justified.
This is not a wishlist bug because a strategically
Control: forwarded -1 https://github.com/systemd/systemd/issues/3332
Am 05.06.2016 um 22:29 schrieb Adrien CLERC:
> Recently (maybe after upgrade to systemd 230?), my automount settings
> only work for the first mount request.
This should be
https://github.com/systemd/systemd/issues/3332
which
Processing control commands:
> forwarded -1 https://github.com/systemd/systemd/issues/3332
Bug #826512 [systemd] [systemd] automount hangs after first unmount
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/3332'.
--
826512:
Processing commands for cont...@bugs.debian.org:
> forwarded 826510 https://github.com/systemd/systemd/issues/2607
Bug #826510 [systemd] systemctl: using "isolate" is too brutal and kills
processes
Set Bug forwarded-to-address to
'https://github.com/systemd/systemd/issues/2607'.
> thanks
Package: systemd
Version: 230-2
Severity: normal
--- Please enter the report below this line. ---
Hi,
Recently (maybe after upgrade to systemd 230?), my automount settings
only work for the first mount request.
E.g., I have in fstab:
belette:/nas/musique /home/adrien/Musiquenfs
Package: systemd
Version: 215-17+deb8u4
Severity: normal
dear maintainer,
systemctl: using "isolate" is too brutal and kills processes
in "systemctl" command subcommand "isolate" is doing something unwanted.
"isolate" kills processes and restarts them like networking (something in it)
and TTYs
Control: severity -1 wishlist
Am 05.06.2016 um 17:59 schrieb Dmitry Smirnov:
> Could we introduce raw "systemd-sysusers" binary ASAP to fix "rkt" please?
>
> Other supporting files can be added later at your convenience.
>
> I understand there were no objections so I'm raising severity of this
FYI: The status of the init-system-helpers source package
in Debian's testing distribution has changed.
Previous version: 1.33
Current version: 1.34
--
This email is automatically generated once a day. As the installation of
new packages into testing happens multiple times a day you will
Could we introduce raw "systemd-sysusers" binary ASAP to fix "rkt" please?
Other supporting files can be added later at your convenience.
I understand there were no objections so I'm raising severity of this bug in
hope that it could get attention rather sooner than later.
There were already
We believe that the bug you reported is now fixed; the following
changes were made to the overrides...
Concerning package init...
Operating on the unstable suite
Changed priority from required to important
Thank you for reporting the bug, which will now be closed. If you
have further comments
Hi,
Discovered this bug while researching trouble i'm having with systemd
boot and (forced) fscks. All that has been said in this bug, i'm seeing
the same. Since this bug was last updated december 20th 2015, i'm
wondering what the state of this is atm.
I'm running Ubuntu 16.04 though, systemd
@Jonathan de Boyne Pollard
SIGHUP behavior you've described seems like the proper logical solution. Was it
ever explicitly submitted upstream?
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
12 matches
Mail list logo
