I also find it the current lack of flexibility highly inconvenient.
However, none of the alternatives proposed in the comments above really
cut it as far as I'm concerned. Here is how I'd like to be able to set
up our desktops (users' home directories are on network shares and have
quota imposed on them):

* xsession-errors to a local filesystem, *not* to the home directory;

* automatic log rotation (some users hardly ever log out, there needs to
be a way to keep the log file from growing without bound);

* support for multiple concurrent sessions by the same user, even on the
same computer (e.g., VNC sessions, sessions with different display
depths, etc.; other changes to lightdm may be needed to fully support
this);

* log filtering and compression (to deal with buggy programs that output
the same message in a loop; the latest incident here involved chromium-
browser);

* timestamping of log entries.

Most of this would be easy if there was an option to pipe the output to
an external program (e.g., /usr/bin/logger or some wrapper script around
it). Make that configurable by the administrator and/or the user.
LightDM could pass additional information as command line arguments or
environment variables.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1001035

Title:
  lightdm uses a hardcoded path to .xsession-errors, please make it
  configurable

Status in Light Display Manager:
  Triaged
Status in “lightdm” package in Ubuntu:
  Triaged

Bug description:
  LightDM uses always $HOME/.xsession-errors as the log file because is
  harcoded in xsession.c. But sometimes you want to use a logfile
  outside your $HOME, suposse your $HOME is in an SSD and you want to
  minimize writes, so you want to put it in /tmp/${USER}_xsession-errors
  for example. If you try to make a $HOME/.xsession_errors ->
  /tmp/{$USER}_xsession-errors symlink to cheat LightDM, then LightDM
  will recreate the $HOME/.xsession_errors file and the hack will not
  work.

  LightDM _always_ recreates $HOME/.xsession_errors and you can't change
  it without recompiling. So, I think this log file needs to be
  configurable, or at least preserve the symlink if one is present.

  Ubuntu 12.04 LTS
  LightDM 1.2.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1001035/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to