Your message dated Thu, 15 Dec 2016 21:44:18 +0100
with message-id <4e0c6efa-6e47-0370-b724-b6a835659...@debian.org>
and subject line Re: Bug#833559: systemd user service standard output is not 
line-buffered
has caused the Debian Bug report #833559,
regarding systemd user service standard output is not line-buffered
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
833559: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=833559
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: systemd
Version: 230-7
Severity: normal

I've tested the following short-lived "daemon" as a systemd user service:

-------
#include <stdio.h>
#include <unistd.h>

int main(int argc, char **argv)
{
  sleep(5);
  printf("a test\n");
  sleep(10);
  return 0;
}
-------

the "a test" line doesn't show up in the user journal when i would
expect it to.  it appears that stdout is not line-buffered.

stderr, on the other hand, does appear to be line-buffered --
newline-terminated strings written to stderr show up immediately in
the journal.

i'd expect both stdout and stderr to be line-buffered.

    --dkg

-- Package-specific info:

-- System Information:
Debian Release: stretch/sid
  APT prefers testing-debug
  APT policy: (500, 'testing-debug'), (500, 'testing'), (200, 
'unstable-debug'), (200, 'unstable'), (1, 'experimental-debug'), (1, 
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.7.0-rc7-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages systemd depends on:
ii  adduser         3.115
ii  libacl1         2.2.52-3
ii  libapparmor1    2.10.95-4
ii  libaudit1       1:2.6.5-1
ii  libblkid1       2.28-6
ii  libc6           2.23-4
ii  libcap2         1:2.25-1
ii  libcap2-bin     1:2.25-1
ii  libcryptsetup4  2:1.7.0-2
ii  libgcrypt20     1.7.2-2
ii  libgpg-error0   1.24-1
ii  libidn11        1.33-1
ii  libkmod2        22-1.1
ii  liblzma5        5.1.1alpha+20120614-2.1
ii  libmount1       2.28-6
ii  libpam0g        1.1.8-3.3
ii  libseccomp2     2.3.1-2
ii  libselinux1     2.5-3
ii  libsystemd0     230-7
ii  mount           2.28-6
ii  util-linux      2.28-6

Versions of packages systemd recommends:
ii  dbus            1.10.8-1
ii  libpam-systemd  230-7

Versions of packages systemd suggests:
ii  policykit-1        0.105-16
ii  systemd-container  230-7
pn  systemd-ui         <none>

Versions of packages systemd is related to:
ii  udev  230-7

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 232-7

On Fri, 5 Aug 2016 18:35:36 -0400 Felipe Sateler <fsate...@debian.org>
wrote:
> Control: tags -1 moreinfo
> 
> On 5 August 2016 at 18:22, Daniel Kahn Gillmor <d...@fifthhorseman.net> wrote:
> > Package: systemd
> > Version: 230-7
> > Severity: normal
> >
> > I've tested the following short-lived "daemon" as a systemd user service:
> >
> > -------
> > #include <stdio.h>
> > #include <unistd.h>
> >
> > int main(int argc, char **argv)
> > {
> >   sleep(5);
> >   printf("a test\n");
> >   sleep(10);
> >   return 0;
> > }
> > -------
> >
> > the "a test" line doesn't show up in the user journal when i would
> > expect it to.  it appears that stdout is not line-buffered.
> 
> Does it appear in the journal at all (ie, without any filters)? What
> do you mean by "when I would expect it to"?
> 
> > stderr, on the other hand, does appear to be line-buffered --
> > newline-terminated strings written to stderr show up immediately in
> > the journal.
> >
> > i'd expect both stdout and stderr to be line-buffered.
> 

Fwiw, this works fine here using a service file like

$ cat .config/systemd/user/test.service
[Unit]
Description=test

[Service]
ExecStart=/home/michael/test


$ systemctl --user start test

Results in
$ journalctl -f
Dez 15 21:41:12 pluto systemd[1896]: Started test.
Dez 15 21:41:27 pluto test[25294]: a test


So I'm closing this bug report accordingly. If you still run into this
issue and you are available for further questions/debugging, please reopen.

Regards,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
_______________________________________________
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Reply via email to