Thank you for taking the time to report this issue and help to improve
Ubuntu.
According to the documentation, the argument to net ads join -S is a
server name, not a realm or domain name. Does this work if you specify
net ads join -w STAFF.GCD.IE instead?
If it works with -w, then I don't
Public bug reported:
Binary package hint: php5
php5 and libtool 2.2 cause some PHP related packages to FTBFS.
php-imap, for instance:
cd build-php5 ./configure --build=i486-linux-gnu --host=i486-linux-gnu \
--prefix=/usr \
--with-php-config=/usr/bin/php-config5
Indeed, winbind is installed and running. I'm not sure why it is
installed, but it is.
--
HAL crashes with generated smb.conf
https://bugs.launchpad.net/bugs/239947
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in ubuntu.
--
The attached patch adds a debconf question, prompting the user as to the
desired behavior on a newly degraded RAID...
To boot, or not to boot, that is the question.
The priority is currently set to medium, with the default being
BOOT_DEGRADED=false, which is the conservative/traditional
Updated patch. Only difference from the previous is that I added a line
to the change log about the debian/po/*.po files changed.
:-Dustin
** Attachment added: mdadm.boot_degraded_debconf.debdiff
http://launchpadlibrarian.net/16894112/mdadm.boot_degraded_debconf.debdiff
--
cannot boot
So, I see three options to fix this, which one to use isn't my call to
decide:
1. patch spamassassin package, to make sure sa-learn doesn't complain if
use_bayes is set to 0
2. patch amavisd-new package, to not run sa-learn if use_bayes is set to
0. There should be a way to query SpamAssassin's
I'd buy:
2. patch amavisd-new package, to not run sa-learn if use_bayes is set to
0. There should be a way to query SpamAssassin's configuration from a
script - if there is, just use it.
Patches welcome.
--
amavisd-new + spamassassin: cronjob spams root user
Thank you for taking the time to report this issue and help to improve
Ubuntu.
This is the same as the previously-reported bug #244265; I'm therefore
marking this report as a duplicate.
--
winbindd segfaults regularly
https://bugs.launchpad.net/bugs/247316
You received this bug notification
Public bug reported:
Binary package hint: samba
Using Ubuntu Hardy L.T.S this error comes up when connecting to Samba
with security = user. My setup checks the password with LDAP, our schema
contains no password expiry information and we don't have this trouble
with other versions of Samba.
Dustin, you could have open a separate bug with your debconf patch to
track your work and at the same time keep the comunity updated and able
to give you feedback in a more organized manner.
the default being BOOT_DEGRADED=false, which is the
conservative/traditional behavior.
Only some may
This bug is considerably overloaded.
Thus, I have split the mdadm/debconf/boot_degrade bug/patch to:
* Bug #259127
:-Dustin
--
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
The smb.conf file is owned by the samba-common package, not by the samba
package (which is only the server components). To force regeneration of
the smb.conf file, you need to use apt-get remove --purge samba-common.
Closing as invalid, the reasons for not regenerating the config file
whenever
Wow, Dustin we again wrote or comments almost simultaneously. Thank you for
separating the issue.
--
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
Sorry for the delay in getting back to you.
Unfortunately, my laptop died shortly after you responded and I have not
been able to resuscitate it. You might as well close this bug and when I
buy a new laptop for Ubuntu I shall attempt to recreate the problem and
resubmit at that point.
Thanks fro
Only some may consider this conservative behaviour a broken behavior,
when a system on a redundant array of independent disks will degrade
just fine when running, but won't even come up when booting.
Even the more when you have upgraded from dapper LTS to hardy LTS and you
*think* you are
I have separated out the issue of booting with degraded non-root arrays
into Bug# 259145.
As a user merely helping to gather info I can't say if updates to hardy
(ubuntu 8.04) will be made available. Dustin?
--
cannot boot raid1 with only one disk
https://bugs.launchpad.net/bugs/120375
You
One more comment on this; I can understand the conservative
behaviour, but when an array was degraded, the boot process halted with
NO MESSAGE indicating what was wrong. Please whatever you do, even in
the case of maintaining conservative behavior, emit a message telling
the user why you're not
On Monday 18 August 2008, Ross Becker wrote:
One more comment on this; I can understand the conservative
behaviour, but when an array was degraded, the boot process halted with
NO MESSAGE indicating what was wrong. Please whatever you do, even in
the case of maintaining conservative
18 matches
Mail list logo
