AwStats plugin for DA [Still in BETA]

Well, just giving you ideas. Most times its just a simple thing that you overlooked. Did you try the rm -rf command to try force the removal of it? As root you should be able to get rid of everything you want to no matter who the owner is.
 
Last edited:
Had to do a rm -d -R awstats

and Y to every file!!!!!

Thanks for trying!!!!! seriously!!!!! no sarcasm i swear!!! text can come off wrong sometimes!
 
That did the trick too... used it in my ftp directory!!!

thanks i will have to remember that one!!!! its alot quicker then the way i did it as seen above!
 
last question!!!


I can't protect the link through tuning?!?!?!!?

one of my users noticveed that for me and is a little concerned. I guess i could protect the directory through file manager but thats a extra step that he will not like so much. I read the entire post, what did i look over or miss?
 
Could you look in the public_html/awstats dir from a site you try to protect for a file named .htaccess ?

with a ls -la you can list the dir for . (hidden) files. (ssh offcourse ;))

and check if the location of the password file is correct ?
 
this is what i got

-rw-r--r-- 1 freddyv freddyv 43 Aug 17 22:34 .htaccess

in root of awstats

where should it be?
 
If you insist on belittling people who try to help you, you'll soon find no one will help you.

If you want to remove a directory, and you don't care what's in it, as root...

First navigate to the directory that contains the directory you want to delete.

Then do this:

# rm -Rf directoryname

where directoryname is the name of the directory you want to delete.

If that doesn't work, then do:

ls -ald directoryname

and post the output.

Jeff
 
jlasman said:
If you insist on belittling people who try to help you, you'll soon find no one will help you.

If you want to remove a directory, and you don't care what's in it, as root...

First navigate to the directory that contains the directory you want to delete.

Then do this:

# rm -Rf directoryname

where directoryname is the name of the directory you want to delete.

If that doesn't work, then do:

ls -ald directoryname

and post the output.

Jeff

im going to let that slide!!!! i never belittled anyone!

thanks for the info!!

peace
 
vincenzobar said:
this is what i got

-rw-r--r-- 1 freddyv freddyv 43 Aug 17 22:34 .htaccess

in root of awstats

where should it be?

Open up the file and look to the .passwd path and check if this file exists. Normaly you should already get a popup for this domain, even if the .passwd isn't found I thought
 
this is all thats in my .htaccess file

Options +ExecCGI
DirectoryIndex awstats.pl


nothing else
 
Updated v0.9.2

- fixed password protection problems (tune awstats)



In reply:

The password couldn't be altered/set due to a fault in converting the password to .htpasswd password format.

The problem is now fixed.



Thx for your support ;)
 
Hey,

Script works great, but I am having problem ONLY with one domain. Here is what I am getting:

Checking if there is already something installed..
AwStats Directory already exists on domain
Checking if awstats files are available...
Checking for AwStats itself
Awstats already exists.
(Re-)Activating CGI for dir
(Re-)Setting permissions
Now (re-)creating your configuration file.
Warning: symlink(): File exists in /usr/local/directadmin/plugins/awstats/user/index.html on line 77 Config file has been created and your statistics are now setup!

You can now view the statistics for your domain at: www.my_domain.com/awstats/

Is it because I have two domains on one account?
Also, other domain's stats are working fine.


______________________________
also, I forgot to mention that when i go to my_domain.com/awstats/ I am getting Internal Server Error



Thanks,
Kamsel
 
Make sure the awstats permisions are set to username:username and not username:apache

I ran into this problem because of that. The installation script does not change the file permissions if the directory already exists.

It may be a good idea to have it do it anyway fusionictnl in case of a similar problem. Or a check that will make sure its set correctly.
 
Hum, weird.

On one server I got a message saying that my log-format isn't OK but on the other one it's perfect.

:confused:
 
Back
Top