[Bug 392532] Re: apache2.2-common: /etc/init.d/apache2 script is empty

2010-02-10 Thread mattwilks
Same as Robert and zeekoe.  Found a bunch of apache2 files that looked
like they had been rotated by logrotate.  Running Ubuntu Karmic Server
with a fresh install.

# uname -a
Linux host 2.6.31-302-rs #7 SMP Thu Oct 29 22:57:03 UTC 2009 x86_64 GNU/Linux

# dpkg -l | grep apache
ii  apache2-doc   2.2.12-1ubuntu2.1
ii  apache2-mpm-prefork   2.2.12-1ubuntu2.1
ii  apache2-utils 2.2.12-1ubuntu2.1
ii  apache2.2-bin 2.2.12-1ubuntu2.1
ii  apache2.2-common  2.2.12-1ubuntu2.1
ii  libapache2-mod-php5   5.2.10.dfsg.1-2ubuntu6.4
ii  libapache2-mod-proxy-html 3.0.1-1

Can't see anything out of the ordinary in the apache entry found in the
/etc/logrotate.d directory

-- 
apache2.2-common: /etc/init.d/apache2 script is empty
https://bugs.launchpad.net/bugs/392532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 392532] Re: apache2.2-common: /etc/init.d/apache2 script is empty

2010-02-22 Thread mattwilks
My system is ext3.

-- 
apache2.2-common: /etc/init.d/apache2 script is empty
https://bugs.launchpad.net/bugs/392532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 392532] Re: apache2.2-common: /etc/init.d/apache2 script is empty

2010-02-22 Thread mattwilks
Stefan, running

logrotate -d /etc/logrotate.conf gives me:

reading config file /etc/logrotate.conf 

including /etc/logrotate.d  

reading config file apache2 

error: error accessing /var/log/apache2: No such file or directory  

error: apache2:1 glob failed for /var/log/apache2/*.log 

error: found error in /var/log/apache2/*.log , skipping 

removing last 1 log configs 

error: apache2:11 lines must begin with a keyword or a filename (possibly in 
double quotes) 
error: apache2:12 missing end of line   

reading config info for /etc/init.d/apache2 reload > /dev/null  

fi  

endscript   

}

Seems it is looking for /var/log/apache2, but the logs seem to be
installed in /var/log/apache.  If I create a symlink

ln -s /var/log/apache /var/log/apache2

and rerun the logrotate -d command, everything seems OK.  I also ran
logrotate without the -d debug switch and my apache2 init.d file was not
clobbered.  So the misnamed log directory seems to be the problem?  I
don't remember changing the name (its possible I did though) and this
was a fresh install...

-- 
apache2.2-common: /etc/init.d/apache2 script is empty
https://bugs.launchpad.net/bugs/392532
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 392420] Re: K/X/Ubuntu - Network Manager OpenVPN support NEEDS an overhaul. It should be a simple config file manager.

2009-12-11 Thread mattwilks
Matt (Trudel),

I agree with you that the GUI does provide a low level of entry for
users who are unfamiliar with VPNs.  I would argue however that setting
a bunch of configuration options in a GUI will always be more
complicated than using a configuration file provided by a VPN
administrator.  Any company/organization that is running its own VPN is
probably more likely to provide users with a customized configuration
file than a bunch of different sets of instructions on how to configure
OpenVPN for Windows/Mac/Linux.  It seems to have become almost
"standard" to write OpenVPN GUIs that act as config file managers.  Add
to his list Tunnelblick (http://www.tunnelblick.net) which takes a
similar approach.

As you mention, NetworkManager does seem to have the functionality to
import an OpenVPN configuration file.  The main problem with the
approach NetworkManager takes (from my limited understanding of what it
is doing in the import process) is that it is very hard to maintain
going forward.  Each option that OpenVPN supports has to be somehow
worked into NetworkManager's import code.  To give an example: as it
stands now (I'm trying it on Ubuntu 9.10) the OpenVPN plugin does not
recognize a configuration file that includes the keys directly in the
file with the ,  and  directives.  Those have been
supported by OpenVPN since version 2.1-beta7, released in November of
2005.

Would it not be much simpler to let NetworkManager it be a simple
configuration file manager instead?  That way, as OpenVPN changes and
progresses, the NetworkManager code does not have to be constantly
updated.  By all means, keep the GUI aspect; that can be very helpful.
But my suggestion would be to let the GUI be a front-end for writing out
a configuration file OpenVPN style.  You'd have the best of both worlds
in that case.

Hope this is helpful.

Matt

-- 
K/X/Ubuntu - Network Manager OpenVPN support NEEDS an overhaul. It should be a 
simple config file manager.
https://bugs.launchpad.net/bugs/392420
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs