Custom Query (1145 matches)

Reported by jdreed, 15 years ago.

After discussion on Athena10 list and via IM, broder has proposed amendments to attach and detach as they're currently working on debathena/Athena10:

(a) Change liblocker so that the attachtab has a concept of per-user mounts (i.e. in addition to tracking which users have a locker mounted, it can also say "broder has /afs/.sipb/project/whatever mounted at /mit/whatever, but price has /usr/local/whatever mounted at /mit/whatever")

(b) Write PyLocker?

(c) Change pyHesiodFS to use PyLocker? instead of keeping its own cache and additionally, alter it to present a different view onto /mit for each user. (i.e. I would actually *see* /mit/whatever symlinked to /afs/.sipb/project/whatever, while if Greg looked at /mit/whatever, he'd see a symlink to /usr/local/whatever)

• This is actually not that hard once parts (a) and (b) are done.

PyFUSE has fuse.FuseGetContext?(), which returns the UID, GID, and PID of the process making the given request.

This would allow us to bring back attach -e, and even allow it to be run by non-root users.

Also add -r should remove the locker from the Search path even if it is not attached rather than complaining of a non-attached locker.

This improved interface should be implemented and tested to see if it is better, and if it is better, it should become the default.

Reported by geofft, 15 years ago.

CUPS by default scans the local network for printers. While this seems at first glance to be either good or neutral. it's the case that lots of users have their personal laptops configured (incorrectly, arguably, but it still happens) to print to Athena printers and then share their local configuration of that printer.

For example, next6.mit.edu is seeing both a "tree-eater" (which I've locally configured because it's Kerberized; see ATN-28) and a "tree_eater", which someone in the dorm has set up. Users should not click an Athena cluster printer's name in the GUI and get some random laptop as their print server.

Reported by broder, 15 years ago.

Users of some (maybe all?) cluster machines get presented with an system notification about restricted drivers being available. They also get prompted when updates are available.

There are a couple issues here.

(1) We should possibly be enabling the restricted drivers (2) We should try to generally suppress these notifications