[Pkg-ltsp-devel] Bug#539116: ltsp-server: garbage in output of ltsp-build-client

[Vagrant Cascadian]

reassign 539116 uswsusp
retitle 539116 uswsusp: truncates /dev/stderr in config script
thanks

On Wed, Jul 29, 2009 at 10:41:57AM +0200, Andre Majorel wrote:
> running ltsp-build-client &>log creates a file containing a long
> run of NULs and possibly out of order text :

i was able to reproduce this with current versions of ltsp, though i believe
the bug is actually in uswsusp's config script.

by running "ltsp-build-client --early-packages ltsp-client-core &> log", which
installs a smaller set of packages, i wasn't able to reproduce the problem.

running "ltsp-build-client --early-packages 'ltsp-client-core uswsusp' &> log",
triggers the problem again.

> I'm guessing that at some point, something inside
> ltsp-build-client does something it shouldn't with stdout and/or
> stderr... Perhaps reopening either one with O_TRUNC just before
> writing "NOTE: disabling security APT source for sid.  It does not
> exist."...

i think it occurs much later, as the log file gets truncated with the first
message being: 

  /sys not mounted. Can't create uswsusp.conf

followed by all the NULL characters.

i think it is uswsusp.config writing to stderr:

  mountpoint -q /sys ||
    { echo "/sys not mounted. Can't create uswsusp.conf" > /dev/stderr; exit 0; }

maybe using ">> /dev/stderr" would not truncate the log file, and fix the
issue?

live well,
  vagrant