Age | Commit message (Collapse) | Author |
|
|
|
In release v1.0 of unionfs-fuse, the meta directory was renamed from
.unionfs to .unionfs-fuse. Consequently, the clean up of the directory
following a commit vacuously succeeds, and the meta data remains. On a
subsequent commit, this hidden directory will be copied into the tmp
directory structure. As permissions on the whiteout files belong solely
to the user, commit actions in a multiuser environment may encounter
permission errors, leading to a failure in commit. Change the meta
directory name here to accord with the change in unionfs-fuse, but
beware that the change is reverted in release v2.0 of unionfs-fuse.
|
|
|
|
|
|
|
|
Use vyos-1x migration script runner.
|
|
|
|
|
|
|
|
|
|
|
|
the return codes?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Configurations that contain double quoted values that ended in \ were
causing parse errors on load / reboot, resulting in a failure to load
the config file and an empty config.
This commit adds extra logic to the lex parsing of the config file to
catch this particular case whilst still allowing escaped quotes in the
middle of quoted values.
Bug #593 http://bugzilla.vyos.net/show_bug.cgi?id=593
|
|
If a configuration session is exited uncleanly, either as a result of a
network disconnect / timeout or other forced quit from within config
mode, the unionfs mount is left in place. These remain until the
system is rebooted, giving an error when unmounting the config
directory.
This commit checks for old configuartion directories when a user enters
config mode, removing any found that are owned by that user but not
part of any active configuration seesion.
Bug #564 http://bugzilla.vyos.net/show_bug.cgi?id=564
|
|
|
|
When changes are made to the system by more than one user, only the
first user after a reboot is able to commit successfully, the others
fail with "Failed to generate committed config". This is caused as
a result of the underlying unionfs-fuse mount used for the system
configuration and the fact that a .unionfs directory if left in the
active configuration with permissions set such that only the original
committing user can change them.
Bug #403 http://bugzilla.vyos.net/show_bug.cgi?id=403
|
|
Use Build-iso to create /etc/fuse.conf file.
Use pipe(),fork(),execl() functions instead of system() function to
call unionfs-fuse.
|
|
|
|
|
|
|
|
1. Bugfix 8254: Show the help text first so users don't think there is
only one completion for a value when it exists with non-comps
2. Fix config mode inconsistencies with operational mode. Show all
values in help text.
3. Fix "exists_only" command handling. Only show nodes that exist when
doing completion for show, comment, and delete.
|
|
|
|
Don't fail if lock file already exists
|
|
1. Make local functions static
2. Use C standard for function with no-args versus old K&R style
3. Make some arguments const
|
|
Bug 8204
Make sure we don't handle unnecessary file descriptors to child
processes. This is done by marking file descriptors as close on
exec, and closing pipe before exec.
|
|
Bug 8192
Put message in log about failed node
|
|
|
|
This fixes some more of the memory leaks in load and commit.
Some still exist in the legacy cli_new/cli_parse code. Since that code
is supposed to be rewritten such that it interfaces with the rewritten
commit code in a clean way, these will not be fixed right now.
|
|
This fixes the biggest memory leak in the config load. There are still
a few small ones but they are not as big of a problem since the
process is ephemeral.
|
|
|
|
|
|
|
|
Incorrect use of #ifdef. Gcc major version is in __GNUC__
|
|
|
|
consistency
|
|
Bug 7188
The problem is that vyatta cfg backend is using internals of c++
templates (in std::tr1) and these will change between versions of glibc.
Workaround by adding necessary conditional compilation
|
|
|
|
|
|
|
|
|