On Sun, Apr 10, 2022 at 09:44:59PM -0700, David Christensen wrote:
> On 4/10/22 19:58, Default User wrote:
> > Hello!
> >
> > My setup:
> > - single home x86-64 computer running Debian 11 Stable, up to date.
> > - one 4-Tb external usb hard drive to use as a backup device, labeled MSD1.
> > -
On 4/10/22 19:58, Default User wrote:
Hello!
My setup:
- single home x86-64 computer running Debian 11 Stable, up to date.
- one 4-Tb external usb hard drive to use as a backup device, labeled MSD1.
- another identical usb hard drive, labeled MSD2, to use as a copy of the
backups on MSD1.
- the
On 11/4/22 11:46 am, David Wright wrote:
There are tabooext and taboopat directives for ignoring files in
logrotated.d, and I would have thought it reasonable to exclude
these sorts of housekeeping files by default, because they're very
likely to contain some duplication. I would file a bug
On Sun, Apr 10, 2022 at 11:13 PM David wrote:
> On Mon, 11 Apr 2022 at 12:59, Default User
> wrote:
>
> > Then I try to use rsync to make an identical copy of backup device MSD1
> on an absolutely identical 4-Tb external usb hard drive,
> > labeled MSD2, using this command:
> >
> > sudo rsync
On Mon 11 Apr 2022 at 10:07:53 (+0800), Jeremy Ardley wrote:
> I have systems (armbian) that had anomalous behaviour.
>
> This included sometimes writing to /var/log/syslog.1 rather than to
> /var/log/syslog (which was created, but zero size)
>
> Additionally the logrotate was happening daily or
On Mon, 11 Apr 2022 at 12:59, Default User wrote:
> Then I try to use rsync to make an identical copy of backup device MSD1 on an
> absolutely identical 4-Tb external usb hard drive,
> labeled MSD2, using this command:
>
> sudo rsync -aAXHxvv --delete --info=progress2,stats2,name2
>
Hello!
My setup:
- single home x86-64 computer running Debian 11 Stable, up to date.
- one 4-Tb external usb hard drive to use as a backup device, labeled MSD1.
- another identical usb hard drive, labeled MSD2, to use as a copy of the
backups on MSD1.
- the computer and all storage devices are
On 2022-04-09 at 23:09 +0300, George wrote:
> Thanks for the reply!
>
> So any ideas how to solve that problem? I tried a lot of things with
> no luck. I didnt find the particular file at that place.
> I clean the log files and still get these annoying notifications.
Try adding
owner
I have systems (armbian) that had anomalous behaviour.
This included sometimes writing to /var/log/syslog.1 rather than to
/var/log/syslog (which was created, but zero size)
Additionally the logrotate was happening daily or twice daily when
seemingly configured for weekly rotates
Anyway
Hola,
- Alguna sugerencia para activar las tildes y eñes en la consola de X?
Todo bien en la consola modo texto pero no así en la consola de X.
- Se mantiene la desactivación de X para que al iniciar, el sistema se
quede en consola?
Recuerdo en las versiones anteriores era así: update-rc.d
On Mon, 11 Apr 2022 at 09:50, Greg Wooledge wrote:
> On Mon, Apr 11, 2022 at 09:34:42AM +1000, David wrote:
> > On Mon, 11 Apr 2022 at 09:24, David Wright wrote:
> >
> > > systemctl disable mlocate.service before you fiddle with its
> > > configuration, then enable it afterwards.
> >
> > Hi, I
Dear Debian community,
First of all many thanks to everybody who has replied to my message and
contributed ideas to solve the issue.
On 3 Apr 2022 22:41:44, Greg Wooledge wrote:
> So... you've got some wild stuff going on here.
>
> You have two interfaces. One of them was named enp2s0 and then
On Mon, Apr 11, 2022 at 09:34:42AM +1000, David wrote:
> On Mon, 11 Apr 2022 at 09:24, David Wright wrote:
>
> > systemctl disable mlocate.service before you fiddle with its
> > configuration, then enable it afterwards.
>
> Hi, I think you need "stop" and "start" there, not "disable" and
>
On Mon, 11 Apr 2022 at 09:24, David Wright wrote:
> systemctl disable mlocate.service before you fiddle with its
> configuration, then enable it afterwards.
Hi, I think you need "stop" and "start" there, not "disable" and
and "enable".
Or maybe "systemctl daemon-reload" although I'm not sure
On Sun 10 Apr 2022 at 09:52:15 (-0500), Roy J. Tellason, Sr. wrote:
> On Saturday 09 April 2022 01:22:08 pm Charles Curley wrote:
> > On Sat, 9 Apr 2022 11:04:18 -0500
> > "Roy J. Tellason, Sr." wrote:
> >
> > > How do I find out where this is invoked, so I can get rid of it?
> >
> > You may
On Sun 10 Apr 2022 at 10:04:53 (-0400), Greg Wooledge wrote:
> On Sun, Apr 10, 2022 at 11:33:53AM +0200, Linux-Fan wrote:
> > Greg Wooledge writes:
> > > unicorn:~$ less /lib/systemd/system/mlocate.timer
> > > [Unit]
> > > Description=Updates mlocate database every day
> > >
> > > [Timer]
> > >
On Sunday, 10 April 2022 09:54:34 EDT Brian wrote:
> On Sun 10 Apr 2022 at 09:19:43 -0400, gene heskett wrote:
> > On Sunday, 10 April 2022 08:40:29 EDT Brian wrote:
> > > /usr/lib/cups/backend/snmp
> >
> > The only machine I have here that has that file installed, an rpi4,
> > does not expose
On sab, 2022-04-09 at 04:28 -0400, Bijan Soleymani wrote:
> On 2022-04-09 03:52, nimrod wrote:
> > Thanks for your advice. Unfortunately I couldn't find any setting
> > about
> > Postscript, PCL or such in CUPS, HPLIP and the usual Gnome
> > utilities to
> > manage printers.
> >
> > The only
On Sunday, 10 April 2022 10:04:53 EDT Greg Wooledge wrote:
> On Sun, Apr 10, 2022 at 11:33:53AM +0200, Linux-Fan wrote:
> > Greg Wooledge writes:
> > > unicorn:~$ less /lib/systemd/system/mlocate.timer
> > > [Unit]
> > > Description=Updates mlocate database every day
> > >
> > > [Timer]
> > >
On Sun 10 Apr 2022 at 21:29:30 +0200, to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 08:19:52PM +0100, Brian wrote:
>
> [...]
>
> > > forbidden of trying to do network scans, but the sysadmin wants to
> > > know. I can't blame him (I'm on speaking terms with him ;-)
> >
> > Not forbidden?
>
On Sun, Apr 10, 2022 at 08:19:52PM +0100, Brian wrote:
[...]
> > forbidden of trying to do network scans, but the sysadmin wants to
> > know. I can't blame him (I'm on speaking terms with him ;-)
>
> Not forbidden?
>
> I know a corporate network or two which would get you disconnected
> if
On Sun 10 Apr 2022 at 20:39:15 +0200, to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 06:47:36PM +0100, Brian wrote:
> > On Sun 10 Apr 2022 at 15:40:28 +0200, to...@tuxteam.de wrote:
> >
> > > On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote:
> > >
> > > [...]
> > >
> > > > Many
On 2022-04-10 at 14:25, Brian wrote:
> On Sun 10 Apr 2022 at 08:52:09 -0400, The Wanderer wrote:
>
>> On 2022-04-10 at 08:38, Brian wrote:
>
> [...]
>
>>> The CUPS web interface is not designed to show the IP address but
>>> to display the URI.
>>
>> This, I think, is exactly the detail
On Sun 10 Apr 2022 at 12:04:05 (-0400), Greg Wooledge wrote:
> On Sun, Apr 10, 2022 at 03:49:02PM +0100, Darac Marjal wrote:
> > Systemd already supports this.
> >
> > * AccuracySec= Specify the accuracy the timer shall elapse with. [...]
> > Within this time window, the expiry time shall be
On Sun, Apr 10, 2022 at 06:47:36PM +0100, Brian wrote:
> On Sun 10 Apr 2022 at 15:40:28 +0200, to...@tuxteam.de wrote:
>
> > On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote:
> >
> > [...]
> >
> > > Many printers provide an snmp (Simple Network Management Protocol)
> > > service on port
On Sun 10 Apr 2022 at 08:52:09 -0400, The Wanderer wrote:
> On 2022-04-10 at 08:38, Brian wrote:
[...]
> > The CUPS web interface is not designed to show the IP address but to
> > display the URI.
>
> This, I think, is exactly the detail that's being complained of. If CUPS
> knows the IP
On Sun 10 Apr 2022 at 15:40:28 +0200, to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote:
>
> [...]
>
> > Many printers provide an snmp (Simple Network Management Protocol)
> > service on port 9100. Check with
> >
> > nmap 10.76.172.100
>
> I know a corporate
On Sun, Apr 10, 2022 at 03:49:02PM +0100, Darac Marjal wrote:
> Systemd already supports this.
>
> * AccuracySec= Specify the accuracy the timer shall elapse with. [...]
> Within this time window, the expiry time shall be placed at a host-specific,
> randomized, but stable position.
>
> *
On 2022-04-10, rhkra...@gmail.com wrote:
> On Friday, April 08, 2022 08:17:14 AM gene heskett wrote:
>> I think Ben Franklin said it first, First, we get rid of all the lawyers.
>
> Billy (Shakespeare) said it before Ben. But I would not be surprised to find
> that someone said it much earlier
On Saturday 09 April 2022 05:11:39 pm Greg Wooledge wrote:
> On Sat, Apr 09, 2022 at 04:59:04PM -0400, gene heskett wrote:
> > On Saturday, 9 April 2022 16:35:26 EDT Greg Wooledge wrote:
> > > grep daily /etc/crontab
> >
> > Matches mine too Greg, so I expect thats default, but why is Roy's going
On 10/04/2022 15:29, Greg Wooledge wrote:
On Sun, Apr 10, 2022 at 06:03:13AM -0400, gene heskett wrote:
Thats fine, as long as the systemd stuff is disabled by finding an entry
in the presently logged in users ~/.config, but I do not consider that as
a user item. thats (updatedb) sysadmin
On Sun 10 Apr 2022 at 09:31:59 -0400, gene heskett wrote:
> On Sunday, 10 April 2022 08:54:07 EDT Brian wrote:
> > On Sun 10 Apr 2022 at 05:46:35 -0400, gene heskett wrote:
> >
> > [...]
> >
> > > This, FWIW, has nothing to do with cups and printer sharing, cups
> > > does
> > > its own
On Saturday 09 April 2022 01:22:08 pm Charles Curley wrote:
> On Sat, 9 Apr 2022 11:04:18 -0500
> "Roy J. Tellason, Sr." wrote:
>
> > How do I find out where this is invoked, so I can get rid of it?
>
> You may not want to get rid of it. That's the process that updates the
> database for the
On Sun 10 Apr 2022 at 10:05:09 -0400, The Wanderer wrote:
> On 2022-04-10 at 09:54, Brian wrote:
>
> > The snmp backend is not installed in the location I gave but has
> > to be moved there. Do either
> >
> > mv /usr/lib/cups/backend-available/snmp /usr/lib/cups/backend/snmp
> >
> > or
> >
On Saturday 09 April 2022 12:39:45 pm Roberto C. Sánchez wrote:
> On Sat, Apr 09, 2022 at 11:04:18AM -0500, Roy J. Tellason, Sr. wrote:
> > So around midnight I am seeing a burst of activity, which sometimes
> > interferes with whatever else I happen to be doing at the time. Looking at
> > the
On Sun, Apr 10, 2022 at 06:03:13AM -0400, gene heskett wrote:
> Thats fine, as long as the systemd stuff is disabled by finding an entry
> in the presently logged in users ~/.config, but I do not consider that as
> a user item. thats (updatedb) sysadmin stuff, and much of this hoohah
> could be
On 2022-04-10 at 09:54, Brian wrote:
> The snmp backend is not installed in the location I gave but has
> to be moved there. Do either
>
> mv /usr/lib/cups/backend-available/snmp /usr/lib/cups/backend/snmp
>
> or
>
> dpkg-reconfigure cups
I've never taken specific action in either of
On Sun, Apr 10, 2022 at 11:33:53AM +0200, Linux-Fan wrote:
> Greg Wooledge writes:
> > unicorn:~$ less /lib/systemd/system/mlocate.timer
> > [Unit]
> > Description=Updates mlocate database every day
> >
> > [Timer]
> > OnCalendar=daily
> > AccuracySec=24h
> > Persistent=true
> >
> > [Install]
>
On Sun 10 Apr 2022 at 09:19:43 -0400, gene heskett wrote:
> On Sunday, 10 April 2022 08:40:29 EDT Brian wrote:
> > /usr/lib/cups/backend/snmp
> The only machine I have here that has that file installed, an rpi4, does
> not expose the printers address, only:
> pi@rpi4:~ $ sudo
On Sun, Apr 10, 2022 at 01:40:29PM +0100, Brian wrote:
[...]
> Many printers provide an snmp (Simple Network Management Protocol)
> service on port 9100. Check with
>
> nmap 10.76.172.100
I know a corporate network or two which would get you disconnected
if you do that :)
Then you've got to
On Sun 10 Apr 2022 at 08:10:17 -0400, gene heskett wrote:
> On Sunday, 10 April 2022 07:17:42 EDT The Wanderer wrote:
> > On 2022-04-10 at 07:08, gene heskett wrote:
> > > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> > >> I just don't install it.
> > >
> > > And how do you
On Sunday, 10 April 2022 08:54:07 EDT Brian wrote:
> On Sun 10 Apr 2022 at 05:46:35 -0400, gene heskett wrote:
>
> [...]
>
> > This, FWIW, has nothing to do with cups and printer sharing, cups
> > does
> > its own advertising. All printers here are attached to this machine,
> > marked as
On Sunday, 10 April 2022 08:40:29 EDT Brian wrote:
> /usr/lib/cups/backend/snmp
The only machine I have here that has that file installed, an rpi4, does
not expose the printers address, only:
pi@rpi4:~ $ sudo /usr/lib/cups/backend/snmp
network lpd://BRN30055C8A2DC8/BINARY_P1 "Brother
On Sun 10 Apr 2022 at 05:46:35 -0400, gene heskett wrote:
[...]
> This, FWIW, has nothing to do with cups and printer sharing, cups does
> its own advertising. All printers here are attached to this machine,
> marked as shareable and I can put stuff on their output trays from any
> machine
On 2022-04-10 at 08:38, Brian wrote:
> On Sat 09 Apr 2022 at 20:21:12 -0400, The Wanderer wrote:
>
>> On 2022-04-09 at 07:56, Brian wrote:
>>> It is straightforward, I don't know about obvious to all users.
>>>
>>> avahi-browse -rt _ipp._tcp
>>
>> Does that get the information from CUPS?
>>
On Sunday, 10 April 2022 08:02:32 EDT to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 07:46:37AM -0400, gene heskett wrote:
> > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> > > AVAHI_DAEMON_DETECT_LOCAL=0 into some /etc/default/avahi-daemon.
> >
> > Checking all my machines,
On Fri 08 Apr 2022 at 13:22:26 -0400, Greg Wooledge wrote:
> On Fri, Apr 08, 2022 at 06:03:47PM +0100, Tixy wrote:
> > On Fri, 2022-04-08 at 17:59 +0100, Tixy wrote:
> > > On Fri, 2022-04-08 at 12:10 -0400, Greg Wooledge wrote:
> > > > Unfortunately, I was not able to find ANY way to determine
On Sat 09 Apr 2022 at 20:21:12 -0400, The Wanderer wrote:
> On 2022-04-09 at 07:56, Brian wrote:
>
> > On Fri 08 Apr 2022 at 19:45:41 -0400, The Wanderer wrote:
> >
> >> (This is probably both overly long and overly repetitive, among
> >> possibly other undesirable things, but I'm running short
On Friday, April 08, 2022 08:17:14 AM gene heskett wrote:
> I think Ben Franklin said it first, First, we get rid of all the lawyers.
Billy (Shakespeare) said it before Ben. But I would not be surprised to find
that someone said it much earlier than that.
I once looked into the origin of ~"I
On 2022-04-10 at 08:10, gene heskett wrote:
> On Sunday, 10 April 2022 07:17:42 EDT The Wanderer wrote:
>
>> On 2022-04-10 at 07:08, gene heskett wrote:
>>> And how do you accomplish that? Its automatically installed
>>> AFAIK. And once installed, apt will not remove it without
>>> destroying
On Sunday, 10 April 2022 07:17:42 EDT The Wanderer wrote:
> On 2022-04-10 at 07:08, gene heskett wrote:
> > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> >> I just don't install it.
> >
> > And how do you accomplish that? Its automatically installed AFAIK.
> > And once
On Sun, Apr 10, 2022 at 07:46:37AM -0400, gene heskett wrote:
> On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
>
> > AVAHI_DAEMON_DETECT_LOCAL=0 into some /etc/default/avahi-daemon.
>
> Checking all my machines, all but one was set to 1, fixed the others and
> redid the initramfs
On Sun, Apr 10, 2022 at 07:17:42AM -0400, The Wanderer wrote:
> On 2022-04-10 at 07:08, gene heskett wrote:
>
> > On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
>
> >> I just don't install it.
> >
> > And how do you accomplish that? Its automatically installed AFAIK.
> > And once
On Sun, Apr 10, 2022 at 07:08:36AM -0400, gene heskett wrote:
> On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
[...]
> > be putting AVAHI_DAEMON_DETECT_LOCAL=0 into some
> > /etc/default/avahi-daemon.
>
> Then whyintarnation does it not say that in what serves as a man page?
On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> AVAHI_DAEMON_DETECT_LOCAL=0 into some /etc/default/avahi-daemon.
Checking all my machines, all but one was set to 1, fixed the others and
redid the initramfs as it said in 2 of the 5, in that file.
Thank you for that Tomas, now
On 2022-04-10 at 07:08, gene heskett wrote:
> On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
>> I just don't install it.
>
> And how do you accomplish that? Its automatically installed AFAIK.
> And once installed, apt will not remove it without destroying the
> install. rm or
On Sunday, 10 April 2022 06:06:31 EDT to...@tuxteam.de wrote:
> On Sun, Apr 10, 2022 at 05:46:35AM -0400, gene heskett wrote:
>
> [...]
>
> > Then why, after a decade and change of bitching about it because it
> > insists on putting a 169.254.xx,yy address in ones routing table that
> > only
On Sun, Apr 10, 2022 at 05:46:35AM -0400, gene heskett wrote:
[...]
> Then why, after a decade and change of bitching about it because it
> insists on putting a 169.254.xx,yy address in ones routing table that
> only removing avahi fixes, has it not been fixed?
This would be an IPv4
On Sunday, 10 April 2022 05:33:53 EDT Linux-Fan wrote:
> Greg Wooledge writes:
> > On Sat, Apr 09, 2022 at 09:26:58PM -0600, Charles Curley wrote:
> > > Two of my machines have their database files dated at midnight or
> > > one
> > > minute after.
> > >
> > > Possibly because updatedb is run by
On Sunday, 10 April 2022 02:33:21 EDT to...@tuxteam.de wrote:
> On Sat, Apr 09, 2022 at 08:21:12PM -0400, The Wanderer wrote:
>
> [...]
>
> > I honestly don't know the subject very well myself, but I'd
> > definitely
> > like to know it better than I do.
> >
> > One aspect of Windows printer
Greg Wooledge writes:
On Sat, Apr 09, 2022 at 09:26:58PM -0600, Charles Curley wrote:
> Two of my machines have their database files dated at midnight or one
> minute after.
>
> Possibly because updatedb is run by a systemd timer, not cron.
[...]
# skip in favour of systemd timer
if [ -d
Le samedi 09 avril 2022 à 19:19 +0200, ajh-valmer a écrit :
> On Saturday 09 April 2022 17:31:17 kaliderus wrote:
> > Le sam. 9 avr. 2022 à 11:06 a écrit :
> > > - tes pilotes d'impression sont fournis par Debian? ou par
> > > Brother?
> > > J'aurais tendance à dire que si ton imprimante est
El 2022-04-09 a las 13:42 -0500, Aristobulo Pinzon Gmail escribió:
> Gracias por tu interés.
> Tenía mutt como aplicación de correo configurada en el navegador y en
> aplicaciones predeterminadas.
> Pero de pronto sucede que cuando deseo contestar algún mensaje, no abre el
> Mutt para
On Sat, Apr 09, 2022 at 08:21:12PM -0400, The Wanderer wrote:
[...]
> I honestly don't know the subject very well myself, but I'd definitely
> like to know it better than I do.
>
> One aspect of Windows printer sharing is that it makes it possible to
> connect a printer not directly to the
On Sat, Apr 09, 2022 at 11:59:07PM -0400, Greg Wooledge wrote:
[...]
> Oh well. It clearly isn't bothering me (I'm usually in bed before
> midnight, though not always), so I never had to look into it. I'm sure
> someone felt it was a "good idea" to move things from perfectly normal
> and
On 04/09/2022 01:17 PM, davidson wrote:
On Sat, 9 Apr 2022 Richard Owlett wrote:
On 04/08/2022 01:18 AM, Tixy wrote:
On Thu, 2022-04-07 at 09:40 -0500, Richard Owlett wrote:
I need a *HTML* copy of "Installation Guide for 64-bit PC (amd64)" for
*OFFLINE* use.
The HTML links on
66 matches
Mail list logo
