-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reading log files return blank page #23
Comments
A simple this is working for me at the moment:
|
Thanks.
Would you like to submit a Pull Request with the fix to the official GitHub
repo? https://github.com/lirantal/daloradius
…On Thu, Dec 22, 2016 at 8:10 PM, Nkansah Rexford ***@***.***> wrote:
A simple this is working for me at the moment:
if (file_get_contents($logfile)) {
$fileReversed = array_reverse(file($logfile));
foreach ($fileReversed as $line) {
echo $line . "<br>";
}
}
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#23 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AATT09cUSs4-DNOGSJpU3OURxm-GCChQks5rKr0kgaJpZM4LUN9K>
.
--
--
Sincerely, Liran Tal
Author
<http://www.amazon.com/Agile-Software-Development-HP-Manager/dp/1484210352/>of
Agile Software Development with HP Agile Manager
Founder and Lead Developer of daloRADIUS <http://www.daloradius.com/>,
MEAN.JS <https://github.com/meanjs/mean>
Open sourcing with passion on github.com/lirantal
<https://www.github.com/lirantal>
Blogging at https://medium.com/@liran.tal, and tweeting at @liran_tal
<https://twitter.com/liran_tal>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Daloradius log and Freeradius log all don't show anything. Entirely blank screen. Permission and location everything looks fine, and the log files aren't empty too.
A screenshot:
![screenshot from 2016-12-22 17-48-02](https://cloud.githubusercontent.com/assets/5289083/21435011/3b232a3e-c86f-11e6-9ae9-ec22148dd174.png)
The text was updated successfully, but these errors were encountered: