Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - poundjd

Pages: 1 2 3 [4] 5 6 ... 13

Installation and Upgrades / Re: A really nasty bug has occurred
« on: July 18, 2009, 08:31:46 pm »
that's true, you can't read my mind, but it is very empty most of the time.....

I installed 1.2 from the new installer, and installed all packages. when to the browser and started checking out the DashBoard.  Well seams that many of the links on left are not loaded or won't load and about the third one produced this.  I can reproduce this fairly easily.  It occurs frequently when I click on any of the left side links that don't load into the browser, See my ohter post yesterday.  I'm thinking that something terriable when wrong, but I have loaded this box up 3 times and have consistent results.  I am going to try it with only one big partition and see if having /var on XFS and / on ext3 could be a contributing factor.  My partitions were /, /home, /boot - ext3, /swap - swap, /var, /vmail -XFS. Reasonable sizes all.

I clicked on System in the dashboard and this is what I got.
Page not found(show help) (hide help)
we're sorry
The page cannot be found
If you typed the URL manually, please check it
Maybe a change in eBox's configuration or software made no longer available the requested page
If you need more help, you may want visit eBox's homepage for documentation and mailing lists
I also get it when clicking on the Network, & Logs, and when I clicked on the Software Management I get a really Nasty bug report that I filed earlier.

Installation and Upgrades / A really nasty bug has occurred
« on: July 18, 2009, 04:08:59 am »
Guys, I don't remember how I got this but get it I did.
A really nasty bug has occurred
One composite element is given and slashes are given. The valid format requires no slashes
One composite element is given and slashes are given. The valid format requires no slashes at /usr/share/perl5/EBox/Model/ line 118
EBox::Model::CompositeManager::composite('EBox::Model::CompositeManager=HASH(0xab8e950)', '/events/') called at /usr/share/perl5/EBox/CGI/ line 201
EBox::CGI::Run::lookupModel('EBox::CGI::Events::Composite') called at /usr/share/perl5/EBox/CGI/ line 226
EBox::CGI::Run::_lookupViewController('EBox::CGI::Events::Composite', 'EBox') called at /usr/share/perl5/EBox/CGI/ line 96
EBox::CGI::Run::run('EBox::CGI::Run', 'Events/Composite/', 'EBox') called at /usr/share/ebox/cgi/ebox.cgi line 19
ModPerl::ROOT::ModPerl::Registry::usr_share_ebox_cgi_ebox_2ecgi::handler('Apache2::RequestRec=SCALAR(0xb544d04)') called at /usr/lib/perl5/ModPerl/ line 204
eval {...} called at /usr/lib/perl5/ModPerl/ line 204
ModPerl::RegistryCooker::run('ModPerl::Registry=HASH(0xb55e104)') called at /usr/lib/perl5/ModPerl/ line 170
ModPerl::RegistryCooker::default_handler('ModPerl::Registry=HASH(0xb55e104)') called at /usr/lib/perl5/ModPerl/ line 31
ModPerl::Registry::handler('ModPerl::Registry', 'Apache2::RequestRec=SCALAR(0xb544d04)') called at -e line 0
eval {...} called at -e line 0

you know if someone could post a single web page with all of the Spanish documentation somewhere, i could then translate it all at one time.

The problem with this is that formating is not preserved in the text files that are saved.  It does look the same on the webpage but what you can cut and past to a document has no formating information.

So if the documentation set was in a single webpage, we would translate it useing google, then proof it and start building the formated documentation from that text base.  This would greatly improve the process I think.

Post back with your comments

Guys, I installed Google's "Google Toolbar" for IE and with it I can click on a button and it is translated into English (My language) I have been reading the postings in the Spanish forum for the last few days and it is not perfect but it is quite workable.

 I followed the link to the document and web page while the translation was not always perfect English it was quite readable and would only take a little proof reading to be ready to post. I was quite amazed by it. Give it a try!

I translated the page and saved the text.  it is attached.

Installation and Upgrades / Re: anti-spam tweaks
« on: July 10, 2009, 04:34:57 am »
Now What we need is for someone to document a HOWTO so that we can set up our home NON-STATIC IP email servers the right way so that our e-mail gets through...

So we need DDNS - which version 1.2 will have - cool  Now we can associate our PUBLIC DOMAIN to our IP,

I know that we need a PUBLIC DNS MX record, and what do we need to get the reverse-ip lookup to work?
What else am I missing here?

Or is the answer to use Google's free service {where they host your DOMAIN on their e-mail servers}, I'd rather not!  but I need for my e-mail to get through,  Maybe I'll have to pony up the extra $$ for a Static IP.... Please no.

Installation and Upgrades / Re: DNS on local ebox machine
« on: July 08, 2009, 04:38:57 am »
Please note that if you change an configuration file that eBox overwrites, it will  get over written every time eBox thinks a change or restart may be needed. - that's a pain, there is a solution.

Each file that eBox overwrites has a TEMPLATE file that it uses to make the configuration file.  This template file is named the same as the configuration file with a .mas added to the end of it.

so if you make this change to the resolv.conf.mas file your change remain in effect until you upgrade eBox and that file gets overwritten.

NOT Stupid, only human, like the rest of us.

logging activities of all users and accounts is one of the first steps taken to help insure some level of security.  Reviewing those logs by an independent third party is the second.  with out this any system can hacked with out anyone knowing it...- much worse to trust a hacked system than to be a little paranoid....
welcome to the world of Information Assureance....

It is not paranoia if someone IS out to get you.....


I would suggest that it be a configuration option on a per user basis that defaults to OFF>>>>

Installation and Upgrades / Re: resolv.conf not updating
« on: June 22, 2009, 05:23:09 am »
     In eBox every time a module is started, eBox tells all of the other modules in eBox that may have their configuration changed by any changes in that modules configuration files.  So all the eBox modules that may be effected build and rewrite their configuration files.

     This is why people that have modified the configuration files for services running in eBox have their changes over written.   There is a method to fix this.  Find the configuration file that eBox uses as the prototype for the configuration file your modifying and place your configuration changes there instead.  This way every time you make changes in eBox and it over writes configuration files, your changes will be included.  This file is always named by taking the name of the configuration file and appending ".mas" at the end of the file name.

So for resolv.conf the prototype file would be called resolv.conf.mas.  These files Mason Template Files and there are two programing languages involved.  1 is Mason, the other is Perl. and of course there are the configuration statements that need to be generated and placed into the configuration file. resolv.conf in this case.  So if you open resolv.conf.mas and add the configuration statements that are needed, and save it, then restart eBox you should see your changes in the file.

     Sounds to me like Samba, LDAP and Ubuntu is not properly stitched together.

     Samba should be the place where the Ubuntu File System is told how to write a given file, I'm sure that on the low level system calls, ( the ones in Samba that call the File System) the USERNAME should passed in as the owner.  I bet that __EBOX__ is the UNIX account that "Owns" the process that runs Samba or eBox. Since the users are Authenticating OK. able to read and write, I suspect that Samba is not asking LDAP for the user name again when formating the Open File system request and so the File System uses the OS Username of the process making the request.  This may be "Required" behavior.


Really cool!

Installation and Upgrades / Re: Good configuration HOWTO, not eBox
« on: June 10, 2009, 03:23:19 am »
     I was trying to provide insight into the deeper workings of these OSS packages that eBox uses.  I am a very committed eBoxer, and was not trying to push anyone away.  Check my posts.

    Exactly what I thought when I read through it,  What was really helpful for me is the discussions that he goes through on why he chose stuff.

Pages: 1 2 3 [4] 5 6 ... 13