Copied to dapper-updates, thank you!
** Changed in: cyrus-sasl2 (Ubuntu Dapper)
Status: Fix Committed = Fix Released
--
Should use /dev/urandom instead of /dev/random
https://bugs.launchpad.net/bugs/225333
You received this bug notification because you are a member of Ubuntu
Server Team,
OK, so this fix must be part of the numerous ACPI fixes in Gutsy/hardy, I'm
closing this bug.
Thanks for posting it and sorry that nobody found the time to answer to you
before.
** Changed in: openvpn (Ubuntu)
Status: Incomplete = Invalid
--
openvpn doesn't reconnect after
Accepted into -proposed, please test and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: samba (Ubuntu Hardy)
Status: New = Fix Committed
** Tags added:
Accepted into -proposed, please test and give feedback here. Please see
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!
** Changed in: samba (Ubuntu Hardy)
Status: New = Fix Committed
** Tags added:
Oops...
It turned out that my regular user (not root) started sshd with that
port number. and since only root allowed to open high ports, the
connection got terminated.
1. why did sshd / ubuntu allowed the regular user to even start the service,
when it's clear no connections will be received?
See this link for openssh 5.1 and internal chrooted sftp server logging ability
added in this version:
https://bugzilla.mindrot.org/show_bug.cgi?id=1488
--
Apply openssh sftp-chroot patch to openssh-server
https://bugs.launchpad.net/bugs/24777
You received this bug notification because you are
How can I apply them?
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a duplicate bug.
--
Ubuntu-server-bugs mailing list
Source removed.
** Changed in: openldap2.3 (Ubuntu)
Status: Confirmed = Fix Released
--
Remove openldap2.3 source package from intrepid archive
https://bugs.launchpad.net/bugs/247439
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
Public bug reported:
Is there any chance to get the 1.1.x release of Dovecot backported to
Hardy?
** Affects: dovecot (Ubuntu)
Importance: Undecided
Status: New
** Tags: new upstream
** Tags added: new upstream
--
New Dovecot 1.1.x upstream for hardy-backports
I'm using:
- Ubuntu 2.6.24-16-server SMP
- Apache 2.2.8-1ubuntu0.3 (apache2-mpm-worker)
Thanks
Bri
--
If many queries come in too quickly, apache2 freezes.
https://bugs.launchpad.net/bugs/234367
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Added to hardy-backports project.
** Also affects: hardy-backports
Importance: Undecided
Status: New
** Changed in: dovecot (Ubuntu)
Status: New = Invalid
** Changed in: hardy-backports
Importance: Undecided = Wishlist
--
New Dovecot 1.1.x upstream for hardy-backports
5.1p1 doesn't seem to be working right for this. Bumping back to in-
progress while I think about this.
** Changed in: openssh (Ubuntu)
Status: Fix Committed = In Progress
--
ssh server forces a command when it should not
https://bugs.launchpad.net/bugs/161047
You received this bug
This bug was fixed in the package openssh - 1:5.1p1-1ubuntu1
---
openssh (1:5.1p1-1ubuntu1) intrepid; urgency=low
* Resynchronise with Debian. Remaining changes:
- Add support for registering ConsoleKit sessions on login.
- Drop openssh-blacklist and openssh-blacklist-extra
This bug was fixed in the package openssh - 1:5.1p1-1ubuntu1
---
openssh (1:5.1p1-1ubuntu1) intrepid; urgency=low
* Resynchronise with Debian. Remaining changes:
- Add support for registering ConsoleKit sessions on login.
- Drop openssh-blacklist and openssh-blacklist-extra
This bug was fixed in the package openssh - 1:5.1p1-1ubuntu1
---
openssh (1:5.1p1-1ubuntu1) intrepid; urgency=low
* Resynchronise with Debian. Remaining changes:
- Add support for registering ConsoleKit sessions on login.
- Drop openssh-blacklist and openssh-blacklist-extra
This bug was fixed in the package openssh - 1:5.1p1-1ubuntu1
---
openssh (1:5.1p1-1ubuntu1) intrepid; urgency=low
* Resynchronise with Debian. Remaining changes:
- Add support for registering ConsoleKit sessions on login.
- Drop openssh-blacklist and openssh-blacklist-extra
2/ openvpn is configured to run as openvpn user out-of-the-box
in Gutsy, and when you upgrade to hardy it runs as root.
Case number 2.
Like I said, my testing on a fresh gutsy install has failed to reproduce
that :
$ sudo apt-get install openvpn
[...]
$ grep openvpn /etc/passwd | wc -l
0
$
** Changed in: openldap2.3 (Ubuntu)
Assignee: (unassigned) = Jamie Strandboge (jdstrand)
--
slapd needs apparmor changes for cn=config
https://bugs.launchpad.net/bugs/243525
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap2.3
Public bug reported:
Binary package hint: winbind
Upgrading Dapper to Hardy
ProblemType: Package
Architecture: i386
Date: Fri Jul 25 22:15:08 2008
DistroRelease: Ubuntu 8.04
ErrorMessage: dependency problems - leaving unconfigured
NonfreeKernelModules: ath_hal
Package: winbind
** Attachment added: Dependencies.txt
http://launchpadlibrarian.net/16314597/Dependencies.txt
** Attachment added: DpkgTerminalLog.gz
http://launchpadlibrarian.net/16314598/DpkgTerminalLog.gz
--
package winbind 3.0.28a-1ubuntu4.4 failed to install/upgrade: dependency
problems - leaving
And this mdadm patch supercedes the previous one. It uses the new
initramfs-tools interface for adding the fail hook.
Updated package in my PPA:
* https://launchpad.net/~kirkland/+archive
:-Dustin
** Attachment added: mdadm.120375.debdiff
** Changed in: initramfs-tools
Status: Confirmed = In Progress
** Changed in: mdadm (Ubuntu)
Status: Triaged = In Progress
** Also affects: initramfs-tools (Ubuntu)
Importance: Undecided
Status: New
** Changed in: initramfs-tools (Ubuntu)
Assignee: (unassigned) =
Testing instructions for Intrepid are available in a wiki page for a
specification covering this bug:
*
https://wiki.ubuntu.com/BootDegradedRaid#head-a5a91db34505d4a047fd7f30e44ac2020da369a6
:-Dustin
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received
Hi, some feedback about the patches.
Does it matter if call_failure_hooks is allways called?
mdadm --run --scan will start all arrays degraded not only the one needed for
the rootfs (and its lvm and crypt respectively).
It will start for example a partial array from a removable disk that was
After
# We've given up,
A while loop is calling panic. An if statement might look better.
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You received this bug notification because you are a member of Ubuntu
Server Team, which is a subscriber of a duplicate bug.
On Sat, Jul 26, 2008 at 01:15:08AM -, ceg wrote:
# We've given up,
A while loop is calling panic. An if statement might look better.
No, the while loop is correct -- it lets the user attempt to fix the
system repeatedly and on failures, it will drop to a shell again.
--
cannot boot raid1
On Fri, Jul 25, 2008 at 8:08 PM, ceg [EMAIL PROTECTED] wrote:
Instead of fixed sleep 5 in init-premount/mdadm, you could introduce a check
timeout loop
after call_failure_hooks in the local script. (So we can resume booting
ASAP.) Maybe just copy
the slumber while loop from above the
On Fri, Jul 25, 2008 at 8:08 PM, ceg [EMAIL PROTECTED] wrote:
mdadm --run --scan will start all arrays degraded not only the one needed
for the rootfs (and
its lvm and crypt respectively).
It will start for example a partial array from a removable disk that was
attatched and hasn't been
28 matches
Mail list logo
