Debian binary package.
> Is this intentional or an omission?
> Could it be possible to enable fq_codel by default?
>
Changelog has this by Marco d'Itri:
> * Do not install sysctl.d/50-default.conf because the systemd package
>should not change kernel policies, at lea
luster --skip-systemctl-redirect %i start
If postgres would report the error back to systemd, it would at least
tell you that.
getty@.service suffers from the same issue. Other units do not:
% sudo systemctl start systemd-nspawn@does-not-exist
Job for systemd-nspawn@does-not-exist.service fa
works, and post the output?
apt install systemd:amd64=238-2
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
Package: systemd
Version: 215-7
Severity: minor
The tmpfiles snippets set the /run/log/journal directory owned to
root:systemd-journal, but it does not add a read acl for the adm group
as README.Debian suggests. I'm not sure tmpfiles can add ACLs, if so,
debian should probably add that ACL.
-- Pa
Hi,
On 4 Dec 2014 02:16, "Michael Biebl" wrote:
>
> Am 04.12.2014 um 04:38 schrieb Felipe Sateler:
> > Package: systemd
> > Version: 215-7
> > Severity: minor
> >
> > The tmpfiles snippets set the /run/log/journal directory owned to
> > root
Control: tags -1 = upstream confirmed
Control: forwarded -1 https://bugs.freedesktop.org/show_bug.cgi?id=87020
On Wed, 15 Oct 2014 22:39:35 -0400 Dominique Brazziel
wrote:
> Package: systemd
> Version: 215-5+b1
> Severity: minor
> Tags: patch
>
> The man page refers to the 'dump' function of
Package: systemd
Version: 215-7
Severity: important
When gdm and kdm are installed, and kdm selected as default display
manager, the system cannot boot correctly. Only sometimes kdm manages
to launch. getty fails to launch as well, I think because it is
waiting for plymouth-wait-quit that never en
On Wed, Dec 10, 2014 at 12:28 PM, Matthias Klumpp wrote:
> 2014-12-10 15:51 GMT+01:00 Felipe Sateler :
>> [...]
>> Other information that may be relevant:
>>
>> When installing gdm3, the following message is displayed:
>> Setting up gdm3 (3.14.1-3) ...
>> W
On Mon, 05 Jan 2015 20:57:05 +0100 Christian Kastner wrote:
>
> If this second PAM session via systemd-user is indeed intended to be
> merely a background thing, them common-session-noninteractive should be
> the way to go anyway. But I'm not familiar enough with systemd to make
> that call.
For
Package: systemd
Version: 219-8
Severity: wishlist
nss-mymachines is quite useful. It would be great to have it enabled.
-- Package-specific info:
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x
On Fri, 06 Feb 2015 19:16:30 +0100 Michael Biebl wrote:
> Hi,
>
> Am 06.02.2015 um 16:42 schrieb Aaron M. Ucko:
> > Package: systemd
> > Version: 215-10
> > Severity: normal
> >
> > On systems with a separate /usr filesystem, /dev entries listed in
> > /usr/lib/tmpfiles.d/*.conf will fall through
Control: tags -1 moreinfo
On Sat, 30 Aug 2014 20:56:15 -0700 Raphael Geissert wrote:
> Source: systemd
> Source-Version: 208-8
> Tags: security
>
> Hi,
>
> At some point between squeeze and wheezy initscript started initialising the
> RANDOM_SEED file in its postinst by basically doing the equiva
t; poweroff or shutdown -h now:
> https://www.debian.org/releases/jessie/i386/ch08s01.html.en
This doesn't look good, though, as halt is almost never what you want.
Reassigning to the release notes.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-ma
, and some should be moved into some user
documentation (eg, overriding units). This page is also missing info
on the socket stop on upgrade issue.
[1] https://wiki.debian.org/Teams/pkg-systemd
[2] https://wiki.debian.org/Teams/pkg-systemd/Bugs
--
Saludos,
Feli
kages with systemd units should
be using) respects it. That should probably solve your problem.
[1]
https://jpetazzo.github.io/2013/10/06/policy-rc-d-do-not-start-services-automatically/
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailin
c/systemd and /lib/systemd), so the fact that one
file changed tells it nothing about whether the resulting
configuration is OK.
You may want to use systemctl edit, which triggers a unit reload after it exits.
[1] eg at https://bugzilla.redhat.com/show_bug.cgi?id=615527
--
Saludos,
Felipe S
Control: clone -1 -2
Control: reassign -2 tacacs_plus
Control: retitle -2 tatacs_plus: init script should not use + char
Control: tags -1 confirmed upstream fixed-upstream
Control: forwarded -1 https://github.com/systemd/systemd/pull/412
On Mon, 11 Jun 2012 15:03:39 +0200 Bernhard Schmidt wrote:
Control: forwarded -1 https://github.com/systemd/systemd/issues/418
Control: tags -1 confirmed upstream
On Thu, 02 Jan 2014 16:52:55 -0800 Russ Allbery wrote:
> Package: systemd
> Version: 204-6
> Severity: minor
>
> As part of the discussion in the tech-ctte bug report, there seemed to
> be gene
uot; | grep -q /usr; then \
echo "ERROR: $$e links to /usr"; echo "$$OUT"; exit 1; \
fi; \
done
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@li
er a while:
Jul 15 09:35:09 deb-dschepler nscd[851]: nss_ldap: reconnected to LDAP
server ldap://dirsrv.snt.loc after 2 attempts
Jul 15 09:35:10 deb-dschepler ntpd[893]: Listen normally on 4 eth0
10.10.3.14 UDP 123
Jul 15 09:35:10 deb-dschepler ntpd[893]: peers refreshed
So it looks like the
On 15 July 2015 at 14:38, Daniel Schepler wrote:
> On Wed, Jul 15, 2015 at 10:18 AM, Felipe Sateler
> wrote:
>>
>> This contains a massive amount of:
>>
>> Jul 15 09:34:37 deb-dschepler nslcd[905]: nss_ldap: could not connect
>> to any LDAP server as (null) -
helst
nbd
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
On 15 July 2015 at 10:00, Felipe Sateler wrote:
> On 15 July 2015 at 04:34, Wouter Verhelst wrote:
>> is there another way in which I can ship an
>> nbd-client initscript for the benefit of !systemd installations, while
>> still not using it for systemd installations? Drop
tango-db does
not depend on mysql-server...
You might want to take a look at the systemd.service manpage, there is
an EXAMPLES section at the end which may be useful to get you started.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers
On 19 July 2015 at 10:38, Cyril Brulebois wrote:
> Michael Biebl (2015-07-19):
>> Am 17.07.2015 um 19:17 schrieb Felipe Sateler:
>> > [tag]
>> > https://lintian.debian.org/tags/systemd-no-service-for-init-rcS-script.html
>> > , but there a
onf-2.0, libc6 (>= 2.4), libcos4-1 (>=
> 4.1.6), libgcc1 (>= 1:4.1.1), liblog4tango5, libmysqlclient18 (>=
> 5.5.24+dfsg-1), libomniorb4-1 (>= 4.1.6), libomnithread3c2 (>= 4.0.6),
> libstdc++6 (>= 4.4.0), libtango8, libzmq3 (>= 3.2.3+dfsg), zlib1g (
On 17 July 2015 at 18:44, Daniel Schepler wrote:
> On Wed, Jul 15, 2015 at 12:30 PM, Felipe Sateler
> wrote:
>>
>> On 15 July 2015 at 16:09, Daniel Schepler wrote:
>> > On Wed, Jul 15, 2015 at 11:48 AM, Felipe Sateler
>> > wrote:
>> >>
>>
t when the shutdown hangs should let you query the
journal to find out issues.
Note that if you enabled persistent journal logging you can maybe
still get the info from the journal: journalctl -b -
[1] http://freedesktop.org/wiki/Software/systemd/Debugging/
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
On 20 July 2015 at 03:48, Eduard Bloch wrote:
> Hallo,
> * Felipe Sateler [Sun, Jul 19 2015, 03:14:11PM]:
>> So, we have 2 issues:
>>
>> 1. Your system is not shutting down
>> 2. Systemd is not telling you enough to discover what is wrong.
>>
>> I'm
ure all my printers with cups at localhost:631.
> The Bug exists since about 2 weeks.
>
> Solution / workaround :
> Starting the system via grub2 with the sysvinit option. I can see and use all
> my printers.
This looks like #792473
--
Saludos,
Felipe Sateler
7;t understand what you want to change. Your fstab requires
checking of a samba mount, an systemd is telling you it cannot run
fsck on that. What would you expect systemd to do?
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers maili
copy everything to the initramfs:
http://sources.debian.net/src/dracut/040%2B1-1/modules.d/95udev-rules/module-setup.sh/#L47
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists
es I should restart, but I don't remember ever seeing any
packages restart other services.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
command then returns
> login processing to normal, without the delay:
>
> systemctl restart systemd-logind
>
This was already reported as #770135 , but the dbus connection was not
mentioned before. I can confirm the same behavior on systemd 222-2
(inside an nspawn con
art=@/usr/sbin/laptop_mode auto and
RemainAfterExit=no, and trigger this unit instead.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
lly this dance would only be done
when the mask is for a sysv script; however I expect most masks will
be to hide sysv services so this should not be a major problem in
practice.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg
I haven't tested this though, and the postinst condition could be
expanded to include the nonconforming upload done but I'm not sure it
is worth the trouble.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
ppreciated.
Does console-setup actually need to be run before user services are
started? My guess is that it only needs to run before getty, but it
should not block other services that want to start.
If someone could answer that question it should be very simple to
provide a patch for this.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
it won't be enabled in
targetB).
However, (and I don't know if this is new or not), the state does not
seem to be removed on package purge: I removed a target, purged the
package, then reinstalled the package and the enable link was not
generated.
--
Saludos,
Felipe Sateler
On 28 August 2015 at 08:28, Christian Seiler wrote:
> On 28.08.2015 04:39, Felipe Sateler wrote:
>> On 27 August 2015 at 17:19, Christian Seiler wrote:
>>> I've also attached a trivial package in two versions to test this.
>>> They change all 3 options (Want
On 1 September 2015 at 14:05, Anton Zinoviev wrote:
> On Thu, Aug 27, 2015 at 03:18:17PM -0300, Felipe Sateler wrote:
>>
>> Does console-setup actually need to be run before user services are
>> started? My guess is that it only needs to run before getty, but it
>> shou
On 3 September 2015 at 15:24, Ritesh Raj Sarraf wrote:
> there's nothing interesting on the console log, that I
> could provide.
Maybe the journal has information? journalctl -M $machine should give
you the logs of the machine.
--
Saludos,
Fel
. Isn't systemd supposed to disable tty's
when running in a container? Maybe you have modified the containers to
have 4 ttys?
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lis
s -P and specify PIDFile= so that systemd knows for sure
what the main process is.
> TimeoutStopSec=233
Why this weird value?
> Restart=always
I don't know if xorp can be told to exit, but this would cause it to
be restarted in such a case.
>
> [Install]
> W
On 9 September 2015 at 20:46, Dhionel Díaz wrote:
> El 09/09/15 a las 16:34, Felipe Sateler escribió:
>> Hi Dhionel,
>>
>> On 9 September 2015 at 17:38, Dhionel Díaz wrote:
>>> Hi everyone,
>>>
>>> Following the directions in https://wiki.debian.o
ue
to the extra complications involved in preserving the file in the
package systemd-container, this case (that will only be confronted by
sid users) was deliberately not handled.
I think this bug should remain closed.
--
Saludos,
Felipe Sateler
a reboot).
I could not find what the fedora people are doing, but they likely
already faced this problem, it is probably worth checking what they
did.
[1]
http://sources.debian.net/src/selinux-basics/0.5.2/debian/selinux-basics.init/
[2] http://freedesktop.org/wiki/Software/systemd/S
l look for a file named debian/${package}.service,
which doesn't exist.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
und --action=change`
to see if rerunning the restore script gives you sound again.
Alternatively, there is one report that the latest pulseaudio 7 is not
working for them (#800120)
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
by a Recommends from systemd to systemd-coredump, but I do
not have that change in my branch.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/ma
conf is pretty much useless.
>
> Martin, any ideas?
I think a reasonable alternative is to ship using Storage=volatile by
default, and ship the directory in the package (or create it in
postinst).
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
On 5 October 2015 at 12:37, Michael Biebl wrote:
> Am 05.10.2015 um 17:35 schrieb Felipe Sateler:
>> On 5 October 2015 at 12:20, Michael Biebl wrote:
>>> But, when using Storage=persistent, journald will create the directory
>>> /var/log/journal/ itself. So this won&
On 7 October 2015 at 12:17, Josh Triplett wrote:
> On Wed, 7 Oct 2015 13:55:30 +0200 Michael Biebl wrote:
>> Am 05.10.2015 um 17:35 schrieb Felipe Sateler:
>> > I think a reasonable alternative is to ship using Storage=volatile by
>> > default, and ship the directory i
0k here and there end up adding up. Was there talk about splitting
up the existing systemd package up so that minimal images can be
(more) minimal?
In particular, I'm thinking about stuff not needed on containers, so
that the base system image size can be minimized.
--
Saludos,
Felipe Satele
Control: tags -1 patch
On 1 September 2015 at 17:54, Michael Biebl wrote:
> Am 01.09.2015 um 19:38 schrieb Felipe Sateler:
>> On 1 September 2015 at 14:05, Anton Zinoviev wrote:
>>> On Thu, Aug 27, 2015 at 03:18:17PM -0300, Felipe Sateler wrote:
>>>>
>>>&
Control: tags -1 patch
Missed the bug cc, sorry for the duplicate.
On 1 September 2015 at 17:54, Michael Biebl wrote:
> Am 01.09.2015 um 19:38 schrieb Felipe Sateler:
>> On 1 September 2015 at 14:05, Anton Zinoviev wrote:
>>> On Thu, Aug 27, 2015 at 03:18:17PM -0300, Fe
On 10 October 2015 at 09:54, Felipe Sateler wrote:
> On 1 September 2015 at 17:54, Michael Biebl wrote:
>> Am 01.09.2015 um 19:38 schrieb Felipe Sateler:
>>> On 1 September 2015 at 14:05, Anton Zinoviev wrote:
>>>> On Thu, Aug 27, 2015 at 03:18:17PM -0300, Felipe S
On 11 October 2015 at 05:18, Martin Pitt wrote:
> Felipe Sateler [2015-10-10 10:59 -0300]:
>> On IRC it was pointed out that --save is not necessary under systemd:
>> /usr must always be mounted.
>
> This isn't related to systemd itself -- if you have a separate /usr,
&g
On 11 October 2015 at 14:26, Martin Pitt wrote:
> Hey Felipe,
>
> Felipe Sateler [2015-10-11 11:22 -0300]:
>> > This isn't related to systemd itself -- if you have a separate /usr,
>> > it will be mounted as part of local-fs.target of course, but you can't
>
th, so we decided against it back then.
Nod. Although there will have to be shuffling around of at least all
the dbus policies, no?
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
-dev should propagate to the binary Depends (if libdbus has a
symbols file, which IIRC it does), which in turn should forbid an old
dbus-daemon.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.aliot
ng it in a separate package
(branch fsateler/coredump). Michael wanted first to see if more new
packages will be introduced so that NEW queue has to happen only once.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing l
it is not useful because refcount is only decremented at purge,
not removal. I'm a bit unclear on whether the grep should be '^i' or
'^.i', but the results appear to be the same either way.
Thoughts?
--
Saludos,
Felipe Sateler
[1] If you are curious, dpkg-query
themselves.
Yes, please do not use the DISABLED flag (and kill it from the init
script as well).
I note that upstream ferm already has a service file[1] that does not
run at early boot. This suggests that the init script should not run
in runlevel S either.
[1] http://sources.debian.net/sr
On 20 October 2015 at 13:00, Sam Morris wrote:
> On Tue, 2015-10-20 at 12:34 -0300, Felipe Sateler wrote:
>> On 20 October 2015 at 10:23, Sam Morris wrote:
>> > I just ran into this: Ferm was not started at boot. Running
>> > 'journalctl
>> > -b' r
le gain
so we didn't do it. I'm not sure that decision should be reverted.
I'm not sure if the hwclock-save link removal is harmless if done again.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-mainta
t localechooser udeb writes to it[2], live-config[3],
cloud-init (changelog suggests write) and ltsp[4].
[1]
http://codesearch.debian.net/perpackage-results/%2Fetc%2Fdefault%2Flocale/2/page_0
[2]
http://sources.debian.net/src/localechooser/2.67/post-base-installer.d/05localechooser/
[3]
is is the case?).
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
On 10 October 2015 at 09:54, Felipe Sateler wrote:
> Control: tags -1 patch
>
> Missed the bug cc, sorry for the duplicate.
>
> On 1 September 2015 at 17:54, Michael Biebl wrote:
>> Am 01.09.2015 um 19:38 schrieb Felipe Sateler:
>>> On 1 September 2015 at 14:05,
lem with /etc/init.d/iptables - don't load
> firewall.
I don't see this file in any debian package. Where did it come from?
Can we see its contents?
>
> Upgrade to jessie: suspended.
If you have the sysvinit package installed you can still boot using
sysv in
patch in branch fsateler/resolve in the git repository,
creating a new package.
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
full patch ready).
What do you think about rasing the severity to serious? I believe that
is appropriate severity for "known to break the boot".
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-syst
(Please keep the bug on CC)
On 5 November 2015 at 08:10, mila_s wrote:
> Great Thankx!
>
> I am not registered user.
> My 8 servers are running for several years. (migrated from Novell)
> The oldest firewall works for 9 years.
>
>
> W dniu 2015-11-04 13:45:51 u
On 5 November 2015 at 12:11, Michael Biebl wrote:
> Am 04.11.2015 um 19:41 schrieb Felipe Sateler:
>> Hi,
>>
>> I was thinking we should raise severity of the bugs regarding runlevel
>> S where we have confirmation that the bugs have caused dependency
>> loops. C
On Wed, 14 May 2014 06:53:50 +0200 Michael Biebl wrote:
> Package: systemd
> Version: 204-10
> Severity: normal
>
> If a service is masked or a native .service file exists, the
> insserv-generator should not generate any drop-in configs for that unit.
>
> For masked services it's pointless to do s
On 5 November 2015 at 17:32, Matthias Klumpp wrote:
> 2015-11-05 16:36 GMT+01:00 Felipe Sateler :
>> On 5 November 2015 at 12:11, Michael Biebl wrote:
>> [...]
>>> I remember nfs-common/rpcbind, ifupdown in combination with firewalld or
>>> NetworkManager, setse
e status because the
> IPv6 network is working.
>
> root@deb-template:~# ping 172.16.20.1
> PING 172.16.20.1 (172.16.20.1) 56(84) bytes of data.
> ^C
> --- 172.16.20.1 ping statistics ---
> 8 packets transmitted, 0 received, 100% packet loss, tim
/*/{,usr/}lib{,/$arch})
[1]
https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/tree/debian/rules#n222
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/c
Control: tags -1 upstream fixed-upstream
Control: forwarded -1 https://github.com/systemd/systemd/pull/1515
On Mon, 03 Aug 2015 23:26:41 +0530 Ritesh Raj Sarraf wrote:
> Package: systemd
> Version: 223-2
> Followup-For: Bug #719695
>
> Hello,
>
> I am hit by the same problem.
>
> So far, we've sh
y disable it
>> once, since the repeating of that 3 times seems like a bug in its
>> handling of this too.
>
>
> This doesn't look like a Debian specific issue, so it would be great if
> you can file this upstream at
> https://github.com/systemd/systemd/issues/new
I ca
}).
[1]
http://lists.freedesktop.org/archives/systemd-devel/2015-November/034925.html
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listi
On 18 November 2015 at 17:06, Michael Biebl wrote:
> Am 18.11.2015 um 20:53 schrieb Michael Biebl:
>> Am 15.11.2015 um 20:17 schrieb Felipe Sateler:
>>> systemd-analyze is rather large. Perhaps there is scope for a
>>> systemd-tools or something that covers things th
a debian-specific patch[1]? Julian, could you
try with this patch removed?
[1]
http://sources.debian.net/src/systemd/227-3/debian/patches/Revert-core-one-step-back-again-for-nspawn-we-actual.patch
--
Saludos,
Felipe Sateler
___
Pkg-system
still experience the boot problem if you change back to v the directive?
Also do you have the same problem if you disable automount (ie, let it
become a normal mount)?
> I set the severity to critical as this seems to render systems unbootable if
> /home is a network filesystem. I hope tha
hat without the automount, the tmpfiles snippet will only
access the locally mounted filesystems, and systemd will not attempt
to mount the remote one.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.
On Sun, 16 Aug 2015 18:57:40 +0200 Michael Biebl wrote:
> Package: systemd
> Version: 224-1
> Severity: normal
> File: /etc/X11/xinit/xinitrc.d/50-systemd-user.sh
>
> On Debian, there is apparently no support for /etc/X11/xinit/xinitrc.d/.
> So 50-systemd-user.sh is not run during X session startu
Package: dh-systemd
Version: 1.24
Severity: normal
Current autoscript has:
if [ -d /run/systemd/system ]; then
systemctl --system daemon-reload >/dev/null || true
if [ -n "$2" : ]; then
_dh_action=try-restart
else
_dh_action=start
fi
n initscripts could ship such a
configuration, thus demoting dependencies only when initscripts is not
installed.
f/ Patch update-rc.d to use --force when initscripts is not installed.
These two options have the added advantage of not relying on the
active init, and thus could work while switching
On 24 November 2015 at 15:59, Michael Biebl wrote:
> Am 24.11.2015 um 19:37 schrieb Felipe Sateler:
>> e/ Patch insserv to look for a flag file/setting somewhere in
>> /etc/insserv{,.conf.d}, which causes it to treat Required-* as Should*
>> (ie, conffile-version of --for
On 24 November 2015 at 18:28, Michael Biebl wrote:
> Am 24.11.2015 um 22:25 schrieb Petter Reinholdtsen:
>> [Felipe Sateler]
>>> That would potentially leave initscripts with wrong ordering, thus
>>> breaking a boot back to sysvinit (via syvinit package).
>>
&
On 24 November 2015 at 18:57, Felipe Sateler wrote:
> On 24 November 2015 at 18:28, Michael Biebl wrote:
>> Am 24.11.2015 um 22:25 schrieb Petter Reinholdtsen:
>>> [Felipe Sateler]
>>>> That would potentially leave initscripts with wrong ordering, thus
>>>
using only mountkernfs.sh as flag file, we could:
1. Check existence of /lib/sysvinit/init
2. Check existence of some file only present in sysvinit-core
(initreq.h? /usr/share/sysvinit/* ?)
3. Check existence of mountkernfs.sh
And only pass the --force flag if all three checks fail.
>
>> If not, could you Felipe please file a bug against sysv-rc?
Will do.
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
recommends:
ii lsb-base 9.20150917
Versions of packages sysv-rc suggests:
pn bum
-- debconf information excluded
>From e69e187e24ba56f12a28fae85d2925bc5723780a Mon Sep 17 00:00:00 2001
From: Felipe Sateler
Date: Fri, 27 Nov 2015 09:46:07 -0300
Subject: [PATCH] update-rc.d: Ensure insserv d
e.
Unfortunately, that means that to manually re-run the unit, one needs
to do a "restart" instead of a "start" to make systemd run the program
again.
>
> Looking forward to your reply. Thank you!
Thank you for your contribution!
--
Saludos,
Felipe Sateler
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
ad to mentors, and
> ask for sponsor in mentors list.
> Environment="TICK=1 FREQ=0"
I don't think this works. There should be no quotes there, or systemd
might treat TICK variable as containing "1 FREQ=0".
> EnvironmentFile=-/etc/default/adjtimex
> ExecS
enable " will
> actually not start unless one also enables machines.target manually.
>
This is actually new in 228, since before that systemd-nspawn@ had
WantedBy=multi-user.target (and machines.target did not exist).
--
Saludos,
Felipe Sateler
___
On 1 December 2015 at 10:05, Felipe Sateler wrote:
> Control: tags -1 confirmed
>
> On 1 December 2015 at 08:32, Ansgar Burchardt wrote:
>> Package: systemd-container
>> Version: 228-2
>> Severity: normal
>>
>> Hi,
>>
>> machines.tar
switching from one terminal to another only appears to occur when X
> is on tty1. Occasionally it switches to tty1 and back to a login prompt
> on tty2.
Upstream claims the problem is either X or the graphics driver:
https://github.com/systemd/systemd/issues/2061
(Not exactl
er, that without the per-user tmpfs, any user can exhaust
the system-wide runtime
space. So you might want to reconsider if mount failure is innocuous.
>
> An option to turn off this behaviour would be nice.
I don't think upstream will like this, due to the above. A single
tmpfs mo
o create its own csync2 user, and
runs it as root under inetd. I don't know which is appropriate.
> ExecStart = -/usr/sbin/csync2 -i
> StandardInput = socket
> StandardOutput = socket
The StandardOutput line should not be needed, as it is inherited from
StandardInput.
--
Saludos,
Fe
1 - 100 of 332 matches
Mail list logo
