Custom Query (1145 matches)


Show under each result:

Results (217 - 219 of 1145)

Ticket Resolution Summary Owner Reporter
#239 worksforme Firefox 3 against AFS homedirs has bad performance broder

Reported by broder, 14 years ago.


We should figure out if there's anything we can do about this.

In particular, we may want to consider setting to 0 in the Firefox plugin. See also  discuss:3771

#240 fixed notify users they're in a chroot on sudo/su geofft

Reported by geofft, 14 years ago.


As I wrote to debathena@ on March 12,

We noticed on zephyr today that sudo has a lecture_file option that will cause it to print a custom message the first time you run sudo. I propose we use it to do something like

$ sudo aptitude install snes9x-x
Attention: You are on a Debathena cluster machine. Although you can use
sudo to become root, your access is restricted to a sandbox (chroot)
created when you logged in. If you install software or change
global settings, they will be reverted when you log out.

If you would like a permanent change to cluster machines, please
report a bug via the "sendbug" command.
Enter your Athena password below.

[sudo] password for geofft:

This would involve setting "Defaults lecture_file=(this warning) lecture=once" in /etc/sudoers.

Another option would be to do this with pam_echo in /etc/pam.d/sudo and /etc/pam.d/su. It has the advantage of also working for su, but making it warn you only once would be harder, so we'd probably have to say something shorter like "Warning: You are in a login sandbox. See  http://... for more information."

Another option would be for 'tellme root' to print the same warning to cover the 'su' case, although unless we change the root password nobody will notice...

After a brief discussion, we determined that sudo warns you once per session, rather than per account or whatever, so this has basically the right behavior.

I intend to go with the lecture_file approach soon, because it's an easy change, unless there's particular interest in having sudo and su use the same configuration. Comments on the wording?

#241 fixed debathena-counterlog needs to depend on debathena-machtype mitchb

Reported by mitchb, 14 years ago.


Pretty self-explanatory. This should not be able to happen:

/etc/cron.daily/debathena-counterlog: /usr/bin/athena-counterlog: 18: machtype: not found /usr/bin/athena-counterlog: 21: machtype: not found /usr/bin/athena-counterlog: 22: machtype: not found

Note: See TracQuery for help on using queries.