Custom Query (1145 matches)

Reported by geofft, 15 years ago.

Nobody will read this e-mail because we've all tuned them out. That's a problem.

Reported by andersk, 15 years ago.

We’ve discovered that on recent Ubuntu, sleeping for extended periods inside a cron job can interfere with shutting down or restarting the machine through the GUI, because it claims that other users are logged in. This is not as important for -cluster but may be annoying to some -workstation users (or anyone else that decides to use our auto-updater).

geofft found  LP:284229, which is not related to anything except in that it mentions “The use of pam-ck-connector means that consolekit registers a session for every cron or ssh session started.” which partially explains the issue.

We could background the job, but we would lose cron’s job management and error reporting. Furthermore, it is a nice feature that it warns you about shutting down or restarting while an update is running.

So instead I think we should make the postinst edit a random hour-mod-2 and minute into /etc/cron.d/debathena-auto-update, and get rid of the sleep.

Reported by quentin, 15 years ago.

I just observed a user who wasn't able to log in because he had exceeded his quota; he got as far as the zenity dialog telling him his quota was exceeded, and then the login session completely hung when he pressed the OK button in the dialog. The zenity window hung with the button depressed, and the login didn't continue. I had to walk him through sshing in from another machine to delete some files; that's not something that the average user is expected to be able to do.