Custom Query (1145 matches)

Reported by kaduk, 12 years ago.

root@PALAVER:/# apt-get install debathena-build-depends
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package debathena-build-depends is not available, but is referred to by another package
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Package 'debathena-build-depends' has no installation candidate

Reported by jdreed, 12 years ago.

Hotline and anecdotal information has suggested that there's some new failure mode, whereby machines come up fine, but attempting to log in causes the greeter to spin. However, networking clearly works. I'll note that a new dbus and a new bind9 showed up fairly recently, and I'm inclined to think that accountservice (started via Dbus) is not starting soon enough, or something, since subsequent attempts work. I initially thought this might be #1259, but now I'm not so sure.

 LP:996791 shares some of these symptoms, and lightdm.log is complaining about FindUserByName?

Reported by adehnert, 12 years ago.

We have lots of mosh-server's on linerva that probably have no clients still around, and will never be connected to. We should figure out a good way to discourage them from accumulating. Fixing the garbage collection half of  https://github.com/keithw/mosh/issues/12 might be part of this.

Techniques / possible components:

• installing an attachandrun script that we tell people to use, and having it do some sort of setup
• kill long-idle mosh sessions (upstream changes may have a role to play here, as might just having root run a bunch of "kill" commands every once in a while...)
• giving mosh sessions some session identifier and auto-killing any current servers with that session ID when connecting
• yelling at people with lots of mosh sessions