Age | Commit message (Collapse) | Author | Files | Lines |
|
Create two new functions, ssd_kvm_open() and ssd_kvm_get_procs().
|
|
When running with «--stop» and only pid or ppid as matching options,
start-stop-daemon aborts with a "no match option" error.
«pid» and «ppid» are proper matching options, so they should be enough
to proceed.
Missed in commits 80de58344cb38ab085ca2c7808f4f7b3be1d2422 and
3fabf94e0b5fe1bcdea26fecee1c87e74fab98b2.
Closes: #763767
Signed-off-by: Guillem Jover <guillem@debian.org>
|
|
Although this got partially corrected with the fix for the background
and pidfile creation bug, it still migth happen that the parent had a
too restrictive umask.
Closes: #760222
Reported-by: Will Conley <willconley3@gmail.com>
|
|
When using the --background option combined with --make-pidfile, the
parent process might end up exiting before the child's pidfile has been
created, which might confuse service supervising programs.
Fix the race condition by making the first parent wait for the second
one, so that it can safely create the pidfile if required.
Closes: #686420
Based-on-patch-by: Nir Soffer <nirs@hyperms.com>
|
|
We'll be needing to call the former in the latter.
|
|
This requires to check the setpgid() return value in the setsid()
compatibility function.
|
|
We do not need TEST_PREFIX anymore, as the prefixes are implicit for
each typo of test case. Use the build directory for compiled programs
and the source directory for scripts.
|
|
Conflicts:
cputable
debian/changelog
|
|
Use libkvm instead of relying on linprocfs, which is not the native
procfs on kFreeBSD, and it is usually not mounted as FreeBSD programs
do not expect it to be present.
This stops making the code handle GNU/kFreeBSD as if it was a
Linux-based system.
|
|
|
|
Closes: #734452
Based-on-patch-by: Hleb Valoshka <375gnu@gmail.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
There are OpenVZ Linux kernels that instead of appending, prepend the
deleted marker, making the exec check fail to match. Add a workaround
so that those systems do not get affected.
This will still be affecting any other userland tool that checks the
/proc/PID/exe symlink, and might end up helping this behaviour to get
entrenched, but better this than the getting strange system failures.
Closes: #731530
|
|
We are performing the same search twice, let's just reuse the fs pointer
to decide if we have found the choice.
This was confusing coverity, and making it think that
alternative_has_broken_slave() could get fs with a NULL value.
Warned-by: coverity
|
|
This does not have any security implications, but it makes the code
more robust.
Warned-by: coverity
|
|
This does not have any security implications, but it makes the code
more robust.
Warned-by: coverity
|
|
This makes it possible to embed libcompat inside libdpkg, so that the
static library that we ship is self contained with the required
compatibility code, specifically the MD5 functions.
This also prepares the build system for when we start building a
shared library, although it disables it by default.
Closes: #746122
|
|
Conflicts:
debian/changelog
utils/start-stop-daemon.c
|
|
This might happen if the executable pathname is longer than
_POSIX_PATH_MAX. Although this should not have security implications
as the buffer is surrounded by two arrays (so those catch accesses
even if the stack grows up or down), and we are compiling with
-fstack-protector anyway.
We just need to always leave room for the final NUL character.
Warned-by: coverity
|
|
Free prio_str and master_file.
Warned-by: coverity
|
|
This allows to check for processes with a specific parent PID.
Suggested-by: Alex Mestiashvili <mailatgoogl@gmail.com>
|
|
Instead of hardcoding their usage depending on system macros.
|
|
|
|
|
|
Use the KERN_PROC_PATHNAME sysctl interface to retrieve the process
pathname. This will allow to stop requiring the linprocfs fileystem
which is not the native procfs and is not usually mounted by default
anyway.
This still has the problem that the pathname cannot be retrieved when
the inode has been unlinked, in the same way as when accessing the
/proc/<PID>/exe symlink from linprocfs.
|
|
|
|
This uses the traditional BSD kinfo_proc layout.
|
|
|
|
|
|
This trades parsing ambiguities due to process names with ‘)’ for ones
with embedded ‘\n’. But it should be more robust and future proof in
general, and allows to retrieve any field by name, which makes the code
more clear and reusable.
|
|
This stops the madness of having to invent sequence numbers to be able
to order the test suite run. Instead we now honour the order of the
arguments passed to the runner.
|
|
The original name was confusing with Makefile.am, let's be more clear.
|
|
Conflicts:
debian/changelog
debian/rules
dpkg-deb/build.c
man/dpkg-deb.1
scripts/Dpkg/Shlibs.pm
scripts/Dpkg/Shlibs/SymbolFile.pm
|
|
|
|
|
|
|
|
This option is useful when the user knows the pid of the process to act
on, and wants to use some of the features from s-s-d, w/o needing to
create a fake pid file.
Closes: #253265
|
|
Return the correct slave link from alternative_add_slave(), instead of
the typoed sl variable.
Regression introduced in commit 9bbdca83fa1a8c817a2f8d02db493f173435a5af.
Closes: #731710
Reported-by: Julian Andres Klode <jak@debian.org>
Tested-by: Julian Andres Klode <jak@debian.org>
Tested-by: Roland Stigge <stigge@debian.org>
|
|
|
|
|
|
|
|
Make it obvious the 0 passed to alternative_print_choice() is the idx,
and move the increment in the for loop into the post action.
|
|
|
|
Instead of computing them on every loop, do so only once before entering
the loop.
|
|
Although we are still using dpkg specific file extensions for the temp
files, it's one step further in untangling it from dpkg.
|