Re: Way to be announced about security updates and new releases

2013-08-21 Thread dgmm
On Wednesday 21 August 2013 07:54:06 Antonio Kless wrote:
> Is there any way to be noticed, when security updates or new releases are
> available?
> 
> https://twitter.com/freebsd nearly would be a solution, if it did not
> repostquestions from its
> subscribers and other information that is not related to updates.

Mailing list
freebsd-annou...@freebsd.org
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Freebsddiary.org - Integrated marketing help

2013-08-21 Thread Joseph Taylor
face="Verdana, sans-serif">Freebsddiary.org color="#ff">Team,
I

thought you might like to know some reasons why you are not getting
enough Social Media and Organic search engine traffic  
forFreebsddiary.org
1.

Your website Freebsddiary.org is
not ranking top in Google organic searches for many competitive
keyword phrases.
2.
Your company is not doing well in most of the Social Media  
Websites.
3.

Your site is not user friendly on mobile devices.
There

are many additional improvements that could be made to your website,
and if you would like to learn about them, and are curious to know
what our working together would involve, then I would be glad to
provide you with a detailed analysis in the form of a WEBSITE
AUDIT REPORT for FREE.
Our

clients consistently tell us that their customers find them because
they are at the top of the Google search rankings. Being at the top
left of Google (#1- #3 organic positions) is the best thing you can
do for your company's website traffic and online reputation. You will
be happy to know that, my team is willing to guarantee you 1st
page Google ranking for most of your targeted keyword phrases in our
six month ongoing campaign.
Sound

interesting? Feel free to email us or alternatively you can provide
me with your phone number and the best time to call you. I am also
available to meet you in person and present you this website audit
report.-Best
Regards,Joseph Taylorface="Verdana, sans-serif">Marketing Consultantcolor="#ff">href="tel:%28315%29-895-1453" target="_blank">(href="tel:315%29-895-1453" value="+13158951453"  
target="_blank">315)-895-1453color="#ff">



PS
I: I

am not spamming. I have studied your website and believe I can help
with your business promotion. If you still want us to not contact
you, you can ignore this email or ask to remove and I will not
contact again.
PS

II: I found your site using Google search and after having a look
over your website I recommend you to implement future technologies
such as HTML5 and Responsive Design to make your site more accessible
in mobile phone, tablets, desktop etc.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: jail.conf ignoring exec.fib?

2013-08-21 Thread Karl Pielorz



--On 20 August 2013 18:02 +0100 Arthur Chance  wrote:


And that's just made me think of something else - I have a horrible
feeling that jexec will attach to the jail using whatever fib it's
running under, i.e. the fib from the host environment. Do you have (or
can you enable) ssh running in the jail? If so, log into the jail that
way, and see what

sysctl net.my_fibnum

shows then, because you'll be running under the environment created by
/etc/rc.


Ok, one word: Bingo. That was it. I'll spare you the gory details of how I 
cut myself off from the machine, managed to create a jail with no access 
etc. etc.


But yes, that was it - in summary:

 jail -c -v  Does not actually *show* the fib being set, but will show an 
error if the setfib call fails.


 jexec   Runs a process in the jail, using the prevailing fib - not 
the jails fib, you can rectify this by using 'setfib X jexec jail tcsh'


I don't know if that last point should be considered a 'bug' or not...

Many thanks for your help!

-Karl
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Way to be announced about security updates and new releases

2013-08-21 Thread Matthew Seaman
On 21/08/2013 08:10, dgmm wrote:
> On Wednesday 21 August 2013 07:54:06 Antonio Kless wrote:
>> Is there any way to be noticed, when security updates or new releases are
>> available?
>>
>> https://twitter.com/freebsd nearly would be a solution, if it did not
>> repostquestions from its
>> subscribers and other information that is not related to updates.
> 
> Mailing list
> freebsd-annou...@freebsd.org

Don't forget about securing your ports too.  There's several available
mechanisms:

   RSS feed from vuxml.freebsd.org

   portaudit(1) -- for old style packages

   pkg audit  -- for pkgng-ized systems

Cheers,

Matthew


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: jail.conf ignoring exec.fib?

2013-08-21 Thread Arthur Chance

On 21/08/2013 11:35, Karl Pielorz wrote:



--On 20 August 2013 18:02 +0100 Arthur Chance  wrote:


And that's just made me think of something else - I have a horrible
feeling that jexec will attach to the jail using whatever fib it's
running under, i.e. the fib from the host environment. Do you have (or
can you enable) ssh running in the jail? If so, log into the jail that
way, and see what

sysctl net.my_fibnum

shows then, because you'll be running under the environment created by
/etc/rc.


Ok, one word: Bingo. That was it. I'll spare you the gory details of how
I cut myself off from the machine, managed to create a jail with no
access etc. etc.

But yes, that was it - in summary:

  jail -c -v  Does not actually *show* the fib being set, but will show
an error if the setfib call fails.

  jexec   Runs a process in the jail, using the prevailing fib - not
the jails fib, you can rectify this by using 'setfib X jexec jail tcsh'

I don't know if that last point should be considered a 'bug' or not...


Certainly the jexec problem is going to bite people again and again, so 
you should probably file a PR for it. As for the -v option, the man page 
says "Print a message on every operation", so it's down to what is or 
isn't regarded as an operation worth reporting.



Many thanks for your help!


No problem, it helps me understand jails better as well.

--
In the dungeons of Mordor, Sauron bred Orcs with LOLcats to create a
new race of servants. Called Uruk-Oh-Hai in the Black Speech, they
were cruel and delighted in torturing spelling and grammar.

_Lord of the Rings 2.0, the Web Edition_
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Renumber users and groups

2013-08-21 Thread Olivier Nicole
Hello,

On my system legacy users come with UID starting from 200 upward, and
all users come with GID lower that 100.

I know it's not a good idea, but consider that some accounts are over 20
years old!

This is not too much a problem with FreeBSD as I can renumber the few
FreeBSD services that have a conflicting ID.

But now I want to share the user directories with Mac (10.6). On Mac,
any id lower than 512 should be reserved for the system.

I tried to renumber the conflicting services on Mac OS, but it messes up
the system.

So I should renumber my users; it's not very difficult to do, but I have
over 1TB of user files for 200 users.

Is there a clever/fast way to do that (other than find -exec chown)?

What pitfall should I avoid?

Best regards,

Olivier
-- 
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Renumber users and groups

2013-08-21 Thread Mark Felder
On Wed, Aug 21, 2013, at 7:36, Olivier Nicole wrote:
> 
> Is there a clever/fast way to do that (other than find -exec chown)?
> 

Maybe! I haven't tried this myself yet, but next time I need to do this
I think I'm going to take an mtree backup of the entire filesystem,
change the UIDs and GIDs (vipw, then vi /etc/groups), and then re-apply
the mtree to the entire filesystem. It should find all the files that
are now orphaned and fix them to use the new UID/GID that you specified.
:)

> What pitfall should I avoid?
> 

Not having a backup :)
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Renumber users and groups

2013-08-21 Thread Frank Leonhardt

On 21/08/2013 13:36, Olivier Nicole wrote:

Hello,

On my system legacy users come with UID starting from 200 upward, and
all users come with GID lower that 100.

I know it's not a good idea, but consider that some accounts are over 20
years old!

This is not too much a problem with FreeBSD as I can renumber the few
FreeBSD services that have a conflicting ID.

But now I want to share the user directories with Mac (10.6). On Mac,
any id lower than 512 should be reserved for the system.

I tried to renumber the conflicting services on Mac OS, but it messes up
the system.

So I should renumber my users; it's not very difficult to do, but I have
over 1TB of user files for 200 users.

Is there a clever/fast way to do that (other than find -exec chown)?

What pitfall should I avoid?

Best regards,

Olivier


Both tar and rsync are spectacularly clever about this. I've never 
needed to renumber users, but I've noticed tar will restore a backup 
across hosts and try to resolve user names correctly. tar stores users 
and groups symbolically and will happily extract them to the correct 
numerical ID on the new host. All you need do, therefore, is merge the 
passwd and group files without conflict and "untar" everything. If 
you've got to do this in-place it's not going to work, but as you'd be 
wise to make a backup anyway you may as well make a copy instead, and 
let it convert them on the fly. rsync seems to pull the same trick.


Regards, Frank.

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Renumber users and groups

2013-08-21 Thread Mark Felder
On Wed, Aug 21, 2013, at 11:12, Frank Leonhardt wrote:
> On 21/08/2013 13:36, Olivier Nicole wrote:
> > Hello,
> >
> > On my system legacy users come with UID starting from 200 upward, and
> > all users come with GID lower that 100.
> >
> > I know it's not a good idea, but consider that some accounts are over 20
> > years old!
> >
> > This is not too much a problem with FreeBSD as I can renumber the few
> > FreeBSD services that have a conflicting ID.
> >
> > But now I want to share the user directories with Mac (10.6). On Mac,
> > any id lower than 512 should be reserved for the system.
> >
> > I tried to renumber the conflicting services on Mac OS, but it messes up
> > the system.
> >
> > So I should renumber my users; it's not very difficult to do, but I have
> > over 1TB of user files for 200 users.
> >
> > Is there a clever/fast way to do that (other than find -exec chown)?
> >
> > What pitfall should I avoid?
> >
> > Best regards,
> >
> > Olivier
> 
> Both tar and rsync are spectacularly clever about this. I've never 
> needed to renumber users, but I've noticed tar will restore a backup 
> across hosts and try to resolve user names correctly. tar stores users 
> and groups symbolically and will happily extract them to the correct 
> numerical ID on the new host. All you need do, therefore, is merge the 
> passwd and group files without conflict and "untar" everything. If 
> you've got to do this in-place it's not going to work, but as you'd be 
> wise to make a backup anyway you may as well make a copy instead, and 
> let it convert them on the fly. rsync seems to pull the same trick.
> 

Those solutions sound pretty handy if I need to move the files at the
same time. mtree should do this in-place with minimal fuss as it's just
confirming permissions and ownership on all files.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Renumber users and groups

2013-08-21 Thread Mark Felder
On Wed, Aug 21, 2013, at 11:36, Mark Felder wrote:
> 
> Those solutions sound pretty handy if I need to move the files at the
> same time. mtree should do this in-place with minimal fuss as it's just
> confirming permissions and ownership on all files.
>

I also just thought of an idea I need to benchmark: running mtree with
and without nscd. I bet nscd could speed it up a lot.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: UUID in fstab.

2013-08-21 Thread varanasi sainath
Thanks for the support.

I want to use the uuid's found using sysctl -a in fstab.
/dev/gptid/ has only uuid for boot partition.

Cheers
Sainath


On Wed, Aug 21, 2013 at 11:48 AM, Warner Losh  wrote:

> /dev/gptid/$UID
>
> maybe what you are looking for?
>
> Warner
>
> On Aug 21, 2013, at 12:16 AM, varanasi sainath wrote:
>
> > Hello,
> >
> > How to find UUID's for Disk volumes.
> >
> > I have used sysctl -a | grep uuid and was able to find
> > freebsd-swap
> > b55ff220-dcdd-11e2-a324-00155d55b20c
> >
> > freebsd-ufs
> > b55762fc-dcdd-11e2-a324-00155d55b20c
> >
> > are these the corresponding UUID's for swap and ufs.
> >
> > I din't find /dev/ufsid folder to get the UUID's
> >
> > I have used glabel and was able to create labels, system boots well,
> > everything works fine but I don't want to use labels (operating
> constraint:
> > to create labels I have to boot into single user mode, is there a way to
> > create labels on mounted partitions (I hope not)).
> >
> > I found gptid folder which has boot UUID can this be used?
> >
> > How to use UUID's in fstab?
> >
> > I have tried using
> > # DeviceMountpointFStype  Options Dump
> > Pass#
> > uuid=b55762fc-dcdd-11e2-a324-00155d55b20c  /  ufs  rw 1 1
> >
> > that din't work.
> >
> > I found (from a post) /dev/ufsid/ should be used in fstab but I
> don't
> > see ufsid in /dev. Do we need to create this or does the system does it?
> >
> > Note:
> > Using FreeBSD 9.1. created partitions using the guided partition tool.
> >
> > Reason: using a SCSI storage driver which changes the drive name
> > accordingly but freebsd installer (boot) is unable to find the drives
> which
> > results in boot failure.
> >
> > Thanks,
> > Sainath.*
> > *
> > *
> > *
> > *"Learning is the key to excellence".*
> > ___
> > freebsd-driv...@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-drivers
> > To unsubscribe, send any mail to "
> freebsd-drivers-unsubscr...@freebsd.org"
>
>


-- 
Sainath Varanasi
Hyderabad
09000855250
*My Website : http://s21embedded.webs.com
**Linked In Profile : http://in.linkedin.com/pub/sainathvaranasi

..
..
*
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without argument), ignoring

2013-08-21 Thread alexus
I just update snort (using portmaster -PP snort) and now I'm getting this:

# pkg_info | grep ^snort
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
pkg_info: corrupted record for package snort-2.9.3.1 (pkgdep line without
argument), ignoring
snort-2.9.3.1   Lightweight network intrusion detection system
#

any ideas how to address it?
thanks in advance!

-- 
http://alexus.org/
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Invitation: Hello dear @ Wed Aug 21, 2013 7:30pm - 8:30pm (hellentolbe...@gmail.com)

2013-08-21 Thread Miss Hellen Tolbert

You have been invited to the following event.

Title: Hello dear
Hello,

My name is Miss Hellen Tolbert, It give me a great pleasure to write you. I  
was browsing when i came across your email and I was attracted to write to  
you so that we can be friends if you will have the desire as me. i will be  
very happy to be in communication with you so that we can get to know each  
other better and see what happens in future. I will like you to reply to my  
email (hellentolb...@ymail.com) so that i can tell you more about my self  
and give you my pictures. I will be waiting to hear from you. Have a  
blessed day.


Thanks
Miss Hellen Tolbert.
When: Wed Aug 21, 2013 7:30pm – 8:30pm Eastern Time
Calendar: hellentolbe...@gmail.com
Who:
(Guest list is too large to display)

Event details:  
https://www.google.com/calendar/event?action=VIEW&eid=amxlcGd0YW4wdmgwZHF0b25mcDZ2czZvNG8gZnJlZWJzZC1xdWVzdGlvbnNAZnJlZWJzZC5vcmc&tok=MjQjaGVsbGVudG9sYmVydDJAZ21haWwuY29tMDc4ZjExODAxMTFiZWY2MGQ3Njg2NmNmMzk0YTFmNzQ2NDkyMDU5NA&ctz=America/New_York&hl=en


Invitation from Google Calendar: https://www.google.com/calendar/

You are receiving this courtesy email at the account  
freebsd-questions@freebsd.org because you are an attendee of this event.


To stop receiving future notifications for this event, decline this event.  
Alternatively you can sign up for a Google account at  
https://www.google.com/calendar/ and control your notification settings for  
your entire calendar.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"

Re: FreeBSD 9.2

2013-08-21 Thread ajtiM
http://forums.macrumors.com/showthread.php?t=1619404

It is helpful too…


On Aug 15, 2013, at 4:14 PM, Doug Hardie  wrote:

> 
> On 15 August 2013, at 06:37, ajtiM  wrote:
> 
>> 
>> How will be ATI supported in FreeBSD 9.2, please? I like bluetooth mouse. Is 
>> it supported?
>> 
>> I try Linux Mint and it works perfect. I am downloading live CD for NetBSD 
>> (jibbed) and I will see how is works but I like to install FreeBSD (not 
>> double boot, just FreeBSD).
>> 
> 
> See:  http://docs.freebsd.org/cgi/mid.cgi?28915479-B712-4ED0-A041-B75F2F59FECA
> 
> Thats not a complete answer as I don't use any of the user interface stuff.  
> However, it will give a starting point for you.  I have updated my two newest 
> minis to run 9.2 (latest candidate).
> 
> 

Mitja

http://www.redbubble.com/people/lumiwa

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


dig

2013-08-21 Thread Doug Hardie
There appears to be a problem with dig and the +trace option in 9.2.  I believe 
its also in 9.1.  The command:

dig freebsd.org +trace

Only yields a dumb response.  No useful information is provided.  Running the 
same command on FreeBSD 7.2 yields a complete trace with lots of useful 
information.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: dig

2013-08-21 Thread Frank Leonhardt

On 22/08/2013 00:34, Doug Hardie wrote:

There appears to be a problem with dig and the +trace option in 9.2.  I believe 
its also in 9.1.  The command:

dig freebsd.org +trace

Only yields a dumb response.  No useful information is provided.  Running the 
same command on FreeBSD 7.2 yields a complete trace with lots of useful 
information.
___



Works for me on 9.0 and 9.1 (and 8.2, 7.1, 7.0)

Is there something wrong with your local bind configuration?

Regards, Frank.


___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: dig

2013-08-21 Thread Doug Hardie

On 21 August 2013, at 17:02, Doug Hardie  wrote:

> 
> On 21 August 2013, at 16:46, Frank Leonhardt  wrote:
> 
>> On 22/08/2013 00:34, Doug Hardie wrote:
>>> There appears to be a problem with dig and the +trace option in 9.2.  I 
>>> believe its also in 9.1.  The command:
>>> 
>>> dig freebsd.org +trace
>>> 
>>> Only yields a dumb response.  No useful information is provided.  Running 
>>> the same command on FreeBSD 7.2 yields a complete trace with lots of useful 
>>> information.
>>> ___
>>> 
>> 
>> Works for me on 9.0 and 9.1 (and 8.2, 7.1, 7.0)
>> 
>> Is there something wrong with your local bind configuration?
>> 
>> Regards, Frank.
> 
> No.  The 7.2 config is identical to the 9.1 and there is no bind running on 
> the 9.2.
> 
> 

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: dig

2013-08-21 Thread Robert Huff

>  > There appears to be a problem with dig and the +trace option in
>  > 9.2.  I believe its also in 9.1.  The command: 
>  >
>  > dig freebsd.org +trace
>  >
>  > Only yields a dumb response.  No useful information is
>  provided.  Running the same command on FreeBSD 7.2 yields a
>  complete trace with lots of useful information.
>  
>  Works for me on 9.0 and 9.1 (and 8.2, 7.1, 7.0)

And on:

FreeBSD 10.0-CURRENT #0 r248938: Sun Mar 31 06:24:42 EDT 2013  amd64 


Robert Huff

___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: dig

2013-08-21 Thread Colin House

On 22/08/2013 9:34 AM, Doug Hardie wrote:

There appears to be a problem with dig and the +trace option in 9.2.  I believe 
its also in 9.1.  The command:

dig freebsd.org +trace

Only yields a dumb response.  No useful information is provided.  Running the 
same command on FreeBSD 7.2 yields a complete trace with lots of useful 
information.


Have you tested against another NS?  I ran into a similar problem when 
setting up unbound as a local recursor recently on a 9.1-STABLE 
(r251985) box.


dig +trace  would return (next to) nothing.  dig +trace  
@8.8.8.8 worked as expected.


I found it was the access-control configuration of unbound.  Changing my 
"access-control: ::1 allow" to "access-control: ::1 allow_snoop" 
restored the +trace functionality.


I'm not sure how this translates with bind.. Perhaps the defaults have 
changed between the versions that you're running (if you're running the 
base versions on 7.2 and 9.1) or your recursive server isn't allowing it 
on 9.2?  Fwiw, in unbound, "allow" allows recursive lookups, 
"allow_snoop" allows both recursive and non-recursive lookups.


- Col
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Re: Renumber users and groups

2013-08-21 Thread Olivier Nicole
Thank you,

>> Those solutions sound pretty handy if I need to move the files at the
>> same time. mtree should do this in-place with minimal fuss as it's just
>> confirming permissions and ownership on all files.
> I also just thought of an idea I need to benchmark: running mtree with
> and without nscd. I bet nscd could speed it up a lot.

I did try mtree on my own files, counting for 20% of the total size,
and it took only seconds.

I bet other users may have many more smaller files, but it's all a
matter of minutes, so it is fast enough.

Best regards,

Olivier
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"


Hello freebsdquestions

2013-08-21 Thread amar
Hello freebsdquestions i havent seen anything work as well as this on the first 
try http://bitly.com/13C7n5L quit your nine to five in three weeks or less 
guaranteed

































































___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscr...@freebsd.org"