I'd love to see a config that flips the Grub list between all kernels, like now, and OSs only (newest kernel from each). We shouldn't remove the ability to make a full list, but I really doubt the average users needs to run a backup kernel, ever.
-- Clarify which kernel is updated in Grub https://bugs.launchpad.net/bugs/629024 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs From [email protected] Thu Sep 02 13:11:02 2010 Return-path: <[email protected]> Envelope-to: [email protected] Delivery-date: Thu, 02 Sep 2010 13:11:02 -0700 Received: from exprod5mx268.postini.com ([64.18.0.91] helo=psmtp.com) by mail-archive.com with smtp (Exim 4.69) (envelope-from <[email protected]>) id 1OrG7i-0005t3-9f for [email protected]; Thu, 02 Sep 2010 13:11:02 -0700 Received: from source ([69.147.83.53]) by exprod5mx268.postini.com ([64.18.4.10]) with SMTP; Thu, 02 Sep 2010 15:11:01 CDT Received: from hub.freebsd.org (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id 0A11D1561C0; Thu, 2 Sep 2010 20:10:48 +0000 (UTC) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id 144C11065863; Thu, 2 Sep 2010 20:10:45 +0000 (UTC) (envelope-from [email protected]) Delivered-To: [email protected] Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 67303106580D for <[email protected]>; Thu, 2 Sep 2010 20:10:37 +0000 (UTC) (envelope-from [email protected]) Received: from mail-qw0-f54.google.com (mail-qw0-f54.google.com [209.85.216.54]) by mx1.freebsd.org (Postfix) with ESMTP id 24ED48FC1A for <[email protected]>; Thu, 2 Sep 2010 20:10:36 +0000 (UTC) Received: by qwg5 with SMTP id 5so1001111qwg.13 for <[email protected]>; Thu, 02 Sep 2010 13:10:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=hPgYqORSnTnTSCDFLTVlyVMr6Jv+dW7IK/EydJJNVXo=; b=wJors8wEs6lmyqEu455XxzOQMt9zE9VbJAiBTFU4sNxf5VwF48/tR0aWqg7j7CxzA8 W116PnSk5qk2PSou/wOlMsQT/ri0UqvLXv/8wyzXA3FMAlsLWyDgcLFkUSq3RDrM1BuW F60eRsJOfKiqJKO9UoiVZPnl8q7Kn6g6g13tA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=phHy3icnzWIeQirEjyrixGNwh8y+rUaA309AdtSun6IBMsPXjKjUMpW7uNRh/RFit1 LMCJkH/GIA7XBGqlXm3O0kzDePb7+kYj8yKtMYdsk9QVlRAJxXVnuk7POB6Rqcopkl9e DLaNy6TDAfE2D70nANlDtWbFpC9RhXgaorYZA= MIME-Version: 1.0 Received: by 10.224.6.136 with SMTP id 8mr41326qaz.149.1283456554673; Thu, 02 Sep 2010 12:42:34 -0700 (PDT) Received: by 10.224.20.74 with HTTP; Thu, 2 Sep 2010 12:42:34 -0700 (PDT) Date: Thu, 2 Sep 2010 12:42:34 -0700 Message-ID: <[email protected]> From: patrick <[email protected]> To: FreeBSD Questions Mailing List <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 Subject: 8.1: Cron ignoring crontab updates X-BeenThere: [email protected] X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions <freebsd-questions.freebsd.org> List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:[email protected]?subject=unsubscribe> List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions> List-Post: <mailto:[email protected]> List-Help: <mailto:[email protected]?subject=help> List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>, <mailto:[email protected]?subject=subscribe> Sender: [email protected] Errors-To: [email protected] X-pstn-neptune: 0/0/0.00/0 X-pstn-levels: (S:98.07000/99.90000 CV:99.9000 FC:95.5390 LC:95.5390 R:95.9108 P:95.9108 M:97.0282 C:98.6951 ) X-pstn-settings: 4 (1.5000:1.5000) s cv gt3 gt2 gt1 r p m c X-pstn-addresses: from <[email protected]> [294/10] I recently upgraded a FreeBSD 7.0 system to 8.1-RELEASE (via freebsd-update) and am experiencing the strangest cron problem I have ever seen. My cron jobs run, but if I make any changes to my crontab, cron does not pick them up; it continues to operate based on the snapshot of crontabs it loaded when cron was started up. If I restart cron (/etc/rc.d/cron restart), the changes are then picked up, but again, any subsequent changes are ignored. I don't see any issues with the permissions, and when I edit a crontab, it says "crontab: installing new crontab", and the /var/log/cron log shows BEGIN EDIT, REPLACE, and END EDIT. I'm somewhat at a loss to figure out where the disconnect is, and it's impractical for me to have to restart cron any time any user updates their crontab. Has anyone come across this? Patrick _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
