Here's a first attempt:
https://github.com/lxc/lxc-pkg-ubuntu/pull/2
--
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/1389954
Title:
Make .lxc domain name resolution easier to discover
Okay, I've written up a short README.Debian describing the necessary
changes to /etc/default/lxc-net and the dnsmasq config file. I don't
remember what steps are necessary to make the domain names accessible,
though, and I'd like to include those steps in the readme.
Do I have to restart the
Which branch?
--
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/1389954
Title:
Make .lxc domain name resolution easier to discover and enable
To manage notifications about this bug go
Sure. Is this the right place?
https://github.com/lxc/lxc-pkg-ubuntu
--
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/1389954
Title:
Make .lxc domain name resolution easier to discover
Thanks for taking an interest in the issue.
Since I filed this specifically against lxc in Ubuntu, wouldn't it make
sense to start by documenting the necessary config changes (including
NetworkManager's dnsmasq config, since it is part of Ubuntu by default)
in /usr/share/doc/lxc/README?
--
You
Public bug reported:
The lxc package installs dnsmasq configuration as
/etc/dnsmasq.d-available/lxc, and a symlink to it is created at
/etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq
instance on systems running NetworkManager, because NetworkManager
starts a dnsmasq instance
** Description changed:
The lxc package installs dnsmasq configuration as
/etc/dnsmasq.d-available/lxc, and a symlink to it is created at
/etc/dnsmasq.d/lxc, but neither has any effect on the main dnsmasq
instance on systems running NetworkManager, because NetworkManager
starts a
Public bug reported:
The lxc package on ubuntu does almost nothing to help a user enable DNS
resolution for containers via dnsmaq, let alone discover that it is
possible. How about enabling it by default? I think all it would take is
adding server=/lxc/10.0.3.1 to a file in
Sure. The part that stood out to me was refreshes secondary IP
addresses during DHCP lease renewal. I haven't examined Amazon's code,
but that description reads like it solves the problem of automatically
configuring additional IP addresses without requiring additional network
interfaces.
--
I'm in a similar situation: An ec2 instance with just one network
interface, to which I have assigned a secondary IP address.
This bit from the AWS docs is interesting:
If you are using Amazon Linux, the ec2-net-utils package can take care
of this step for you. It configures additional network
See also https://bugs.launchpad.net/ubuntu/+source/libjpeg-
turbo/+bug/1189939
--
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/1177684
Title:
php5-gd doesn't close /proc/NN/auxv -
Hi, i spent lots of time to get this brcompat module loaded but all
failed on Ubuntu12.10.
Is anybody still working on this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openvswitch in Ubuntu.
** Also affects: rabbitmq-server (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to rabbitmq-server in Ubuntu.
https://bugs.launchpad.net/bugs/833073
Title:
oneiric gdm picker list
This was seen on Ubuntu Maverick just a week or two ago.
** Changed in: apache2 (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
https://bugs.launchpad.net/bugs/795315
Title:
Public bug reported:
Binary package hint: apache2
After enabling ssl on my apache2 installation, doing an apache2 reload
or restart produces messages like this in the error log:
SSL Library Error: 336027900 error:140760FC:SSL
routines:SSL23_GET_CLIENT_HELLO:unknown protocol speaking not SSL to
** Patch added: put-listen-80-last.patch
https://bugs.launchpad.net/bugs/795315/+attachment/2163048/+files/put-listen-80-last.patch
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to apache2 in Ubuntu.
smbnetfs has the same problem, and the developer already has a fix in
testing.
http://sourceforge.net/tracker/?func=detailatid=857137aid=2492545group_id=171223
** Bug watch added: SourceForge.net Tracker #2492545
http://sourceforge.net/support/tracker.php?aid=2492545
--
fusesmb - Not
Does fix released mean that something was changed in an upcoming samba
release such that sec=none is no longer required for guest connections?
Or, will we have to use sec=none forever?
--
cifs doesn't support connecting as guest
https://bugs.launchpad.net/bugs/98658
You received this bug
This bug might be related:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/98658
If you're trying to mount a share using guest access, see if the
sec=none option works around the failure.
--
'mount error 13 = Permission denied' when user mounts cifs (sudo works!)
I don't see smbnetfs or fusesmb in your ppa. What would you like us to
try, and what's different between it and the official version?
--
crashing with SIGABRT while scanning network or reading some files
https://bugs.launchpad.net/bugs/293233
You received this bug notification because you are a
Bug 293233 contains a SIGABRT backtrace which might be the same crash
we're seeing here.
** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You received this bug notification because you are a
** Bug watch added: Samba Bugzilla #5847
https://bugzilla.samba.org/show_bug.cgi?id=5847
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=5847
Importance: Unknown
Status: Unknown
--
crashing with SIGABRT while scanning network or reading some files
** Bug watch added: Samba Bugzilla #5847
https://bugzilla.samba.org/show_bug.cgi?id=5847
** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=5847
Importance: Unknown
Status: Unknown
--
fusesmb - Not working properly.
https://bugs.launchpad.net/bugs/198351
You
Tying together more related bug reports...
(Debian 503038 and Samba 5847 contain some enlightening comments from
the smbnetfs and samba developers)
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=503038
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=497572
24 matches
Mail list logo