Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
S
suexec
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Package Registry
Container Registry
Model registry
Operate
Environments
Terraform modules
Monitor
Incidents
Service Desk
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
silver-platter
suexec
Commits
0c02a445
Commit
0c02a445
authored
4 years ago
by
ale
Browse files
Options
Downloads
Patches
Plain Diff
Remove reference to 'log'
parent
9dbd4d12
No related branches found
No related tags found
No related merge requests found
Changes
1
Hide whitespace changes
Inline
Side-by-side
Showing
1 changed file
suexec.c
+0
-14
0 additions, 14 deletions
suexec.c
with
0 additions
and
14 deletions
suexec.c
+
0
−
14
View file @
0c02a445
...
...
@@ -572,20 +572,6 @@ int main(int argc, char *argv[])
umask
(
AP_SUEXEC_UMASK
);
#endif
/* AP_SUEXEC_UMASK */
/*
* Be sure to close the log file so the CGI can't
* mess with it. If the exec fails, it will be reopened
* automatically when log_err is called. Note that the log
* might not actually be open if AP_LOG_EXEC isn't defined.
* However, the "log" cell isn't ifdef'd so let's be defensive
* and assume someone might have done something with it
* outside an ifdef'd AP_LOG_EXEC block.
*/
if
(
log
!=
NULL
)
{
fclose
(
log
);
log
=
NULL
;
}
/*
* Execute the command, replacing our image with its own.
*/
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment