Custom Query (1145 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (28 - 30 of 1145)

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Ticket Resolution Summary Owner Reporter
#371 fixed Graphical Installer should suggest use of athena username. xavid afarrell

Reported by afarrell, 12 years ago.

Description

Desired behaviour: during installation, when the user is asked for a username, he/she should be suggested to use his/her athena username. Actual behaviour: the user is simply asked for a username. To Reproduce: Install Debathena via the graphical installer.

This would simply make things simpler for using ssh, renewing tickets. It would prevent the user from having to know most of http://debathena.mit.edu/customizing.

additional shinyness: if the user's athena username is known, that should be filled in as the default.

#457 fixed force logout of abandoned cluster causes greyout geofft afarrell

Reported by afarrell, 12 years ago.

Description

After trying to force logout a user who has been away yet logged in for a significant amount of time, the screen turns light grey and the fan begins overspinning.

#245 workaround 127.0.1.1 breaks 3partysw license managers alexp

Reported by alexp, 12 years ago.

Description

On Apr 3, 2009, at 6:07 PM, Anders Kaseorg wrote:

127.0.1.1 zippy zippy.mit.edu is denied, but 127.0.1.1 zippy.mit.edu is allowed.

This probably happens because hostname -i will be 127.0.1.1 in the former case, but 18.142.4.128 in the latter case. So this is another manefestation of the known problem with 127.0.1.1.

Thanks for the information; we really need to solve the problem though; do we do that by making sure all hosts on those lines are fully qualified?

To be clear, the problem is not that there is a non-fully-qualified hostname in /etc/hosts. The problem is that because your kernel’s hostname is zippy, which is resolved by /etc/hosts to 127.0.1.1, license managers that have a client-side ACL of IP addresses (like 18.*) get confused.

If, as you did, you take zippy out of /etc/hosts (leaving only zippy.mit.edu), then zippy is resolved by DNS to 18.142.4.128 using the search path and servers in /etc/resolv.conf, and the license manager presumably becomes less confused.

A better client-side workaround is to put the right IP address in /etc/hosts:

18.142.4.128 zippy zippy.mit.edu

which is what I think the Ubuntu installer does if you configure it with a static IP address at install time. (For the cluster machines, we currently don’t.)

We are currently discussing possible solutions on zephyr.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
Note: See TracQuery for help on using queries.