Problem with working directory in destructor in php
and found that there is only start in log.log and no finish. After clearing the contents in the log, modify the program: unset($test); Sure enough, there was a start and a finish. It seems that __destruct will be executed only after unset. But the matter is not over yet. I modified the program again, changed the __destruct function, and deleted the unset code:
At this time, 'finish' was actually printed on the screen, which proved that the destructor was indeed executed. After being puzzled, I started looking for information on the Internet and saw that error_log was used in the destructor of a friend and was executed. The difference from my usage is that he did not specify the error_log file, but set it to the default log file, so I simulated it and modified my program:
I found that the log.log still started after start, but there was no finish. And E:AppServApache2.2logserror.log (the default log file of my apache configuration) really has start and finish. It was a strange question and I couldn’t figure it out, so I went to the group to ask. My friends in the group either asked me to check for syntax errors or to check file permissions. I made sure there were no problems with these two. I said, "There is no permission problem in the Windows system. It is definitely not caused by this." A group friend said: "windos system, no explanation!" I said: "This must have nothing to do with the system. I suspect it is an apache problem." So I restored the _log and ran it on the linux+nginx virtual machine.
log.log and start and finish are successfully written. This makes me doubt my judgment even more: it’s caused by apache So I struggled for an hour, installed apache on the server and ran the file. Still the same result, finish was not successfully written. At this time, a colleague told me, try writing an absolute path, so I modified another _log
Look at it again and write "finish" successfully. I'm so excited. I finally found the problem. I modified the program again.
It turns out that the destructor of apache will change the directory of the current program, so if you use a relative directory, the corresponding file will not be found, and the writing will of course fail. Learning a language is not easy, it pays to practice more.
|

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

Video Face Swap
Swap faces in any video effortlessly with our completely free AI face swap tool!

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics

Alipay PHP...

JWT is an open standard based on JSON, used to securely transmit information between parties, mainly for identity authentication and information exchange. 1. JWT consists of three parts: Header, Payload and Signature. 2. The working principle of JWT includes three steps: generating JWT, verifying JWT and parsing Payload. 3. When using JWT for authentication in PHP, JWT can be generated and verified, and user role and permission information can be included in advanced usage. 4. Common errors include signature verification failure, token expiration, and payload oversized. Debugging skills include using debugging tools and logging. 5. Performance optimization and best practices include using appropriate signature algorithms, setting validity periods reasonably,

Session hijacking can be achieved through the following steps: 1. Obtain the session ID, 2. Use the session ID, 3. Keep the session active. The methods to prevent session hijacking in PHP include: 1. Use the session_regenerate_id() function to regenerate the session ID, 2. Store session data through the database, 3. Ensure that all session data is transmitted through HTTPS.

The enumeration function in PHP8.1 enhances the clarity and type safety of the code by defining named constants. 1) Enumerations can be integers, strings or objects, improving code readability and type safety. 2) Enumeration is based on class and supports object-oriented features such as traversal and reflection. 3) Enumeration can be used for comparison and assignment to ensure type safety. 4) Enumeration supports adding methods to implement complex logic. 5) Strict type checking and error handling can avoid common errors. 6) Enumeration reduces magic value and improves maintainability, but pay attention to performance optimization.

The application of SOLID principle in PHP development includes: 1. Single responsibility principle (SRP): Each class is responsible for only one function. 2. Open and close principle (OCP): Changes are achieved through extension rather than modification. 3. Lisch's Substitution Principle (LSP): Subclasses can replace base classes without affecting program accuracy. 4. Interface isolation principle (ISP): Use fine-grained interfaces to avoid dependencies and unused methods. 5. Dependency inversion principle (DIP): High and low-level modules rely on abstraction and are implemented through dependency injection.

How to debug CLI mode in PHPStorm? When developing with PHPStorm, sometimes we need to debug PHP in command line interface (CLI) mode...

How to automatically set the permissions of unixsocket after the system restarts. Every time the system restarts, we need to execute the following command to modify the permissions of unixsocket: sudo...

Sending JSON data using PHP's cURL library In PHP development, it is often necessary to interact with external APIs. One of the common ways is to use cURL library to send POST�...
