Support Issue 164620

To whom it may concern:

          My question is?  So is this problem in the process of being looked
at?  Or am I being directed to a different group in the BSD support staff?

Morris Allen (Moe)

___________________________

E-mail is a privilege.  Not a right.

Stop Spam now!!!

Thank you very much for your problem report.

It has the internal identification `i386/164620'.

The individual assigned to look at your

report is: freebsd-i386. 

You can access the state of your problem report at any time via this link:

http://www.freebsd.org/cgi/query-pr.cgi?pr=164620

>Category:       i386

>Responsible:    freebsd-i386

Re: Support Issue 164620

On Tue, Jan 31, 2012 at 06:28:25PM -0600, Morris Allen wrote:
> 
> 
> To whom it may concern:
> 
>  
> 
>           My question is?  So is this problem in the process of being looked
> at?  Or am I being directed to a different group in the BSD support staff?
> 
>  

It's an automatic notice to let you know the issue tracker has received
the problem report.  So hopefully, someone will look at it.

> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=164620
> 

It seems you just pasted the text from the docs (Handbook
probably) on GEOM RAID 1, without any info as to what is the problem
you're having.  Not to mention the wrong "Environment" entry etc.

I think you would benefit from reading this:
http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/index.html

--

-- 
I am ready to meet my Maker.  Whether my Maker is prepared
for the great ordeal of meeting me is another matter.
		-- Winston Churchill

Re: Support Issue 164620

On Wed, Feb 01, 2012 at 02:18:46AM +0100, Nikola Pavlović wrote:
> On Tue, Jan 31, 2012 at 06:28:25PM -0600, Morris Allen wrote:
> > 
> > To whom it may concern:
> > 
> >           My question is?  So is this problem in the process of being looked
> > at?  Or am I being directed to a different group in the BSD support staff?
> > 
> >  
> 
> It's an automatic notice to let you know the issue tracker has received
> the problem report.  So hopefully, someone will look at it.
> 
> > 
> > http://www.freebsd.org/cgi/query-pr.cgi?pr=164620
> > 
> 
> It seems you just pasted the text from the docs (Handbook
> probably) on GEOM RAID 1, without any info as to what is the problem
> you're having.  Not to mention the wrong "Environment" entry etc.
> 
> I think you would benefit from reading this:
> http://www.freebsd.org/doc/en_US.ISO8859-1/articles/problem-reports/index.html

And there are no "support issues", PRs are for reporting real problems.
If you need to ask something, just use this list instead.

Yuri

no borders with firefox, terminal (xfce on FreeBSD 9.0 amd64 STABLE)

Dear folks,

I am having some difficultites when starting up the desktop.  The
desktop starts up automagically and when I start firefox or terminal
there is no border :(.  Upon logging out and unchecking Save Settings,
and relogging back in the borders appear.  I have had this happen once
on one of my FreeBSD 8.2 amd64 boxes, but I fixed it somehow with the
settings.  Now I can't find the settings that cause this.  All I know
is that if I log out and un check save settings, the border appear
again and all is well.  But if I reselect the save settings box, and
log out and back in, the borderless windows appear :(  How can I
troubleshoot this?  Any ideas, suggestions, comments are greatly
appreciated.

Regards,

Antonio
_______________________________________________
freebsd-questions <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at> freebsd.org"

Re: no borders with firefox, terminal (xfce on FreeBSD 9.0 amd64 STABLE)

Hi,

I did not see which window manager or desktop you are using.

Erich

On Wednesday 01 February 2012 10:45:26 Antonio Olivares wrote:
> Dear folks,
> 
> I am having some difficultites when starting up the desktop.  The
> desktop starts up automagically and when I start firefox or terminal
> there is no border :(.  Upon logging out and unchecking Save Settings,
> and relogging back in the borders appear.  I have had this happen once
> on one of my FreeBSD 8.2 amd64 boxes, but I fixed it somehow with the
> settings.  Now I can't find the settings that cause this.  All I know
> is that if I log out and un check save settings, the border appear
> again and all is well.  But if I reselect the save settings box, and
> log out and back in, the borderless windows appear :(  How can I
> troubleshoot this?  Any ideas, suggestions, comments are greatly
> appreciated.
> 
> Regards,
> 
> Antonio
> _______________________________________________
> freebsd-questions <at> freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at> freebsd.org"
> 
> 

Securely sharing directories between jails

L.S.,

I want to set up my system in a way where applications are clustered
over jails, e.g. a httpd, smbd and dbmsd jail. However, in most cases I
need to share data over the jails, which is stored on the host.
Often, nullfs and mounting ro is suitable, but I need write access in
some cases. As nullfs rw over multiple jails can be considered insecure,
I was wondering what would be a secure way.

The only thing I could come up with was having both a NFS server and
client running on the host and mounting such that all access is mapped
to an account with less privileges. However, it seems like a waste to
NFS with yourself. Thus, are there any better ways to achieve this?

(I also thought of using nosuid flags, but I'm not sure if this is
enough.)

Kind regards,

Stas Verberkt

Re: Unable to upgrade packages on FreeBSD

At 11:42 31/01/2012, you wrote:
>While your offer is made with the best of intentions, I doubt the
>project would feel able take you up on it.  The problem is simply one of
>security -- while crowd-sourcing package compilation would be a pretty
>sweet technical solution to much of the scaling and resource cost
>problems, it offers far too much opportunity for people up-to-no-good to
>be able to introduce trojans, spyware and so forth.

No no, i didn't said i will make them manually, i wanted to said that 
i can add one server amd64 to the pool of automate servers that make 
the packages, i think it works automatically and distribute workload 
like boinc or other similar net. About the people which introduce 
trojans, rootkits etc... i didn't think on that issue and is really a 
very important stopper.

With the rest of your mail, i agree with you, my idea was completly 
halfthinked (is it the correct word?).

Mental Note to remember: Beside daemons, there are devils.

L 

_______________________________________________
freebsd-questions <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at> freebsd.org"

limit on PV entries

FreeBSD 8.2-RELEASE
>From time to time, I get in /var/log/messages
 kernel: Approaching the limit on PV entries, consider increasing either
the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.

this started a few weeks ago, never had that before, don't have it on other
FreeBSD 8.2-RELEASE systems.

- What does this mean?
- And how to increase either of the two and to what level ?

$ sysctl vm.pmap.shpgperproc
vm.pmap.shpgperproc: 200
$ sysctl vm.pmap.pv_entry_max
vm.pmap.pv_entry_max: 3256966
_______________________________________________
freebsd-questions <at> freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at> freebsd.org"

Re:[SOLVED] bash LC_COLLATE or LC_ALL set “C” not sort in dictionary order.

On 01/31/12 12:22, Robert Bonomi wrote:
> `
>
>
> Edward wrote:
>> On 01/31/12 06:31, Robert Bonomi wrote:
>>>>        Hi,
>>>>
>>>>        Been trying to get BASH to sort set characters in  dictionary order.
>>>>       I typed "locale" and it shows LC_COLLATE and LC_ALL are set to "C"
>>>> thought that was enough to work,
>>>>       however when i type metacharacters:  set character; any character,
>>>> something like this:
>>>>
>>>>           ls  [a-cx-y]*
>>>>
>>>>        bash does not sort in dictionary order; file   "Binarc" does not
>>>> list.
>>>>
>>> *OF*COURSE* it doesn't.  Unix is _case_sensitive_.  You specified a lower-
>>> case only (in the C locale) pattern.  Naturally, it doesn't match a file
>>> with an upper-case character in it.
>>>
>>> Note: in the 'C' locale, characters are sorted on the underlying byte value.
>>> Thus you will get all the upper-case matches before any lower-case match.
>>>
>>> To get upper-and-lower case files in the C locale, you will have to use:
>>>             ls [A-CX-Ya-cx-y]*
>>>
>>> IF you speciy a different charset for collating, you _may_ get upper/lower

Re: limit on PV entries

Did you explicitly disabled superpages?
What is the output of $ sysctl vm.pmap.pg_ps_enabled ?

On 02/01/2012 10:17, n dhert wrote:
> FreeBSD 8.2-RELEASE
>> From time to time, I get in /var/log/messages
>   kernel: Approaching the limit on PV entries, consider increasing either
> the vm.pmap.shpgperproc or the vm.pmap.pv_entry_max sysctl.
>
> this started a few weeks ago, never had that before, don't have it on other
> FreeBSD 8.2-RELEASE systems.
>
> - What does this mean?
> - And how to increase either of the two and to what level ?
>
> $ sysctl vm.pmap.shpgperproc
> vm.pmap.shpgperproc: 200
> $ sysctl vm.pmap.pv_entry_max
> vm.pmap.pv_entry_max: 3256966
> _______________________________________________
> freebsd-questions <at> freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe <at> freebsd.org"

--

-- 
No trees were killed in the creation of this message.
However, many electrons were terribly inconvenienced.

_______________________________________________