shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2024-11-02 19:21:53 +03:00
Code
70b6ee6110
systemd/test/fuzz/fuzz-unit-file/directives.service

348 lines
5.6 KiB
SYSTEMD
Raw Normal View History

fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
service
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
[Unit]
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
After=
AllowIsolate=
AssertACPower=
AssertArchitecture=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
AssertCPUs=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
AssertCapability=
AssertControlGroupController=
AssertDirectoryNotEmpty=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
AssertEnvironment=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
AssertFileIsExecutable=
AssertFileNotEmpty=
AssertFirstBoot=
AssertGroup=
AssertHost=
AssertKernelCommandLine=
AssertKernelVersion=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
AssertMemory=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
AssertNeedsUpdate=
AssertPathExists=
AssertPathExistsGlob=
AssertPathIsDirectory=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
AssertPathIsEncrypted=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
AssertPathIsMountPoint=
AssertPathIsReadWrite=
AssertPathIsSymbolicLink=
AssertSecurity=
AssertUser=
AssertVirtualization=
fuzz: add BPFProgram= to directives
2020-12-22 20:27:14 +03:00
BPFProgram=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
Before=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
BindTo=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
BindsTo=
CollectMode=
ConditionACPower=
ConditionArchitecture=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ConditionCPUs=
Add support for conditions on the machines firmware This allows to limit units to machines that run on a certain firmware type. For device tree defined machines checking against the machine's compatible is also possible.
2020-10-09 13:13:00 +03:00
ConditionFirmware=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ConditionCapability=
ConditionControlGroupController=
ConditionDirectoryNotEmpty=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ConditionEnvironment=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ConditionFileIsExecutable=
ConditionFileNotEmpty=
ConditionFirstBoot=
ConditionGroup=
ConditionHost=
ConditionKernelCommandLine=
ConditionKernelVersion=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ConditionMemory=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ConditionNeedsUpdate=
ConditionPathExists=
ConditionPathExistsGlob=
ConditionPathIsDirectory=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ConditionPathIsEncrypted=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ConditionPathIsMountPoint=
ConditionPathIsReadWrite=
ConditionPathIsSymbolicLink=
ConditionSecurity=
ConditionUser=
ConditionVirtualization=
Conflicts=
DefaultDependencies=
Description=
Documentation=
FailureAction=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
FailureActionExitStatus=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
IgnoreOnIsolate=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
IgnoreOnSnapshot=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
JobRunningTimeoutSec=
JobTimeoutAction=
JobTimeoutRebootArgument=
JobTimeoutSec=
JoinsNamespaceOf=
OnFailure=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
OnFailureIsolate=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
OnFailureJobMode=
core: add new OnSuccess= dependency type This is similar to OnFailure= but is activated whenever a unit returns into inactive state successfully. I was always afraid of adding this, since it effectively allows building loops and makes our engine Turing complete, but it pretty much already was it was just hidden. Given that we have per-unit ratelimits as well as an event loop global ratelimit I feel safe to add this finally, given it actually is useful. Fixes: #13386
2021-04-14 15:36:15 +03:00
OnSuccess=
OnSuccessJobMode=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
PartOf=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
PropagateReloadFrom=
PropagateReloadTo=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
PropagatesReloadTo=
core: add new PropagateStopTo= dependency (and inverse) This takes inspiration from PropagatesReloadTo=, but propagates stop jobs instead of restart jobs. This is defined based on exactly two atoms: UNIT_ATOM_PROPAGATE_STOP + UNIT_ATOM_RETROACTIVE_STOP_ON_STOP. The former ensures that when the unit the dependency is originating from is stopped based on user request, we'll propagate the stop job to the target unit, too. In addition, when the originating unit suddenly stops from external causes the stopping is propagated too. Note that this does *not* include the UNIT_ATOM_CANNOT_BE_ACTIVE_WITHOUT atom (which is used by BoundBy=), i.e. this dependency is purely about propagating "edges" and not "levels", i.e. it's about propagating specific events, instead of continious states. This is supposed to be useful for dependencies between .mount units and their backing .device units. So far we either placed a BindsTo= or Requires= dependency between them. The former gave a very clear binding of the to units together, however was problematic if users establish mounnts manually with different block device sources than our configuration defines, as we there might come to the conclusion that the backing device was absent and thus we need to umount again what the user mounted. By combining Requires= with the new StopPropagatedFrom= (i.e. the inverse PropagateStopTo=) we can get behaviour that matches BindsTo= in every single atom but one: UNIT_ATOM_CANNOT_BE_ACTIVE_WITHOUT is absent, and hence the level-triggered logic doesn't apply. Replaces: #11340
2021-04-13 23:30:31 +03:00
PropagatesStopTo=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
RebootArgument=
RefuseManualStart=
RefuseManualStop=
ReloadPropagatedFrom=
Requires=
RequiresMountsFor=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
RequiresOverridable=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
Requisite=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
RequisiteOverridable=
fuzz: add SocketBind{Allow|Deny}= directive
2021-02-12 10:15:17 +03:00
SocketBindAllow=
SocketBindDeny=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
SourcePath=
StartLimitAction=
StartLimitBurst=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
StartLimitInterval=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
StartLimitIntervalSec=
StopWhenUnneeded=
core: add new PropagateStopTo= dependency (and inverse) This takes inspiration from PropagatesReloadTo=, but propagates stop jobs instead of restart jobs. This is defined based on exactly two atoms: UNIT_ATOM_PROPAGATE_STOP + UNIT_ATOM_RETROACTIVE_STOP_ON_STOP. The former ensures that when the unit the dependency is originating from is stopped based on user request, we'll propagate the stop job to the target unit, too. In addition, when the originating unit suddenly stops from external causes the stopping is propagated too. Note that this does *not* include the UNIT_ATOM_CANNOT_BE_ACTIVE_WITHOUT atom (which is used by BoundBy=), i.e. this dependency is purely about propagating "edges" and not "levels", i.e. it's about propagating specific events, instead of continious states. This is supposed to be useful for dependencies between .mount units and their backing .device units. So far we either placed a BindsTo= or Requires= dependency between them. The former gave a very clear binding of the to units together, however was problematic if users establish mounnts manually with different block device sources than our configuration defines, as we there might come to the conclusion that the backing device was absent and thus we need to umount again what the user mounted. By combining Requires= with the new StopPropagatedFrom= (i.e. the inverse PropagateStopTo=) we can get behaviour that matches BindsTo= in every single atom but one: UNIT_ATOM_CANNOT_BE_ACTIVE_WITHOUT is absent, and hence the level-triggered logic doesn't apply. Replaces: #11340
2021-04-13 23:30:31 +03:00
StopPropagatedFrom=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
SuccessAction=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
SuccessActionExitStatus=
core: implement Uphold= dependency type This is like a really strong version of Wants=, that keeps starting the specified unit if it is ever found inactive. This is an alternative to Restart= inside a unit, acknowledging the fact that whether to keep restarting the unit is sometimes not a property of the unit itself but the state of the system. This implements a part of what #4263 requests. i.e. there's no distinction between "always" and "opportunistic". We just dumbly implement "always" and become active whenever we see no job queued for an inactive unit that is supposed to be upheld.
2021-04-14 16:24:08 +03:00
Upholds=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
Wants=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
[Install]
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
Alias=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
Also=
DefaultInstance=
RequiredBy=
WantedBy=
[Service]
AllowedCPUs=
AllowedMemoryNodes=
AmbientCapabilities=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
AppArmorProfile=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
BindPaths=
BindReadOnlyPaths=
BlockIOAccounting=
BlockIODeviceWeight=
BlockIOReadBandwidth=
BlockIOWeight=
BlockIOWriteBandwidth=
BusName=
BusPolicy=
CPUAccounting=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
CPUAffinity=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
CPUQuota=
CPUQuotaPeriodSec=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
CPUSchedulingPolicy=
CPUSchedulingPriority=
CPUSchedulingResetOnFork=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
CPUShares=
CPUWeight=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
CacheDirectory=
CacheDirectoryMode=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
Capabilities=
CapabilityBoundingSet=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ConfigurationDirectory=
ConfigurationDirectoryMode=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
CoredumpFilter=
DefaultMemoryLow=
DefaultMemoryMin=
Delegate=
DeviceAllow=
DevicePolicy=
DisableControllers=
DynamicUser=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
Environment=
EnvironmentFile=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ExecCondition=
ExecPaths=
ExecReload=
ExecStart=
ExecStartPost=
ExecStartPre=
ExecStop=
ExecStopPost=
ExitType=
ExtensionImages=
FailureAction=
FileDescriptorStoreMax=
FinalKillSignal=
Group=
GuessMainPID=
IOAccounting=
IODeviceLatencyTargetSec=
IODeviceWeight=
IOReadBandwidthMax=
IOReadIOPSMax=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
IOSchedulingClass=
IOSchedulingPriority=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
IOWeight=
IOWriteBandwidthMax=
IOWriteIOPSMax=
IPAccounting=
IPAddressAllow=
IPAddressDeny=
IPCNamespacePath=
IPEgressFilterPath=
IPIngressFilterPath=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
IgnoreSIGPIPE=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
InaccessibleDirectories=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
InaccessiblePaths=
KeyringMode=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
KillMode=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
KillSignal=
LimitAS=
LimitCORE=
LimitCPU=
LimitDATA=
LimitFSIZE=
LimitLOCKS=
LimitMEMLOCK=
LimitMSGQUEUE=
LimitNICE=
LimitNOFILE=
LimitNPROC=
LimitRSS=
LimitRTPRIO=
LimitRTTIME=
LimitSIGPENDING=
LimitSTACK=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
LoadCredential=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
LockPersonality=
LogExtraFields=
LogLevelMax=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
LogNamespace=
core: implement per unit journal rate limiting Add LogRateLimitIntervalSec= and LogRateLimitBurst= options for services. If provided, these values get passed to the journald client context, and those values are used in the rate limiting function in the journal over the the journald.conf values. Part of #10230
2018-10-08 06:28:36 +03:00
LogRateLimitBurst=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
LogRateLimitIntervalSec=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
LogsDirectory=
LogsDirectoryMode=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ManagedOOMMemoryPressure=
ManagedOOMMemoryPressureLimit=
ManagedOOMPreference=
ManagedOOMSwap=
MemoryAccounting=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
MemoryDenyWriteExecute=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
MemoryHigh=
MemoryLimit=
MemoryLow=
MemoryMax=
MemoryMin=
MemorySwapMax=
MountAPIVFS=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
MountFlags=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
MountImages=
NUMAMask=
NUMAPolicy=
NetClass=
NetworkNamespacePath=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
Nice=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
NoExecPaths=
main: add NoNewPrivileges config option (#8475) This makes it possible to disable new privileges for the whole system.
2018-03-22 01:41:19 +03:00
NoNewPrivileges=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
NonBlocking=
NotifyAccess=
OOMPolicy=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
OOMScoreAdjust=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
PAMName=
PIDFile=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
PassEnvironment=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
PermissionsStartOnly=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
Personality=
PrivateDevices=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
PrivateIPC=
PrivateMounts=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
PrivateNetwork=
PrivateTmp=
PrivateUsers=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ProcSubset=
ProtectClock=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ProtectControlGroups=
ProtectHome=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ProtectHostname=
ProtectKernelLogs=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ProtectKernelModules=
ProtectKernelTunables=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ProtectProc=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ProtectSystem=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ReadOnlyDirectories=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ReadOnlyPaths=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
ReadWriteDirectories=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
ReadWritePaths=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
RebootArgument=
RemainAfterExit=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
RemoveIPC=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
Restart=
RestartForceExitStatus=
RestartKillSignal=
RestartPreventExitStatus=
RestartSec=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
RestrictAddressFamilies=
RestrictNamespaces=
RestrictRealtime=
core: expose SUID/SGID restriction as new unit setting RestrictSUIDSGID=
2019-03-20 21:09:09 +03:00
RestrictSUIDSGID=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
RootDirectory=
RootDirectoryStartOnly=
RootHash=
RootHashSignature=
RootImage=
RootImageOptions=
RootVerity=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
RuntimeDirectory=
RuntimeDirectoryMode=
RuntimeDirectoryPreserve=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
RuntimeMaxSec=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
SELinuxContext=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
SecureBits=
SendSIGHUP=
SendSIGKILL=
SetCredential=
Slice=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
SmackProcessLabel=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
Sockets=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
StandardError=
StandardInput=
StandardInputData=
StandardInputText=
StandardOutput=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
StartLimitAction=
StartLimitBurst=
StartLimitInterval=
StartupBlockIOWeight=
StartupCPUShares=
StartupCPUWeight=
StartupIOWeight=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
StateDirectory=
StateDirectoryMode=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
SuccessExitStatus=
SupplementaryGroups=
SysVStartPriority=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
SyslogFacility=
SyslogIdentifier=
SyslogLevel=
SyslogLevelPrefix=
SystemCallArchitectures=
SystemCallErrorNumber=
SystemCallFilter=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
SystemCallLog=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
TTYPath=
TTYReset=
TTYVHangup=
TTYVTDisallocate=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
TasksAccounting=
TasksMax=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
TemporaryFileSystem=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
TimeoutAbortSec=
TimeoutCleanSec=
TimeoutSec=
TimeoutStartFailureMode=
TimeoutStartSec=
TimeoutStopFailureMode=
TimeoutStopSec=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
TimerSlackNSec=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
Type=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
UMask=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
USBFunctionDescriptors=
USBFunctionStrings=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
UnsetEnvironment=
User=
UtmpIdentifier=
UtmpMode=
test: check if the unit file fuzzer corpora is up to date This follows a similar pattern we already have in place for networkd-related directives.
2021-04-02 20:51:44 +03:00
WatchdogSec=
WatchdogSignal=
fuzz-unit-file: add a dump of systemd.directives(7) as a corpus entry $ ( echo service; man systemd.directives|grep =|grep -v -e --|sed 's/ //g' ) >> test/fuzz-corpus/unit-file/directives.service
2018-03-11 14:36:19 +03:00
WorkingDirectory=
Copy Permalink