Hello Oleg, or anyone else affected,
Accepted juju-core into trusty-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/juju-
core/1.22.1-0ubuntu0.14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
** Changed in: devstack
Status: New = Invalid
** Changed in: heat
Status: New = Invalid
** Changed in: heat (Ubuntu)
Status: New = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to heat in Ubuntu.
** Package changed: openssh (Ubuntu) = xorg (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1450871
Title:
xserver crashes ATI AMD Radeon 7700 driver 12.20
To manage
Thanks for following up. Closing this bug 'wontfix'.
** Changed in: rpcbind (Ubuntu)
Status: Incomplete = Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rpcbind in Ubuntu.
https://bugs.launchpad.net/bugs/1448586
*** This bug is a duplicate of bug 1438745 ***
https://bugs.launchpad.net/bugs/1438745
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1438745, so it is being marked as such. Please
The output in your log is:
Preparing to unpack .../rpcbind_0.2.1-6ubuntu3_amd64.deb ...
Error getting authority: Error initializing authority: Could not connect: No
such file or directory (g-io-error-quark, 1)
Error getting authority: Error initializing authority: Could not connect: No
such
The version of haproxy in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
The version of haproxy in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
The version of haproxy in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: haproxy (Ubuntu Trusty)
Status: Fix Committed = Won't Fix
The version of haproxy in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
The version of haproxy in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
The version of haproxy in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
The version of haproxy in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
The version of charm-tools in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
The version of seabios in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: seabios (Ubuntu Trusty)
Status: Fix Committed = Won't Fix
The version of haproxy in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: haproxy (Ubuntu Precise)
Status: Fix Committed = Won't
The version of charm-tools in the proposed pocket of Precise that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
** Changed in: charm-tools (Ubuntu Precise)
Status: Fix Committed =
The version of seabios in the proposed pocket of Trusty that was
purported to fix this bug report has been removed because the bugs that
were to be fixed by the upload were not verified in a timely (105 days)
fashion.
--
You received this bug notification because you are a member of Ubuntu
Ok, don't know how this ended up with the wrong bug number in the
changelog, but cloud-init has been uploaded and accepted into vivid.
cloud-init (0.7.7~bzr1088-0ubuntu3) vivid; urgency=medium
* systemd/*.service: don't declare a Wants/Requires on network.target; this
is a passive target
The last piece of this is cloud-init, which has been uploaded and is
awaiting freeze review.
** Changed in: snappy-ubuntu
Status: New = In Progress
** Changed in: snappy-ubuntu
Status: In Progress = Fix Committed
--
You received this bug notification because you are a member of
Confirmed that the systemd fixes have the correct effect in the latest
devel-proposed version. Thanks, Martin! Now we just need the cloud-
init changes.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
On Tue, Apr 07, 2015 at 02:35:35PM -, Martin Pitt wrote:
Steve Langasek [2015-04-07 14:22 -]:
I'm not sure what you mean by this. We absolutely did block on our network
interfaces when using upstart; just with a 2 minute timeout for any
misconfigured interfaces.
Right
minute timeout for any
misconfigured interfaces.
The code change itself appears reasonable to me.
--
Steve Langasek Give me a lever long enough and a Free OS
Debian Developer to set it on, and I can move the world.
Ubuntu Developer
** Information type changed from Private Security to Public
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to init-system-helpers in Ubuntu.
https://bugs.launchpad.net/bugs/1441369
Title:
package init-system-helpers 1.22ubuntu5 failed
Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a regular (non-security) bug. I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross
Sorry, that part of the systemd.special(7) manpage doesn't actually
explain the problem with network.target. The problem is described here:
SPECIAL PASSIVE SYSTEM UNITS
A number of special system targets are defined that can be used to
properly order boot-up of optional services.
Martin, I'm assigning the ifupdown and systemd tasks to you, as I'm not
sure how to fix this. Can you please have a look?
** Changed in: systemd (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Server Team,
The remaining issue is that /etc/init.d/networking is sequenced before
network.target, with no timeout.
# cat
/run/systemd/generator/networking.service.d/50-insserv.conf-\$network.conf
# Automatically generated by systemd-insserv-generator
[Unit]
Wants=network.target
Before=network.target
#
I'm looking through the systemd ordering now; I've found a couple of
issues so far:
- ifupdown: /lib/systemd/system/network-online.target.wants/ifup-wait-
all-auto.service is a broken symlink to ../ifup-all-auto.service, looks
like this should be ../ifup-wait-all-auto.service instead.
-
Fix uploaded; debdiff attached.
** Patch added: maas-1433697.patch
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1433697/+attachment/4349158/+files/maas-1433697.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in
Public bug reported:
The maas-cluster-controller package depends on syslinux-dev to provide
/usr/lib/syslinux/pxelinux.0, in response to bug #1328659. However, as
the name implies, 'syslinux-dev' is not meant to be used at runtime.
And in the newer versions of the syslinux package in Debian, the
** Changed in: debian-installer (Ubuntu)
Assignee: (unassigned) = Mathieu Trudel-Lapierre (mathieu-tl)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to a duplicate bug report (1429849).
https://bugs.launchpad.net/bugs/1427821
In the jenkins automated test at
https://jenkins.qa.ubuntu.com/job/vivid-server-amd64-smoke-multi-lvm/, this
error first appears in build 86 on February 19. The test was failing with a
different and unrelated error prior to that; it's not clear to me if this is a
latent issue that was only
Public bug reported:
Crash happens irregularly, sometimes on boot, sometimes not. Error is
[Thread debugging using libthread_db enabled]
Using host libthread_db library /lib/x86_64-linux-gnu/libthread_db.so.1.
0x7f9d8453db4c in __libc_waitpid (pid=1641,
Your output shows that systemd is invoking the init script for apache2,
because there is no native systemd unit in the package. So this is not
a problem specific to systemd, the init script must be racy when running
under sysvinit as well. (And even under upstart, since apache2 has no
upstart
** Tags removed: apparmor
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to lxc in Ubuntu.
https://bugs.launchpad.net/bugs/1100877
Title:
lxc-start fails after upgrade to raring
To manage notifications about this bug go to:
So python-oauth2 has some reverse dependencies:
python-oauth2
Reverse Depends:
turses
screenlets-pack-all
python-django-social-auth
python-django-oauth-plus
turses was removed from debian in
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=779448
python-django-social-auth was removed
** Changed in: libibverbs (Ubuntu)
Assignee: Steve Langasek (vorlon) = Adam Conrad (adconrad)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libibverbs in Ubuntu.
https://bugs.launchpad.net/bugs/1364442
Title:
udaddy
** Changed in: libibverbs (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) = Steve Langasek (vorlon)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libibverbs in Ubuntu.
https://bugs.launchpad.net/bugs/1364442
Title
** Also affects: numactl (Ubuntu Trusty)
Importance: Undecided
Status: New
** Changed in: numactl (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to numactl in Ubuntu.
I agree that it doesn't make sense to block the login updating the motd
when we aren't actually going to display the motd. I'm not sure if this
should be solved in pam_motd, or in openssh - perhaps openssh should be
using different a separate PAM profile for interactive vs. non-
interactive
Here's the complete sh -xe output from running lxc-net start:
ubuntu@vivid-i386:~$ sudo sh -xe /usr/lib/i386-linux-gnu/lxc/lxc-net start
+ distrosysconfdir=/etc/default
+ localstatedir=/var
+ varrun=/run/lxc
+ USE_LXC_BRIDGE=true
+ LXC_BRIDGE=lxcbr0
+ LXC_ADDR=10.0.3.1
+ LXC_NETMASK=255.255.255.0
Public bug reported:
The lxc-net script in /usr/lib/$archtriplet/lxc/lxc-net attempts to use
ifconfig first and then falls back to trying to use ip(8) in the ifup()
and ifdown() shell functions. This behavior should be reversed, as ip
has been preferred over ifconfig for several years now.
As an
And here's the patch to the lxc-net script to prefer ip(8) over
ifconfig.
** Patch added: lxc-net-prefer_ip.patch
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1424143/+attachment/4323815/+files/lxc-net-prefer_ip.patch
--
You received this bug notification because you are a member of
So the only difference that I can see is that so *without* the added
remount rule, /proc/mounts contains the following entries for
sysfs+/sys/ within the container:
sysfs /sys sysfs rw,nosuid,nodev,noexec,relatime 0 0
sysfs /sys sysfs ro,nosuid,nodev,noexec,relatime 0 0
with the added rule,
Public bug reported:
When starting up an ubuntu lxc container in vivid, I'm seeing the
following apparmor rejection:
Feb 21 01:30:41 vivid-i386 kernel: [ 2121.606513] audit: type=1400
audit(1424511041.643:125): apparmor=DENIED operation=mount
info=failed flags match error=-13
** Changed in: maas (Ubuntu)
Importance: Undecided = Critical
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1423613
Title:
maas needs to support systemd for Ubuntu = 15.04
To
Marking this bug as critical, because it's one of two last blockers for
the switch to systemd by default in 15.04, and feature freeze is upon
us. If we don't resolve this, we will need to leave maas broken in
vivid temporarily with systemd as default.
--
You received this bug notification
I believe there had been discussion during the systemd sprint about
having maas set a boot option to continue booting upstart until the
systemd units have been written, so that this could be removed from the
critical path. But I don't see that this was captured anywhere.
--
You received this
I think I see this as well, simply doing an 'apt-get install mysql-
server-5.6' on vivid leaves things in the following state after the
installation completes:
$ sudo aa-status
[SNIP]
2 processes are unconfined but have a profile defined.
/usr/sbin/dnsmasq (665)
/usr/sbin/mysqld
= Medium
** Changed in: clamav (Ubuntu)
Assignee: (unassigned) = Steve Beattie (sbeattie)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to clamav in Ubuntu.
https://bugs.launchpad.net/bugs/1420819
Title:
ClamAV 0.98.6 security
Hi Chris,
Did you do a test build on powerpc? Even with not using llvm, I got a
build failure in the unit tests on powerpc. I'll retry the build as
sometimes things can be flaky on the powerpc buildds, but the relevant
bits from the log are as follows:
make[3]: Entering directory
Public bug reported:
Since February 2, the mysql-5.5 testsuite has been failing consistently
under autopkgtest. This appears to be caused by a bug in the test suite
that uses keys with fixed time stamps, causing problems when those
keys' expiration date is in the past.
The output in the adt
Hello Geoffrey, or anyone else affected,
Accepted samba into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/samba/2:4.1.6+dfsg-
1ubuntu2.14.04.5 in a few hours, and then in the -proposed repository.
Please help us by testing this new package.
Serge, as you've reviewed this patch, are you happy to upload this for
15.04?
** Changed in: numactl (Ubuntu)
Assignee: Taco Screen team (taco-screen-team) = Serge Hallyn
(serge-hallyn)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
Hello bugproxy, or anyone else affected,
Accepted librtas into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/librtas/1.3.13-1~14.04
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
Hello bugproxy, or anyone else affected,
Accepted librtas into utopic-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/librtas/1.3.13-1~14.10
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
This was addresses in http://www.ubuntu.com/usn/usn-2461-1/ , thanks.
** Changed in: libyaml (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libyaml in Ubuntu.
Just wanted to note that the patch in #6 has been working fine for me.
Any luck on getting it patched into Trusty?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rsync in Ubuntu.
https://bugs.launchpad.net/bugs/1300367
Title:
rsync
This config file belongs to ssh, not to pam.
** Changed in: pam (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1377924
Title:
ecryptfs
The patches are not attached to the launchpad bug via the bug proxy.
Could someone please attach them directly here?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libibverbs in Ubuntu.
https://bugs.launchpad.net/bugs/1364442
Title:
Ok. So the crucial thing shown here is that in addition to the br
interfaces, you have NetworkManager. NetworkManager sets 'nameserver
127.0.1.1', which by design will redirect DNS requests to a local
dnsmasq proxy, with dnsmasq itself picking up the configured nameservers
instead; and when set,
Readding the linux task. Chris, as Adam says there's work to be done
here to verify that no other modules are affected before regarding this
as resolved.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Tags added: regression-update
--
You received this bug
** Changed in: linux (Ubuntu)
Status: Confirmed = Invalid
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
https://bugs.launchpad.net/bugs/1379201
Title:
openvswitch-datapath-dkms 1.4.6-0ubuntu1.12.04.3:
From discussions on IRC, I believe this FFe is blocked by the
corresponding FFe on psycopg2,
https://bugs.launchpad.net/ubuntu/+source/psycopg2/+bug/1366104
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
On Tue, Sep 16, 2014 at 02:43:08PM -, Serge Hallyn wrote:
Seems like the best thing would be to move qemu-system-x86.qemu-
kvm.upstart to qemu-system-common.qemu-kvm.upstart (and same with
.default and .init) and have the jobs check for the right architectures.
Note that currently
Public bug reported:
on ppc64el, the kvm modules are not autoloaded. The qemu-system-x86
package contains an init script that loads the kvm modules for the
platform, but there is no corresponding init script for ppc64el, where
the kvm-hv module needs to be loaded.
** Affects: qemu (Ubuntu)
Yes, closing.
** Changed in: upstart (Ubuntu RTM)
Status: Triaged = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cgmanager in Ubuntu.
https://bugs.launchpad.net/bugs/1357252
Title:
upstart can race with
** Changed in: librtas (Ubuntu Utopic)
Importance: Undecided = High
** Changed in: librtas (Ubuntu Trusty)
Importance: Undecided = High
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to librtas in Ubuntu.
Note that these fixes need to get into the Ubuntu RTM distro as well.
cgmanager 0.30-1ubuntu1 is already there (https://launchpad.net/ubuntu-
rtm/+source/cgmanager), but upstart is currently at version
1.13.1-0ubuntu3 vs. 1.13.2-0ubuntu1 in utopic.
James, please get the necessary changes landed
my Kernel Version is 3.13.0-34-generic #60~precise1-Ubuntu SMP Wed Aug
13 15:57:32 UTC 2014 i686 i686 i386 GNU/Linux
after upgrading to the latest hardware enablement stack, it seems that
iscsitarget reports that the module is not found.
after trying to reinstall iscsitarget-dkms, the build
and I'm also getting this same error between rsync 3.1.0 and rsync
3.1.0, so it's not just an incompatibility between the two versions:
inflate returned -3 (0 bytes)
rsync error: error in rsync protocol data stream (code 12) at token.c(557)
[receiver=3.1.0]
rsync: [generator] write error: Broken
This also seems to be a dup of:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628#50
** Bug watch added: Debian Bug tracker #741628
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=741628
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
That does seem more appropriate than putting all the SAPI methods in
php-common. The HHVM guys (Paul Tarjan, etc) gave me the green light to
do the session cleanup bit, so I'll take care of it once we settle on a
script.
Wouldn't /usr/lib/php5/sapi/sapi be a better location for scripts?
--
You
Btw, if we go the route of separate sapi folders inside
/usr/lib/php5/sapi/ we should also move php5-fpm-checkconf into
/usr/lib/php5/sapi/fpm/ (I used fpm instead of php5-fpm here since
that how it is in /etc/php5/).
--
You received this bug notification because you are a member of Ubuntu
I prefer option #1 - sourcing the sessionclean scripts from
/usr/lib/php5/sapi/* or perhaps /usr/lib/php5/sapi/sapi/sessionclean
so we can make room for more sapi-specific scripts should the need
arise.
If we keep the logic in php-common, a con is that we can't use it for HHVM (not
that HHVM
Hello Serge, or anyone else affected,
Accepted golang-context-dev into trusty-proposed. The package will build
now and be available at http://launchpad.net/ubuntu/+source/golang-
context-dev/0.0~git20140522.1.1f3e8a4-2~ubuntu0.14.04.1 in a few hours,
and then in the -proposed repository.
Please
Indeed, I think we've passed the 80/20 mark on this one. I'll test your
updated one today and we should be good.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to php5 in Ubuntu.
https://bugs.launchpad.net/bugs/1356113
Title:
PHP5
Issue on line 8:
echo -e $SAPIS | \
The -e is ending up in the output (perhaps dash's echo has no -e) resulting
in this error:
./sessionclean: 10: [: /etc/php5/-e: unexpected operator
I've removed the -e as our input is clean anyway.
Also, I've run this to normalize the spacing:
sed -i
Thanks Ondřej, no apology needed, this was indeed a constructive thread.
Sometimes us open source geeks get all too used to being in charge and
we forget how to communicate effectively. If I'm up in your neck of the
woods some time I'll look you up and we can grab a beer :)
Also, I'll do a PR on
Thanks, this is looking better now. Here are some notes:
1. PROC_NAMES should be defined as proc_names or used as PROC_NAMES
(inconsistent case)
2. printf %s:%s:%s\n $save_path $gc_maxlifetime has 2 arguments but the
definition takes 3, I would simplify it to this:
echo
I've added HHVM support and discovered another issue along the way:
session.save_path can be empty and empty string. This is actually the
default in stock PHP and HHVM. The PHP docs imply that an empty string
is equal to /tmp
(http://php.net/manual/en/session.configuration.php#ini.session.save-
It seems likely that HHVM will find its way into the Debian repo, so I'm
going to see if they will set the session.save_path to /var/lib/php5:
https://github.com/hhvm/packaging/pull/67
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I have a feeling the CGI-mode process name is php5-cgi. I've installed
it, but I haven't been able to get Apache 2.4 and mod_actions to play
nice with it yet, so I haven't confirmed it.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
I noticed that you changed the default session.save_path to
/var/lib/php5/sessions, which I think is a great idea (I have no idea
what the modules/ dir is for).
In order to align the HHVM packaging with the Debian PHP packaging I
have some questions:
1. Will PHP 5.6 be the default in Ubuntu
[http://blog.jcole.us/2014/08/08/stupid-and-dangerous-set-global-sql_log_bin/]
suggests that there is no known use case for this command, that the only
use of the command is by mistake, causes problems and/or data loss, and
this has happened in the real world in production environments.
If
Thanks Ondřej, this is a much better script, and I agree that the lack
of session.save_path support was rather annoying. This is still not
optimal for high-performance servers, but it seems to be a good
compromise for general use. Also, the fact that is honors SAPI-specific
settings helps.
all the files it has open and touch
them.
This is more efficient than lsof since it looks only at the files open
by the SAPI in question, instead of every process. As an example,
here's the timing of my proposed way and the current way:
kamermans@steve-ubuntu:~$ time for pid in $(pidof apache2
It just occurred to me that I was timing sudo in my last post, so here
are the sudo-less numbers:
root@steve-ubuntu:~# time for pid in $(pidof apache2); do find /proc/$pid/fd
-lname /var/lib/php5/* -print -exec touch {} \; ; done
/proc/30005/fd/21
real0m0.042s
user0m0.016s
sys
Ok, sorry for the repeated spamming tonight.
One problem with the solution you linked to is that it is extracting the
gx_maxlifetime in seconds, then putting that in find's -cmin which
expects minutes.
I've attached a script that incorporates the improvements of SAPI-
specific session file
Thanks for the completely non-constructive message. Google me if you
want. Anyway, my point (and apparently your subpoint) is that the
current script is not safe for production use. My improvements make it
slightly more suitable out of the box.
--
You received this bug notification because
You can improve things even when not using the argument from
authority. I totally agree, I was just trying to make a point that I
know what I'm talking about, as opposed to being a passive observer.
You also know what you're talking about, and I can respect that as well.
If you seriously think
** Description changed:
[Impact]
A missing replaces: from rpcbind against the version of libc-bin in 12.04
means that upgrades may fail if libc-bin and rpcbind aren't unpacked in the
right order.
[Test case]
- 1. Install rpcbind on 12.04.
- 2. dist-upgrade to 14.04.
+ 1. On 12.04,
Had to revise the test case because this isn't necessarily reproducible
with a straight dist-upgrade due to arbitrary apt ordering, but I've
confirmed this fix now.
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a
Public bug reported:
The php5 file-based session cleaner script /var/lib/php5/sessionclean is
extremely expensive, taking over 10 seconds to run on my laptop, even
when no PHP file-based session storage is enabled and the system is
idle. My servers, on the other hand, are completely overwhelmed
On another note, why would we possibly need to run lsof every time we
need to cleanup sessions? This is a very inefficient and expensive
process. If someone knows how it came to be that this code was added, I
would be very curious. Also, I see that recent versions of Ubuntu
(14.04 for example)
Status: New
** Changed in: rpcbind (Ubuntu Trusty)
Importance: Undecided = High
** Changed in: rpcbind (Ubuntu Trusty)
Status: New = Triaged
** Changed in: rpcbind (Ubuntu Trusty)
Assignee: (unassigned) = Steve Langasek (vorlon)
** Changed in: rpcbind (Ubuntu)
Status: New
** Description changed:
- Received an upgrade notice. I executed the upgrade procedures which
- indicated 529 packages need to be installed. Upgrade requesrted that I
- install the DVD. of the ISO file I had downloaded. Upgrade did not
- complete and failed to reboot. I had to use recovery mode
Hello Robie, or anyone else affected,
Accepted juju-core into trusty-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/juju-core/1.18.4
+dfsg-0ubuntu0.14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
Hello Robie, or anyone else affected,
Accepted juju-core into trusty-proposed. The package will build now and
be available at http://launchpad.net/ubuntu/+source/juju-core/1.18.4
+dfsg-0ubuntu0.14.04.1 in a few hours, and then in the -proposed
repository.
Please help us by testing this new
201 - 300 of 1454 matches
Mail list logo
