On 2017-10-25, Stefan Monnier wrote:
>>> With such a setup, your host should correctly use your local `bind`
>>> server, and if you ever stop your `bind` server it should start using
>>> your ISP's server instead. And when you restart your `bind` server, it
>>> will switch back to using that.
>>
how can i check the shortcut (default) ?
e.g. [browser : www] does not work but [browser : firefox] does ; btw why
have i 2 versions : firefox & firefox-esr ?
& crtl+alt+t does not start the terminal but [run command prompt : alt+f2]
works.
- do you know a command or a soft doing the job just fo
>> With such a setup, your host should correctly use your local `bind`
>> server, and if you ever stop your `bind` server it should start using
>> your ISP's server instead. And when you restart your `bind` server, it
>> will switch back to using that.
> That is not at all what I am trying to acco
On Tuesday 24 October 2017 23:02:39 Michael Stone wrote:
> On Tue, Oct 24, 2017 at 10:52:03PM -0400, Gene Heskett wrote:
> >But since its worked flawlessly for years, please explain what IS
> > wrong with it.
>
> We've been over this before. Your "search host dns" line doesn't do
> anything at all
On Tue, Oct 24, 2017 at 11:44:59PM -0400, Stefan Monnier wrote:
>
> With such a setup, your host should correctly use your local `bind`
> server, and if you ever stop your `bind` server it should start using
> your ISP's server instead. And when you restart your `bind` server, it
> will switch ba
Gene Heskett composed on 2017-10-24 22:52 (UTC-0400):
>> On Mon, Oct 23, 2017 at 20:31:05 -0400, Gene Heskett wrote:
>>>and made immutable. Particularly is the fact that /etc/resolv.conf
>>> isn't a link to something else but contains:
>>>nameserver 192.168.XX.1
>>>search hostdns
>>>do
> My /etc/resolv.conf looks like this:
> domain example.com
> search example.com.
> nameserver 127.0.0.1
Here's how I'd do it:
- install resolvconf
- move the resolv.conf config you use with bind to somewhere else, like
/etc/resolv.conf.bind
- arrange for the script which starts your `bind` ser
On Tue, Oct 24, 2017 at 10:52:03PM -0400, Gene Heskett wrote:
But since its worked flawlessly for years, please explain what IS wrong
with it.
We've been over this before. Your "search host dns" line doesn't do
anything at all as written, but will screw things up if copied in a
different orde
On Tuesday 24 October 2017 21:06:58 Michael Stone wrote:
> On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote:
> >and made immutable. Particularly is the fact that /etc/resolv.conf
> > isn't a link to something else but contains:
> >
> >nameserver 192.168.XX.1
> >search hostdns
On 10/24/2017 09:14 AM, David Wright wrote:
On Tue 24 Oct 2017 at 08:29:50 (-0400), The Wanderer wrote:
On 2017-10-24 at 08:15, Greg Wooledge wrote:
On Tue, Oct 24, 2017 at 07:31:32AM -0400, The Wanderer wrote:
clear_console clears your console if this is possible. It looks in the
That pro
On Tue, Oct 24, 2017 at 10:18:00PM +0100, Roger Lynn wrote:
> On 24/10/17 08:20, Roberto C. Sánchez wrote:
> > So, it happened again at 03:02:26 that resolv.conf was changed. I
> > looked in the logs and found nothing that appeared to be a close
> > correlation. There were several DHCPREQUEST/DHC
On Mon, Oct 23, 2017 at 08:31:05PM -0400, Gene Heskett wrote:
and made immutable. Particularly is the fact that /etc/resolv.conf isn't
a link to something else but contains:
nameserver 192.168.XX.1
search hostdns
domain coyote.den
Please stop posting that, it uses incorrect syntax (as has
On 24/10/17 08:20, Roberto C. Sánchez wrote:
> So, it happened again at 03:02:26 that resolv.conf was changed. I
> looked in the logs and found nothing that appeared to be a close
> correlation. There were several DHCPREQUEST/DHCPACK exchanges before
> and after, but my network has a near constan
On Tue, Oct 24, 2017 at 08:02:28PM +, J.W. Foster wrote:
> I'm wondering if anyone here has used or been able to install a scanner
> model: Canon - 9000F Mark II Flatbed Scanner - BlackI am currently trying to
> decide if I can use this scanner with current debian stable. There is not
> muc
Hi,
On Mon, 16 Oct 2017 12:34:45 +0500
"Alexander V. Makartsev" wrote:
> For your situation I suggest to upgrade your installation to latest
> release, which is based on jessie, according to official FAQ:
> https://wiki.vyos.net/wiki/FAQ#Usage
> Updating to latest VyOS release is a good thing for
On 10/23/2017 10:40 PM, Robert Arkiletian wrote:
On Mon, Oct 23, 2017 at 2:51 PM, The Wanderer wrote:
On 2017-10-23 at 16:21, Robert Arkiletian wrote:
Just tried this on a different box running Fedora 25 (64) and it
works perfectly, no problem. So I think this is a Debian bug.
Although on Fed
On 10/19/2017 8:31 PM, John Ratliff wrote:
On 10/16/2017 3:35 PM, Christian Seiler wrote:
On 10/16/2017 07:57 PM, John Ratliff wrote:
On 10/15/2017 3:38 AM, Christian Seiler wrote:
Furthermore, the MANAGED_GIDS setting is only for NFSv2/3 and only
for supplementary groups, not the primary grou
On 2017-10-24, Roberto C Sánchez wrote:
>>
>> If it's a SYMLINK and you made the symlink immutable, well, that would
>> explain a whole lot.
>
> It is not a symlink:
>
> debian:/etc# ls -l --full-time /etc/resolv.conf
> -rw-r--r-- 1 root root 25 2017-10-24 07:07:54.513938427 -0400 /etc/resolv.co
On Sat, 21 Oct 2017 16:34:23 +0100
Roger Lynn wrote:
> On 20/10/17 05:00, Celejar wrote:
> > The description of the imagemagick package (8:6.9.7.4+dfsg-11+deb9u1)
> > on my Stable system includes the statements:
> >
> > "This is a dummy package. You can safely purge or remove it."
> >
> > But
On Tue, 24 Oct 2017 08:52:46 +0200
Jörg-Volker Peetz wrote:
> I forgot that you showed the dependency on cups-filters in your original mail.
> On testing cups-filters 1.17.9-1 does not depend on imagemagick, it only
> recommends it. And I use APT::Install-Recommends "false"; in
> /etc/apt/apt.co
On Tue 24 Oct 2017 at 03:15:30 (-0400), Roberto C. Sánchez wrote:
> On Mon, Oct 23, 2017 at 11:05:03PM -0400, Roberto C. Sánchez wrote:
> > On Mon, Oct 23, 2017 at 07:26:38PM -0500, David Wright wrote:
> > >
> > > So if you:
> > > $ ls -l --full-time /etc/resolv.conf
> > > and then look at what ha
On Tue 24 Oct 2017 at 08:29:50 (-0400), The Wanderer wrote:
> On 2017-10-24 at 08:15, Greg Wooledge wrote:
>
> > On Tue, Oct 24, 2017 at 07:31:32AM -0400, The Wanderer wrote:
> >
> >>> clear_console clears your console if this is possible. It looks in the
> >
> >> That program is shipped as part
On Tue, Oct 24, 2017 at 04:27:38PM +0200, tovis wrote:
Hi!
I have using Brain Boxes UC-260 4xserial port card for many years on
Debian 6.0.10 Squeeze. Now I have build a new box with this card for
Stretch and I recognize that old "tricks" are does not work.
The old recipe was
/etc/lilo.conf
appe
Hi!
I have using Brain Boxes UC-260 4xserial port card for many years on
Debian 6.0.10 Squeeze. Now I have build a new box with this card for
Stretch and I recognize that old "tricks" are does not work.
The old recipe was
/etc/lilo.conf
append="8250.nr_uarts=8"
In result I have 8 nodes for serial
On 2017-10-24 at 08:15, Greg Wooledge wrote:
> On Tue, Oct 24, 2017 at 07:31:32AM -0400, The Wanderer wrote:
>
>>> clear_console clears your console if this is possible. It looks in the
>
>> That program is shipped as part of bash, so it looks as if this might
>> actually be considered a bash bu
On Tue, Oct 24, 2017 at 08:12:20AM -0400, Greg Wooledge wrote:
> On Mon, Oct 23, 2017 at 07:33:01PM -0400, Roberto C. Sánchez wrote:
> > So, I edited resolv.conf to my preference and then made it immutable
> > with `chattr +i /etc/resolv.conf`. Several hours later the name server
> > was changed b
On Tue, Oct 24, 2017 at 07:31:32AM -0400, The Wanderer wrote:
> > clear_console clears your console if this is possible. It looks in the
> That program is shipped as part of bash, so it looks as if this might
> actually be considered a bash bug. I'd see about reporting it there, yes
> - either in
On Mon, Oct 23, 2017 at 07:33:01PM -0400, Roberto C. Sánchez wrote:
> So, I edited resolv.conf to my preference and then made it immutable
> with `chattr +i /etc/resolv.conf`. Several hours later the name server
> was changed back to the ISP router's address. That is very odd.
ls -ld /etc/resolv
On 2017-10-24 at 01:40, Robert Arkiletian wrote:
> On Mon, Oct 23, 2017 at 2:51 PM, The Wanderer wrote:
>
>> On 2017-10-23 at 16:21, Robert Arkiletian wrote:
>>
>>> Just tried this on a different box running Fedora 25 (64) and it
>>> works perfectly, no problem. So I think this is a Debian bug.
>
Hi,
when multiple clients (about 70-80) access our NFS servers, we start
encountering timeouts. All servers are running jessie (on VMware)
and we use NFSv4 via IPv6. If only a small number of servers is
accessing the server, everything works fine, on higher load random
servers get a timeout on mo
On Mon, Oct 23, 2017 at 11:05:03PM -0400, Roberto C. Sánchez wrote:
> On Mon, Oct 23, 2017 at 07:26:38PM -0500, David Wright wrote:
> >
> > So if you:
> > $ ls -l --full-time /etc/resolv.conf
> > and then look at what happened at that precise time in /var/log/syslog
> > or wherever your logs are b
31 matches
Mail list logo
