only recovers
> lost space.
That and inode link changes (ie, adding or removing files from a directory).
>> With journalling, it should be able to do a journal replay to restore
>> the filesystem to an OK state,
>
> My understanding is that the journal does nothing to restore the
Hi--
On Oct 14, 2013, at 11:51 AM, Daniel Feenberg wrote:
> This discussion skirts the critical issue - are files that are not open for
> writing endangered? No description of the uses of journaling can be
> considered informative if it doesn't address that explicitly. As a n
xplain the logic in which this helps anything.
>
>
> Or to do a filesystem check
> after crash..?
>
>
> Already standard behavior as implicitly seen in this thread.
>
>
> Are there any flags like that to mark filesystem
> unclean and to force f
On 14.10.2013 18:47, Adam Vande More wrote:
> There is no *warranty* as explicitly stated in
> http://www.freebsd.org/copyright/freebsd-license.html
>
Aha, please don't play on words ;-). I think you understood I was
speaking about the filesystem state
not
On 14.10.2013 20:08, RW wrote:
> On Mon, 14 Oct 2013 18:34:36 +0200
> David Demelier wrote:
>
>> On 14.10.2013 14:39, RW wrote:
>
>>> If you are having problems with data integrity you might try
>>> gjournal or zfs instead.
>>
>> Why? SU+J is enab
On Mon, 14 Oct 2013 11:48:18 -0700
Charles Swiger wrote:
> fsck_y_enable="YES"
One of the most annoying things about SU+J is that fsck asks if you
want to use the journal. So fsck -y wont do a proper check unless the
journal replay fails.
__
Charles Swiger wrote:
[snip]
> Yes. Without journalling, you'd normally perform the full timeconsuming
> fsck
> in the foreground. With journalling, it should be able to do a journal
> replay to restore the filesystem to an OK state, but sometimes that
> doesn't rest
On Mon, 14 Oct 2013 11:48:18 -0700
Charles Swiger wrote:
> Yes. Without journalling, you'd normally perform the full
> timeconsuming fsck in the foreground.
Journalling removes the need for the background fsck which only recovers
lost space.
> With journalling, it should be
On Mon, 14 Oct 2013, Bruce Cran wrote:
On 10/14/2013 6:16 PM, CeDeROM wrote:
Isn't there Journal to prevent and reverse such damage?
Unlike other journaling filesystems, UFS+J only protects the metadata, not
the data itself - i.e. I think it ensures you won't have to run a ma
Thank you all for good hints! This will come handy! :-)
--
CeDeROM, SQ7MHZ, http://www.tomek.cedro.info
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-
tects the metadata, not
>> the data itself - i.e. I think it ensures you won't have to run a manual
>> fsck, but just like plain old UFS files may be truncated as the journal is
>> replayed.
>
> Thank you for explaining :-) So it looks that it would be sensible to
> for
On Mon, Oct 14, 2013 at 1:43 PM, Adam Vande More wrote:
>
>
> mount -o sync
>
should be
mount sync
--
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any
On Mon, Oct 14, 2013 at 1:33 PM, CeDeROM wrote:
> Thank you for explaining :-) So it looks that it would be sensible to
> force filesystem check every n-th mount..?
Please explain the logic in which this helps anything.
> Or to do a filesystem check
> after crash..?
Alre
On 10/14/2013 7:33 PM, CeDeROM wrote:
Thank you for explaining :-) So it looks that it would be sensible to
force filesystem check every n-th mount..? Or to do a filesystem check
after crash..? Are there any flags like that to mark filesystem
unclean and to force fsck after n-th mount? That
On Mon, Oct 14, 2013 at 7:54 PM, Bruce Cran wrote:
> On 10/14/2013 6:16 PM, CeDeROM wrote:
>> Isn't there Journal to prevent and reverse such damage?
>
> Unlike other journaling filesystems, UFS+J only protects the metadata, not
> the data itself - i.e. I think it ensures
On Mon, 14 Oct 2013 18:34:36 +0200
David Demelier wrote:
> On 14.10.2013 14:39, RW wrote:
> > If you are having problems with data integrity you might try
> > gjournal or zfs instead.
>
> Why? SU+J is enabled by default. Isn't the purpose of a journaled file
>
On 10/14/2013 6:16 PM, CeDeROM wrote:
Isn't there Journal to prevent and reverse such damage?
Unlike other journaling filesystems, UFS+J only protects the metadata,
not the data itself - i.e. I think it ensures you won't have to run a
manual fsck, but just like plain old UFS fi
ining
> the directory entries for those files, not the file data itself, may be
> damaged (ie: the directory was in the process of being written OR the
> pointer to that SECTOR was in the process of being written).
>
> It doesn't mean a file was in active use, just that a chunk of t
On 10/14/2013 12:50 PM, CeDeROM wrote:
On Mon, Oct 14, 2013 at 6:47 PM, Adam Vande More wrote:
On Mon, Oct 14, 2013 at 11:34 AM, David Demelier
wrote:
Why? SU+J is enabled by default. Isn't the purpose of a journaled file
system to ensure that any bad shutdown will protect data?
As al
On Mon, Oct 14, 2013 at 6:56 PM, Adam Vande More wrote:
> On Mon, Oct 14, 2013 at 11:50 AM, CeDeROM wrote:
>> Then why random files gets damaged as well even they are not
>> accessed/written on power loss? :-)
> Prove they weren't.
Hmm, maybe /etc/pwd.db as David mentioned? This is updated on pa
On Mon, Oct 14, 2013 at 11:50 AM, CeDeROM wrote:
>
> Then why random files gets damaged as well even they are not
> accessed/written on power loss? :-)
>
Prove they weren't.
--
Adam Vande More
___
freebsd-questions@freebsd.org mailing list
http://lis
On Mon, Oct 14, 2013 at 6:47 PM, Adam Vande More wrote:
> On Mon, Oct 14, 2013 at 11:34 AM, David Demelier
> wrote:
>>
>> Why? SU+J is enabled by default. Isn't the purpose of a journaled file
>> system to ensure that any bad shutdown will protect data?
>
> As
On Mon, Oct 14, 2013 at 11:34 AM, David Demelier
wrote:
>
> Why? SU+J is enabled by default. Isn't the purpose of a journaled file
> system to ensure that any bad shutdown will protect data?
>
As already stated, those measures are to preserve fs integrity eg meta data
is in
On Mon, Oct 14, 2013 at 6:34 PM, David Demelier
wrote:
> Why? SU+J is enabled by default. Isn't the purpose of a journaled file
> system to ensure that any bad shutdown will protect data?
>
> On GNU/Linux, on Windows you will not require anything else to recover
> your data.
On 14.10.2013 14:39, RW wrote:
> On Mon, 14 Oct 2013 05:02:22 -0400
> Michael Powell wrote:
>
>> David Demelier wrote:
>>
>>> Hello there,
>>>
>>> I'm writing because after a power failure I was unable to log in on
>>> my FreeBSD 9.2-
On Mon, 14 Oct 2013 05:02:22 -0400
Michael Powell wrote:
> David Demelier wrote:
>
> > Hello there,
> >
> > I'm writing because after a power failure I was unable to log in on
> > my FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly
> > b
o successfully fsck all the other partitions (besides
> /), then rebooted and system came back up OK.
Meant to include also that I booted from a CD with wddiags and ran the Quick
test and it found no errors on the disk.
[snip]
>
> -Mike
_
David Demelier wrote:
> Hello there,
>
> I'm writing because after a power failure I was unable to log in on my
> FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some
> files disappeared, including /etc/pwd.db. Thus I was unable to log in.
>
> I'
> On 13.10.2013 12:16, CeDeROM wrote:
> > On 13 Oct 2013 11:30, "David Demelier" > <mailto:demelier.da...@gmail.com>> wrote:
> >> Hello there,
> >> I'm writing because after a power failure I was unable to log in on my
> >> FreeBSD
On 13.10.2013 12:16, CeDeROM wrote:
> On 13 Oct 2013 11:30, "David Demelier" <mailto:demelier.da...@gmail.com>> wrote:
>> Hello there,
>> I'm writing because after a power failure I was unable to log in on my
>> FreeBSD 9.2-RELEASE. The SU+J jour
On 13 Oct 2013 11:30, "David Demelier" wrote:
> Hello there,
> I'm writing because after a power failure I was unable to log in on my
> FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some
> files disappeared, including /etc/pwd.db. Thus I was unable
Hello there,
I'm writing because after a power failure I was unable to log in on my
FreeBSD 9.2-RELEASE. The SU+J journal were executed correctly but some
files disappeared, including /etc/pwd.db. Thus I was unable to log in.
I've been able to regenerate the password database with a l
Ralf Mardorf writes:
> Have you tested Debian's FreeBSD port? Debian GNU/kFreeBSD perhaps
> does provide a more current user space.
> https://wiki.debian.org/Debian_GNU/kFreeBSD
Hmm, I think I would prefer a distribution with a relatively large user
base. The Wikipedia page al
Steve O'Hara-Smith writes:
>> 2. Try to become a maintainer. How?
>
> Step one would be to try bringing the port up to date yourself,
> sometimes it is as easy as editing the Makefile, changing the version
> and running make makesum to update the checksums. Sometime
On Fri, 11 Oct 2013 19:14:48 +0300
Jarmo Hurri wrote:
>
> Greetings.
>
> I would like to switch from Linux to FreeBSD, but am puzzled by the
> timeliness of the ports. In particular, I use a drawing program called
The extent to which any given port is kept up to date
On Fri, 2013-10-11 at 19:14 +0300, Jarmo Hurri wrote:
> I would like to switch from Linux to FreeBSD, but am puzzled by the
> timeliness of the ports. In particular, I use a drawing program called
> asymptote quite heavily in my work. From the ports page I noticed that
> the port
Greetings.
I would like to switch from Linux to FreeBSD, but am puzzled by the
timeliness of the ports. In particular, I use a drawing program called
asymptote quite heavily in my work. From the ports page I noticed that
the ports version is approximately 14 months old:
http://www.freebsd.org
one
> #
>
> The problem is, I cannot configure any RAIDs (please see output
> below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD
> still sees them as separate physical discs. What am I doing wrong?
>
> I cannot use gmirror with these servers because a) if n
Gary Aitken wrote:
> On 10/09/13 21:25, Polytropon wrote:
>> On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote:
>>> Seems like it must be possible to mount a cd9660 image somehow without
>>> burning an actual disc?
>>
>> Of course. :-)
>
> I guess
On Wed, 09 Oct 2013 22:18:41 -0600, Gary Aitken wrote:
> for the record, that's:
> mdconfig -a -t vnode -u 0 -f
Correct, I noticed too late that -a was missing. But "man mdconfig"
mentions all parts that are needed. :-)
> > # mount -o ro
On 10/09/13 21:25, Polytropon wrote:
> On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote:
>> Seems like it must be possible to mount a cd9660 image somehow without
>> burning an actual disc?
>
> Of course. :-)
I guess knowing it's possible is a start;
couldn't
On Wed, 09 Oct 2013 21:14:22 -0600, Gary Aitken wrote:
> Seems like it must be possible to mount a cd9660 image somehow without
> burning an actual disc?
Of course. :-)
It is possible by using a virtual node "connected" to the
ISO file. Without having tested, according
can't find the CD I burned...).
#mount -t cd9660 -o ro FreeBSD-9.1-RELEASE-amd64-disc1.iso /mnt/tmp
mount_cd9660:
/hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso: Block
device required
Seems like it must be possible to mount a cd9660 image somehow without
burning an actual d
-t cd9660 -o ro FreeBSD-9.1-RELEASE-amd64-disc1.iso /mnt/tmp
mount_cd9660: /hd1/Downloads/FreeBSD/9_1/FreeBSD-9.1-RELEASE-amd64-disc1.iso:
Block device required
Seems like it must be possible to mount a cd9660 image somehow without
burning an actual d
output
below) from FreeBSD. If I configure volumes from BIOS setup, FreeBSD
still sees them as separate physical discs. What am I doing wrong?
I cannot use gmirror with these servers because a) if no MPT RAID is
configured in BIOS setup, it cannot boot from HDD and b) if an MPT
RAID *is
On Mon, 07 Oct 2013 21:09:44 +0100, Frank Leonhardt wrote:
> On 07/10/2013 13:36, Polytropon wrote:
> > > Is there any way to make a noise through the built in "bell" speaker
> > > found on an IBM PC compatible server box? Writing 007 to the BIOS cout
> > >
On 07/10/2013 13:36, Polytropon wrote:
> Is there any way to make a noise through the built in "bell" speaker
> found on an IBM PC compatible server box? Writing 007 to the BIOS cout
> routine might do it, but I've realised I haven't got a clue how to
do that.
&
On Mon, 7 Oct 2013, Frank Leonhardt wrote:
On 07/10/2013 13:06, Peter Boosten wrote:
echo "CTRL-V CTRL-G" should do the trick
Or, more easily, printf "\a".
Alas, not. The console driver won't ring the BIOS bell on anything I've
tried. It might on a desktop
On 07/10/2013 14:31, RW wrote:
On Mon, 07 Oct 2013 13:46:53 +0100
Frank Leonhardt wrote:
Alas, not. The console driver won't ring the BIOS bell on anything
I've tried. It might on a desktop with a built-in sound card and
speakers, but it won't do anything with the "bee
On Mon, 07 Oct 2013 13:46:53 +0100
Frank Leonhardt wrote:
> Then there's the issue of writing it to the console rather than a
> virtual terminal, but I have a few hacks that'll achieve that part.
/dev/console is your friend.
--
St
On Mon, 07 Oct 2013 13:46:53 +0100
Frank Leonhardt wrote:
> Alas, not. The console driver won't ring the BIOS bell on anything
> I've tried. It might on a desktop with a built-in sound card and
> speakers, but it won't do anything with the "beep" speaker.
Are y
Frank Leonhardt skrev 2013-10-07 13:37:
In the good'ol days I could make UNIX ring a bell (literally) by sending
\a to the console TTY (an ASR33 in my case). Now there's an electronic
synthesised ting or beep from an terminal emulator IF it's got a sound
card and so on, and
On Mon, 07 Oct 2013 12:37:35 +0100
Frank Leonhardt wrote:
> In the good'ol days I could make UNIX ring a bell (literally) by sending
> \a to the console TTY (an ASR33 in my case). Now there's an electronic
> synthesised ting or beep from an terminal emulator IF it's go
On 07/10/2013 13:06, Peter Boosten wrote:
On 7 okt. 2013, at 13:37, Frank Leonhardt <mailto:fra...@fjl.co.uk>> wrote:
In the good'ol days I could make UNIX ring a bell (literally) by
sending \a to the console TTY (an ASR33 in my case). Now there's an
electronic synthesise
On Mon, 07 Oct 2013 12:37:35 +0100, Frank Leonhardt wrote:
> In the good'ol days I could make UNIX ring a bell (literally) by sending
> \a to the console TTY (an ASR33 in my case).
Ah, the famous ^G control character... :-)
> Now there's an electronic
> synthesise
On 7 okt. 2013, at 13:37, Frank Leonhardt wrote:
> In the good'ol days I could make UNIX ring a bell (literally) by sending \a
> to the console TTY (an ASR33 in my case). Now there's an electronic
> synthesised ting or beep from an terminal emulator IF it's got a soun
In the good'ol days I could make UNIX ring a bell (literally) by sending
\a to the console TTY (an ASR33 in my case). Now there's an electronic
synthesised ting or beep from an terminal emulator IF it's got a sound
card and so on, and an IBM-PC had a beep routine in the BIOS.
I
lstat("/usr/local/etc/libmap.d",0x7fffb990) ERR#2 'No such file or
> directory'
>
> Any suggestions? Thank you for the help thus far.
The 'undefined symbol' error means you have a binary which is somehow
not dynamically linking against the shared lib
On Sun, 06 Oct 2013 08:08:42 +0100, Matthew Seaman wrote:
> On 05/10/2013 21:41, Polytropon wrote:
> > On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote:
> >> I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just
> >> be able to do a
>
On 05/10/2013 21:41, Polytropon wrote:
> On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote:
>> I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just
>> be able to do a
>>
>> cd /usr/src
>> make buildworld
>> make installworld
&g
.
Eric
On Sat, Oct 5, 2013 at 4:41 PM, Polytropon wrote:
> On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote:
> > I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should
> just
> > be able to do a
> >
> > cd /usr/src
> > make buildworld
>
On Sat, 5 Oct 2013 16:00:25 -0400, Eric Feldhusen wrote:
> I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just
> be able to do a
>
> cd /usr/src
> make buildworld
> make installworld
> reboot
>
> and I'll be running up on the 9.2 kernel an
Ah, yes, when this particular box was a 9.0-release, I had compiled a
custom kernel to enable ipsec. When I check the strings, it's a 9.1
release kernel.
I see my /usr/src/sys/amd64/conf/GENERIC is a 9.2 kernel, so I should just
be able to do a
cd /usr/src
make buildworld
make install
On 05/10/2013 20:11, Eric Feldhusen wrote:
> I have a server that was/is running 9.1 release that I tried to upgrade to
> 9.2 release. I missed the step of updating to the latest 9.1 patches by
> doing
>
> freebsd-update fetch
> freebsd-update install
>
> I went righ
I have a server that was/is running 9.1 release that I tried to upgrade to
9.2 release. I missed the step of updating to the latest 9.1 patches by
doing
freebsd-update fetch
freebsd-update install
I went right to
freebsd-update upgrade -r 9.2-RELEASE
freebsd-update install
rebooot
freebsd
On 01/10/2013 08:22, Michael wrote:
> Also I am bit unsure about the setup I should pick: we are a hand of
> users for the service and I would like to know if a 64-MB Ram and a
> 166Mhz setup could do, or if I definitely should consider a faster CPU
> or more RAM. Given my actual jail
Hi John,
John Levine wrote:
> Dunno about Soekris, but I'm very happy with one of these
> mini-box systems that cost about $250 with a 60GB SSD disk:
>
> http://www.mini-box.com/MiniPC-Value-Systems
thank you for your detailed answer and useful suggestion, I will
probably l
Hello Bill,
thank you for your answer!
Bill Tillman wrote:
> The way technology has moved on these days I would approach this from a
> completely different manner. Soekris makes some cool little boxes, but the
> last time I looked they still had I486 cpu's...today may be differen
the library under
/usr/local/lib/amd64,
the file is located in /usr/local/openjdk7/jre/lib/amd64, I was able
to work around the problem by creating a symbolic link to point
/usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the
amd64
sub-directory didn't exist in /usr/local/lib.
located in /usr/local/openjdk7/jre/lib/amd64, I was able
to work around the problem by creating a symbolic link to point
/usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the amd64
sub-directory didn't exist in /usr/local/lib.
This does make me wonder though, if I am just mi
/amd64, I was able to
work around the problem by creating a symbolic link to point
/usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the amd64
sub-directory didn't exist in /usr/local/lib.
This does make me wonder though, if I am just missing something from my
environment, that'
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Dunno about Soekris, but I'm very happy with one of these
mini-box systems that cost about $250 with a 60GB SSD disk:
http://www.mini-box.com/MiniPC-Value-Systems
I got a fan but it doesn't need it. It runs ordinary amd64 FreeBSD
9.1,
From: Michael
To: "freebsd-questions@freebsd.org"
Sent: Tuesday, October 1, 2013 2:22 AM
Subject: Soekris for a Trac server
I am planning to move a jail-hosted service to a physical device and
would like to hear the advices of experts here.
/lib/amd64, I was able
to work around the problem by creating a symbolic link to point
/usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the amd64
sub-directory didn't exist in /usr/local/lib.
This does make me wonder though, if I am just missing something from
my environment, t
the problem by creating a symbolic link to point
/usr/local/lib/amd64 to /usr/local/openjdk/jre/lib/amd64, as the amd64
sub-directory didn't exist in /usr/local/lib.
This does make me wonder though, if I am just missing something from my
environment, that's causing this. Or i
I am planning to move a jail-hosted service to a physical device and
would like to hear the advices of experts here.
My service runs sshd, apache and trac (the ticket service) and I am
considering getting one of the products by soekris. I know that some
list users have some experience with these
Hi,
for the list archive, here's how I solved my "problem".
Some on the thread tell me to run BIND on the 1rst VPS, as DNS
autoritative server and as caching resolver who let only hosts from my
network send him queries.
Well I'm quite happy my setup with NSD as DNS autoritative and UNBOUND
as cach
On 2013-09-28 09:37, loran42o wrote:
Le 28.09.2013 00:08, Terje Elde a écrit :
On 28. sep. 2013, at 00:03, Frank Leonhardt wrote:
If I understand the way it works correctly, the resolver pulls a list of the NS
and hard-sets the port number for each to 53 (via a manifest constant) . See
On Sep 28, 2013, at 2:24 PM, Laurent SALIN wrote:
> Le 28.09.2013 21:28, Mike. a écrit :
>> The way I solved this problem on my setup, I assigned another IP
>> address to the network interface via ifconfig alias.
>>
>> I put the authoritative namesever on one IP ad
Le 28.09.2013 21:28, Mike. a écrit :
> The way I solved this problem on my setup, I assigned another IP
> address to the network interface via ifconfig alias.
>
> I put the authoritative namesever on one IP address, and the
> recursive nameserver on the other IP address.
>
>
On 9/28/2013 at 7:16 PM Laurent SALIN wrote:
|Le 28.09.2013 18:32, Terje Elde a écrit :
|> Not sure if I misunderstood what you're trying to do, but the way
I
|recall it, you have two boxes, one running with one recursive and
one
|authoritative nameserver, and you wanted a second box to
Le 28.09.2013 18:32, Terje Elde a écrit :
> Not sure if I misunderstood what you're trying to do, but the way I recall
> it, you have two boxes, one running with one recursive and one authoritative
> nameserver, and you wanted a second box to quey the recursive nameserver on
&
On 28. sep. 2013, at 15:50, Frank Leonhardt wrote:
> Given that BIND can happily listen on ports other than 53 and OpenBSD allows
> a port to be specified against each nameserver in resolv.conf, it does not
> seem an unreasonable question to me.
Just to avoid any misunderstanding
On 28/09/2013 00:20, Michael Sierchio wrote:
On Fri, Sep 27, 2013 at 4:11 PM, Frank Leonhardt wrote:
On 27/09/2013 23:08, Terje Elde wrote:
On 28. sep. 2013, at 00:03, Frank Leonhardt wrote:
If I understand the way it works correctly, the resolver pulls a list of
the NS and hard-sets the
Le 28.09.2013 01:11, Frank Leonhardt a écrit :
> It was more of an explanation as to /why/ it's not easy to do what asked
> in the original reasonable-sounding question.
Hi,
Thanks for the explanation of how it works from the behind.
I don't think I'll compile and maintain
Le 27.09.2013 23:31, jb a écrit :
> Well, I hope I understand you.
> You use DNS Proxy server, like BIND or DNSMASQ.
hi,
actually I use two daemons,
one to serve as a autoritative DNS server : nsd
the other one to serve as a recursive DNS resolver with caching : unbound
I can't se
Le 28.09.2013 00:08, Terje Elde a écrit :
> On 28. sep. 2013, at 00:03, Frank Leonhardt wrote:
>
>> If I understand the way it works correctly, the resolver pulls a list of the
>> NS and hard-sets the port number for each to 53 (via a manifest constant) .
>> See libc/re
On Fri, Sep 27, 2013 at 4:11 PM, Frank Leonhardt wrote:
> On 27/09/2013 23:08, Terje Elde wrote:
>>
>> On 28. sep. 2013, at 00:03, Frank Leonhardt wrote:
>>
>>> If I understand the way it works correctly, the resolver pulls a list of
>>> the NS and hard-set
On 27/09/2013 23:08, Terje Elde wrote:
On 28. sep. 2013, at 00:03, Frank Leonhardt wrote:
If I understand the way it works correctly, the resolver pulls a list of the NS
and hard-sets the port number for each to 53 (via a manifest constant) . See
libc/resolv/res_init.c. All you need to do
On 28. sep. 2013, at 00:03, Frank Leonhardt wrote:
> If I understand the way it works correctly, the resolver pulls a list of the
> NS and hard-sets the port number for each to 53 (via a manifest constant) .
> See libc/resolv/res_init.c. All you need to do(!) is change this to a va
On 27/09/2013 19:20, Laurent SALIN wrote:
Hello,
I wondering how i can send queries to a dns resolver listening on a
different port than the normaly 53 tcp/udp ?
The situation:
I've got a vps who running NSD as a autoritative nameserver, listening
on tcp/udp 53 and unbound as personnal res
Laurent SALIN laposte.net> writes:
>
> Hello,
> I wondering how i can send queries to a dns resolver listening on a
> different port than the normaly 53 tcp/udp ?
>
> The situation:
> I've got a vps who running NSD as a autoritative nameserver, listening
&
Is there any way to use multiple IPs?
hi,
no I can't. Each VPS got only one IPv4 and I'm really not aware yet
about how IPv6 works.
Laurent SALIN
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questi
Le 27/09/2013 22:28, Terje Elde a écrit :
Why is that a "bad" solution?
You'd cache locally, which is often considered a good thing?
Granted, it's a bit of a weird setup, but still.
I hope it could be esay as put the ip of my "resolver VPS" in the
/etc/resolv
On 27. sep. 2013, at 20:20, Laurent SALIN wrote:
> I've got a "bad" solution, use unbound on the second VPS and maybe tell
> him to ask the 1rst VPS on the unusual tcp/udp port
Why is that a "bad" solution?
You'd cache locally, which is often considered a g
On Fri, Sep 27, 2013, at 13:20, Laurent SALIN wrote:
> Hello,
> I wondering how i can send queries to a dns resolver listening on a
> different port than the normaly 53 tcp/udp ?
>
> The situation:
> I've got a vps who running NSD as a autoritative nameserver, listen
Hello,
I wondering how i can send queries to a dns resolver listening on a
different port than the normaly 53 tcp/udp ?
The situation:
I've got a vps who running NSD as a autoritative nameserver, listening
on tcp/udp 53 and unbound as personnal resolver, listening on a
different tcp/udp por
i found many
> hints to start it using inetd. Since it worked for me there was no reason
> to change it.
>
In general, most administrators will not run ssh via inetd. A more common
configuration is detailed in the FreeBSD handbook at
http:/
nting it out.
>>
>> I will also open port 80 for web access, but i do not want to log those.
>> Because i expect a huge amount of traffic on my server.
>>
>
> Most web servers handle their own logging.
>
> So i only want to log successfull and unsucces
On 16/09/2013 14:36, aurikus grande wrote:
> I try to add a line in /etc/hosts.allow which would allow and log all
> attempts using SSH (sshd).
Actually, by default all logins via ssh are already logged to
/var/log/auth.log
Verb. Sap. tcpwrappers are mostly a lot less useful than they app
1 - 100 of 17292 matches
Mail list logo
