[lxc-devel] [lxc/lxc] f8f560: removed shebang from bash_completion-file
GitHub
noreply at github.com
Mon Mar 3 21:23:01 UTC 2014
Branch: refs/heads/stable-1.0
Home: https://github.com/lxc/lxc
Commit: f8f560f846a463adb4935e631903afa2b5023d92
https://github.com/lxc/lxc/commit/f8f560f846a463adb4935e631903afa2b5023d92
Author: Johannes Kastl <git at ojkastl.de>
Date: 2014-03-03 (Mon, 03 Mar 2014)
Changed paths:
M config/bash/lxc.in
Log Message:
-----------
removed shebang from bash_completion-file
Signed-off-by: Johannes Kastl <git at ojkastl.de>
Acked-by: Stéphane Graber <stgraber at ubuntu.com>
Commit: 9cfdea88ffd4429fc491333f956a3df004a87639
https://github.com/lxc/lxc/commit/9cfdea88ffd4429fc491333f956a3df004a87639
Author: Serge Hallyn <serge.hallyn at ubuntu.com>
Date: 2014-03-03 (Mon, 03 Mar 2014)
Changed paths:
M src/lxc/cgmanager.c
M src/lxc/cgroup.c
M src/lxc/cgroup.h
M src/lxc/start.c
Log Message:
-----------
cgmanager: don't stay connected
There are only a few times when we need to be connected to the
cgroup manager:
* when starting a container, from cgm_init until we've set cgroup limits
* when changing a cgroup setting (while running)
* when cleaning up (when shutting down)
* around the cgroup entering at attach
So only connect/disconnect the cgmanager socket on-demand as
needed. This should have a few benefits.
1. Reduce the # open fds when many containers are running
2. if cgmanager is stopped and restarted, the container
doesn't have to deal with the disconnection.
This is currently RFC. There are a few issues outstanding:
1. the cgm_set and cgm_get may need to be made thread-safe.
2. a non-daemonized start which fails while cgm is connected,
will not disconnected.
Signed-off-by: Serge Hallyn <serge.hallyn at ubuntu.com>
Acked-by: Stéphane Graber <stgraber at ubuntu.com>
Commit: 83876d75db9c211f9e0feca0f4f7bc8812a67ba3
https://github.com/lxc/lxc/commit/83876d75db9c211f9e0feca0f4f7bc8812a67ba3
Author: S.Çağlar Onur <caglar at 10ur.org>
Date: 2014-03-03 (Mon, 03 Mar 2014)
Changed paths:
M src/lxc/bdev.c
Log Message:
-----------
use btrfs snapshot feature to restore snapshots
fixes #131
changes since v1;
* uses btrfs snapshot feature only if src and dest are on same fs
Signed-off-by: S.Çağlar Onur <caglar at 10ur.org>
Acked-by: Serge E. Hallyn <serge.hallyn at ubuntu.com>
Commit: f25ffc275c88da3b2eeb2ee14ae28d3acdfa478e
https://github.com/lxc/lxc/commit/f25ffc275c88da3b2eeb2ee14ae28d3acdfa478e
Author: Serge Hallyn <serge.hallyn at ubuntu.com>
Date: 2014-03-03 (Mon, 03 Mar 2014)
Changed paths:
M src/lxc/lxccontainer.c
Log Message:
-----------
clone: don't ever mark the clone's rootfs as being the old, on disk
Otherwise an interrupted clone can lead to the original rootfs
being delete.
There is a period during lxcapi_clone during which we have written down
a temporary configuration file on disk, for the new container, using the
old rootfs. Interruption of clone doesn't allow us to do the cleanup we
do in error paths, so a subsequent lxc-destroy removes the old rootfs.
Fix this by doing the copy_storage as early as possible, and not
writing down the rootfs when we write down the temporary configuration
file.
(note - I tested this by putting a series of
'if (strcmp(newname, "u%d") == 0) exit(1)' inline to trigger
interruption between most blocks. If someone has a good idea
for a generic way to regression-test this henceforth that'd be
great)
See https://bugs.launchpad.net/lxc/+bug/1285850
Signed-off-by: Serge Hallyn <serge.hallyn at ubuntu.com>
Acked-by: Stéphane Graber <stgraber at ubuntu.com>
Commit: 20c1b5377c6ddc41b0d9f7dcc860cbbd2a06d0e3
https://github.com/lxc/lxc/commit/20c1b5377c6ddc41b0d9f7dcc860cbbd2a06d0e3
Author: Serge Hallyn <serge.hallyn at ubuntu.com>
Date: 2014-03-03 (Mon, 03 Mar 2014)
Changed paths:
M src/lxc/conf.c
M src/lxc/utils.c
M src/lxc/utils.h
Log Message:
-----------
simpler shared rootfs handling
Only do the funky chroot_into_slave if / is in fact the rootfs.
Rootfs is a special blacklisted case for pivot_root.
If / is not rootfs but is shared, just mount / rslave. We're
already in our own namespace.
This appears to solve the extra /proc/$$/mount entries in
containers and the host directories in lxc-attach which have
been plagueing at least fedora and arch.
Signed-off-by: Serge Hallyn <serge.hallyn at ubuntu.com>
Acked-by: Stéphane Graber <stgraber at ubuntu.com>
Commit: 9a10d37ddacfabfacd994fa6fe7f1f05dfffb460
https://github.com/lxc/lxc/commit/9a10d37ddacfabfacd994fa6fe7f1f05dfffb460
Author: Stéphane Graber <stgraber at ubuntu.com>
Date: 2014-03-03 (Mon, 03 Mar 2014)
Changed paths:
M README
Log Message:
-----------
Update README to mention pkg-config and current configure
Signed-off-by: Stéphane Graber <stgraber at ubuntu.com>
Commit: 1f776f5b9502ab9891927879ec3e0fa23cc24e9f
https://github.com/lxc/lxc/commit/1f776f5b9502ab9891927879ec3e0fa23cc24e9f
Author: Stéphane Graber <stgraber at ubuntu.com>
Date: 2014-03-03 (Mon, 03 Mar 2014)
Changed paths:
M src/lxc/bdev.c
Log Message:
-----------
Fix typo I introduced in the bdev change.
When adding the missing return value in Caglar's change (as discussed on
the mailing-list), I set err = -1 instead or ret = -1, causing an
obvious build failure...
Signed-off-by: Stéphane Graber <stgraber at ubuntu.com>
Commit: d1d44d6b129e822aa1ce0ea3f1a49896aaf10cae
https://github.com/lxc/lxc/commit/d1d44d6b129e822aa1ce0ea3f1a49896aaf10cae
Author: Dwight Engen <dwight.engen at oracle.com>
Date: 2014-03-03 (Mon, 03 Mar 2014)
Changed paths:
M config/init/systemd/Makefile.am
Log Message:
-----------
fix systemd unit file location to use prefix for local installs
also remove /usr special case for non-debian distros since systemd
itself sets systemunitdir=$(rootprefix)/lib/systemd/system
Signed-off-by: Dwight Engen <dwight.engen at oracle.com>
Acked-by: Stéphane Graber <stgraber at ubuntu.com>
Commit: b57b58d44af3956c5036cfb19d635d0708c8d2bd
https://github.com/lxc/lxc/commit/b57b58d44af3956c5036cfb19d635d0708c8d2bd
Author: Serge Hallyn <serge.hallyn at ubuntu.com>
Date: 2014-03-03 (Mon, 03 Mar 2014)
Changed paths:
M src/lxc/lxccontainer.c
Log Message:
-----------
clone: don't set new containers' rootfs to the old
If clone is called from the api, the container object in memory
retains the bad fs. The line is wrong, being a leftover from a
previous attempt before copy_storage was moved earlier.
Signed-off-by: Serge Hallyn <serge.hallyn at ubuntu.com>
Compare: https://github.com/lxc/lxc/compare/496d78791d50...b57b58d44af3
More information about the lxc-devel
mailing list