Re: Reply configuration (was: All-in-One printer: HP OfficeJet 8012)
On 11/08/2021 12:25, Gene Heskett wrote: On Wednesday 11 August 2021 04:02:14 Polyna-Maude Racicot-Summerside wrote: Debian is about choice Polyna. That is mine. Quit monopolizing the conversation unless you are helping the user SOLVE his/her problem. +1 -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Apparmor pain
On 29/01/2021 13:27, Reco wrote:
Hi.
On Fri, Jan 29, 2021 at 12:49:42PM +, Tony van der Hoff wrote:
This is a simplified scenario: Say I have 2 machines, both running Debian 10.7.
Each machine has 3 users: A, B and C. Each machine has an identical (mantained
by Unison) directoery: /home/C/pictures, with permissions ugo:rwx owned by C.
Each file therein has permissions ugo:r
...
I don't understand why my two machines are behaving so differently.
uid difference between hosts A and B, most probably.
Along the other things, thunderbird's apparmor policy contains this:
owner @{HOME}/** r,
I.e. it's allowed to read any file at /home as long as the file is owned
by thunderbird's uid.
I don't think I really want apparmor running at all,
Add apparmor=0 to kernel's cmdline. Building a kernel without apparmor
helps with that too, but that's straying too far from Debian's defaults.
The debian wiki gives me a way to disable apparmor by patching grub,
but that seems like overkill.
You probably got it wrong. Modifying a kernel cmdline and rebuilding
grub with custom patches are different, and they should suggest former
at Debian's wiki.
Does anyone pease have any suggestions on how to enable an application
without major surgery? any help appreciated. Thanks
Disabling a problematic apparmor profile altogether is done by:
/usr/sbin/aa-disable /usr/bin/thunderbird
Disabling a problematic apparmor profile but keeping audit records
generation is done by
/usr/sbin/aa-complain /usr/bin/thunderbird
You'll want the first one, probably.
Reco
Thanks, Reco, that was just the information I needed. I had to install
apparmor-utils, but otherwise aa-disable did the job.
Cheers, Tony
--
Tony van der Hoff| mailto:t...@vanderhoff.org
Buckinghamshire, England |
Apparmor pain
This is a simplified scenario: Say I have 2 machines, both running Debian 10.7. Each machine has 3 users: A, B and C. Each machine has an identical (mantained by Unison) directoery: /home/C/pictures, with permissions ugo:rwx owned by C. Each file therein has permissions ugo:r Both machines can access any file within pictures with no problems, as one would expect. However, using Thunderbird, machine A can attach any file from pictures, but machine B fails silently to do so. Examining the syslog for B it would appear that apparmor is preventing access. From my web research it appears that apparmor was introduced by default at debian 10. On machine B it is blocking Thunderbird, but not on A. I don't understand why my two machines are behaving so differently. I don't think I really want apparmor running at all, but at least I'd like either machine to access C's files. Apparmor's man page gives eye-watering detail, but I can'tr find any easily usable configuration suggestions. The debian wiki gives me a way to disable apparmor by patching grub, but that seems like overkill. Does anyone pease have any suggestions on how to enable an application without major surgery? any help appreciated. Thanks -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: MariaDB database under /home
On 11/11/2020 15:42, Nicolas George wrote: Tony van der Hoff (12020-11-11): It is known that the maintainers of MariaDB deprecate the database files residing under /home, in fact going so far as making it an error, unless /usr/lib/systemd/system/mariadb.service has ProtectHome=true commented out. Now, this is all very well, and I'm sure there are good reasons for it, but I want my databases to reside in /home. Unfortunately, each time there's an upgrade to the package my preferred setting gets overwritten, resulting in MariaDB failing to start, and my having to edit the service file on a number of machines. I'd consider this a bug, but is there at least any way of making my change more permanent? It is not a bug, only files residing in /etc can be modified by the administrator. I suggest you read about systemd's drop-in configuration files and the edit command in the systemctl(1) man page. Regards, OK, I see, thanks. For the archive a useful source might be: https://www.computernetworkingnotes.com/linux-tutorials/systemd-unit-configuration-files-explained.html -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
MariaDB database under /home
It is known that the maintainers of MariaDB deprecate the database files residing under /home, in fact going so far as making it an error, unless /usr/lib/systemd/system/mariadb.service has ProtectHome=true commented out. Now, this is all very well, and I'm sure there are good reasons for it, but I want my databases to reside in /home. Unfortunately, each time there's an upgrade to the package my preferred setting gets overwritten, resulting in MariaDB failing to start, and my having to edit the service file on a number of machines. I'd consider this a bug, but is there at least any way of making my change more permanent? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: shells (was Re: Zoom.)
On 20/10/2020 15:51, rhkra...@gmail.com wrote: Top posting intentionally as I don't think any (or much) context is required. so, hijacking a thread instead? :-) -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: stretch -> buster upgrade fails
On 11/05/2020 09:23, Tony van der Hoff wrote: On 10/05/2020 19:02, Sven Hartge wrote: Tony van der Hoff wrote: E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi' E: Sub-process returned an error code I don't know where to find a verbose log. Any suggestions as to how tp proceed please? What happens when you run appstreamcli refresh-cache manually as root? Grüße, S! root@debian-jane:~# appstreamcli refresh-cacheappstreamcli refresh-cache Command 'refresh-cacheappstreamcli' is unknown. Doing it correctly: root@debian-jane:~# appstreamcli refresh-cache AppStream cache update is not necessary. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: stretch -> buster upgrade fails
On 10/05/2020 19:02, Sven Hartge wrote: Tony van der Hoff wrote: E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi' E: Sub-process returned an error code I don't know where to find a verbose log. Any suggestions as to how tp proceed please? What happens when you run appstreamcli refresh-cache manually as root? Grüße, S! root@debian-jane:~# appstreamcli refresh-cacheappstreamcli refresh-cache Command 'refresh-cacheappstreamcli' is unknown. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
stretch -> buster upgrade fails
hi, I've just tried to upgrade a workstation on my network from stretch to buster. I changed all references to stretch in sources.list to buster, and ran apt-get upgrade,with the following results: root@debian-jane:~# apt-get update Get:1 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB] Get:2 http://ftp.uk.debian.org/debian buster InRelease [121 kB] Get:3 http://ftp.uk.debian.org/debian buster-updates InRelease [49.3 kB] Get:4 http://security.debian.org/debian-security buster/updates/main amd64 Packages [197 kB] Get:5 http://security.debian.org/debian-security buster/updates/main Translation-en [106 kB] Get:6 http://security.debian.org/debian-security buster/updates/non-free amd64 Packages [552 B] Get:7 http://security.debian.org/debian-security buster/updates/non-free Translation-en [344 B] Get:8 http://ftp.uk.debian.org/debian buster/main amd64 Packages [7,905 kB] Get:9 http://ftp.uk.debian.org/debian buster/main Translation-en [5,969 kB] Get:10 http://ftp.uk.debian.org/debian buster/main amd64 DEP-11 Metadata [3,807 kB] Get:11 http://ftp.uk.debian.org/debian buster/main DEP-11 64x64 Icons [7,596 kB] Get:12 http://ftp.uk.debian.org/debian buster/main DEP-11 128x128 Icons [12.8 MB] Get:13 http://ftp.uk.debian.org/debian buster/contrib amd64 Packages [51.0 kB] Get:14 http://ftp.uk.debian.org/debian buster/contrib Translation-en [44.7 kB] Get:15 http://ftp.uk.debian.org/debian buster/contrib amd64 DEP-11 Metadata [11.5 kB] Get:16 http://ftp.uk.debian.org/debian buster/contrib DEP-11 64x64 Icons [110 kB] Get:17 http://ftp.uk.debian.org/debian buster/contrib DEP-11 128x128 Icons [226 kB] Get:18 http://ftp.uk.debian.org/debian buster/non-free amd64 Packages [87.7 kB] Get:19 http://ftp.uk.debian.org/debian buster/non-free Translation-en [88.9 kB] Get:20 http://ftp.uk.debian.org/debian buster/non-free amd64 DEP-11 Metadata [9,096 B] Get:21 http://ftp.uk.debian.org/debian buster/non-free DEP-11 64x64 Icons [38.3 kB] Get:22 http://ftp.uk.debian.org/debian buster/non-free DEP-11 128x128 Icons [6,725 B] Get:23 http://ftp.uk.debian.org/debian buster-updates/main amd64 Packages [7,380 B] Get:24 http://ftp.uk.debian.org/debian buster-updates/main Translation-en [5,166 B] Fetched 39.3 MB in 14s (2,792 kB/s) The AppStream system cache was updated, but some errors were detected, which might lead to missing metadata. Refer to the verbose log for more information. Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi' E: Sub-process returned an error code I don't know where to find a verbose log. Any suggestions as to how tp proceed please? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Seeing command history when using MATE terminal
On 18/04/2020 11:19, Richard Owlett wrote: I can see any *ONE* previous commands by using the up-arrow key. But I need to see the *complete* history. F1 is no "Help". Obviously its stored in a file. Where? TIA Well, for Bash, the file is at ~/.bash_history (as set in $HISTFILE), but, beware, it is only updated when the terminal is closed. Bash provides the 'history' command, which shows the entire history. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Buster without systemd?
On 23/03/2020 15:15, Michael Howard wrote: On 23/03/2020 14:28, Patrick Bartek wrote: On Mon, 23 Mar 2020 08:37:47 -0400 Jude DaShiell wrote: I know it's a sensitive subject, and I really don't want to upset the list, there's been enough of that already, but why are some people so afraid of systemd? I have used it since the beginning of jessie, through stretch, and now buster, and have had no problems with it. I ask the question in all innocence, purely to understand whypeople seem to want to jump through hoops to avoid it. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Advice on upgrading to SSD
On Monday 02 March 2020 06:28:58 Tony van der Hoff wrote: Hi, I'm currently running Buster on a 5 year old GigaByte motherboard with a 10-year old Raid-1 array on 2 500GB disks. Although it is running fine, I'm becoming a bit concerned about the longevity of this storage, so I'm planning to upgrade it to a 500GB or maybe 1TB SSD from Crucial. My plan would be to install the SSD in the cage, and dd the contents of the array onto the SSD. I would then change the BIOS to boot from the SSD, making the RAID array redundant. Can someone please tell me whether this plan is feasible, and what pitfalls I might encounter? Thanks to all who replied. Gene didn't address my problem, but made the very useful observation that disks spinning 24/7 don't really die. Perhaps I shouldn't worry about replacing them. Dan gave a useful step-by-step procedure for copying at file level. This method is slightly problematical for me as it includes "make changes to new /etc/fstab" and "make changes to bootloader to set new root filesystem", neither of which I feel feel comfortable with, due to lack of knowledge. I'll certainly abandon my plan to dd the whole filesystem. Basti and Deloptes propose to add the SSD as a third drive to the RAID. Very attractive, but would involve complications if the SSD is not identical in size to the old spinners. Andrei supports file-level copying, so I'll stick to that. Joe supports the idea of adding the drive to the RAID, but makes no reference to dealing wth the size difference. Alex highlights the downside of size difference. David and Sarunas suggests doing a system reinstall on the SSD, leaving my data on the RAID. Whilst a useful upgrade, I don't really understand how that addresses my problem. (if I have one!) Michael and Deloptes poo-poo that suggestion, with which I concur. Andy suggests that I should continue using RAID, instead of reverting to a single disk. Thank you very much for this helpful suggestion, I considered it originally, but abandoned it on cost grounds. When I originally built this system with RAID, 10 years ago, I was very reliant on data integrity. I now no longer have such a pressing need, and am quite happy to rely on a single disk, with nightly rsync backups to an off-site server. I certainly have no need for the always-on data that RAID provides. Finally, Geoff supports Andy's suggestion, and in addition, interestingly, mentions NVME to replace SATA SSD. Attractive, but costly. So, you have all given me plenty to think about, for which I'm grateful. I guess I'll go with s single SSD onto which I'll copy the data from the RAID. Thank you all for helping me make up my mind. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Advice on upgrading to SSD
Hi, I'm currently running Buster on a 5 year old GigaByte motherboard with a 10-year old Raid-1 array on 2 500GB disks. Although it is running fine, I'm becoming a bit concerned about the longevity of this storage, so I'm planning to upgrade it to a 500GB or maybe 1TB SSD from Crucial. My plan would be to install the SSD in the cage, and dd the contents of the array onto the SSD. I would then change the BIOS to boot from the SSD, making the RAID array redundant. Can someone please tell me whether this plan is feasible, and what pitfalls I might encounter? Thanks, Tony -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: identity confusion
On 03/02/2020 15:11, to...@tuxteam.de wrote: On Mon, Feb 03, 2020 at 09:57:13AM -0500, Wayne Sallee wrote: [...] That's strange I thought I had it set for text for this list. But it wasn't. It's fixed now. Things happen. It is now. And I thank you very much :-) Cheers -- tomás Now all *you* need to do is fix your sig.sep :) -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Apache2/PHP7 fails in Buster
On 16/01/2020 17:48, Roberto C. Sánchez wrote: On Thu, Jan 16, 2020 at 12:43:17PM -0500, Greg Wooledge wrote: Well, it seems it's failing because it tries to enable the php7.3 module -- which it can't do, because the module's not THERE. If it were me, I would attempt to purge this package (not just remove), and then reinstall it. The --reinstall should have handled that. If purging fails because of a2enmod being unable to find the module and manipulate it in various ways, then it might be necessary to short-circuit the prerm/postinst/etc. scripts so that they do nothing, just so you can purge everything. The normal way to do that with a prerm or postinst script is to stick "exit 0" near the top of it. That would be a good approach. Thanks to all, and especially Roberto, for pointing me in the right direction. I did ~# dpkg -P libapache2-mod-php7.3 libapache2-mod-php, because it reported a dependency on libapache2-mod-php, which went smoothly. I than did apt-get install libapache2-mod-php, and systemctl restart apache2. It now runs phpinfo() without problem. I'm now stuck with my php script in my home being commented out by Apache, but I'm sure that's just a configuration issue. Thanks again chaps -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Apache2/PHP7 fails in Buster
On 16/01/2020 16:39, Roberto C. Sánchez wrote: On Thu, Jan 16, 2020 at 03:55:46PM +, Tony van der Hoff wrote: On 16/01/2020 15:11, Roberto C. Sánchez wrote: Can you send me (directly) the files from that system named '/var/lib/dpkg/info/libapache2-mod-php7.3*'? Apparently not: : host mailly.debian.org[82.195.75.114] said: 550 HELO mismatch Forged HELO for (shell.localdomain) (in reply to RCPT TO command) That's bizzare. I've been receiving other mail at this address, so I wonder if it might be an issue on your side. It may well be. However this Postfix server has been running for many years, and I've not had any such occurrence. But that's not important right now. archive attached Hmm. I thought the list might reject that, but it seems I was mistaken. Either way, your postinst script seems fine. My recommendation is to edit libapache2-mod-php7.3.postinst to add on a new line after 'set -e': set -x That will make bash trace the execution to the console. After you have added that 'set -x' then: sudo dpkg --pending --configure That should leave your terminal output right near the point in the script where it is erroring out. If you still have questions at that point then post the output of the dpkg command. OK, fine, thanks. I'm afraid my bash-fu is a little rusty, so I'd appreciate you taking a look. Thanks, Tony -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England | dpkg.tar.gz Description: application/gzip
Re: Apache2/PHP7 fails in Buster
On 16/01/2020 15:11, Roberto C. Sánchez wrote: On Thu, Jan 16, 2020 at 03:07:18PM +, Tony van der Hoff wrote: On 16/01/2020 15:03, Roberto C. Sánchez wrote: Well, you are definitely missing the module file. It should be in that package: apt-file search php7.3.load libapache2-mod-php7.3: /etc/apache2/mods-available/php7.3.load I recommend this: sudo apt-get install --reinstall libapache2-mod-php7.3 After that recheck the contents of /etc/apache2/mods-available to see if the file is there. dpkg: error processing package libapache2-mod-php7.3 (--configure): installed libapache2-mod-php7.3 package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: libapache2-mod-php7.3 E: Sub-process /usr/bin/dpkg returned an error code (1) That is a problem. Now what? Can you send me (directly) the files from that system named '/var/lib/dpkg/info/libapache2-mod-php7.3*'? Apparently not: : host mailly.debian.org[82.195.75.114] said: 550 HELO mismatch Forged HELO for (shell.localdomain) (in reply to RCPT TO command) archive attached -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England | libapache.tar.bz2 Description: Binary data
Re: Apache2/PHP7 fails in Buster
On 16/01/2020 15:03, Roberto C. Sánchez wrote: On Thu, Jan 16, 2020 at 02:59:15PM +, Tony van der Hoff wrote: On 16/01/2020 14:52, Roberto C. Sánchez wrote: On Thu, Jan 16, 2020 at 02:39:21PM +, Tony van der Hoff wrote: On 16/01/2020 14:35, Roberto C. Sánchez wrote: On Thu, Jan 16, 2020 at 02:27:16PM +, Tony van der Hoff wrote: Hi, I have a up to date Buster system as a fresh install (not upgrade). My PHP scripts, which used to work fine under Stretch, are now failing - the browser just shows the script source. a2enmod php7.3 shows ERROR: Module php7.3 does not exist! apt-get install libapache2-mod-php7.3 shows libapache2-mod-php7.3 is already the newest version (7.3.11-1~deb10u1) OK, so what is going wrong, please? What is the output of `ls -l /etc/apache2/mods-*'? [SNIP] That looks like the contents of /etc/apache2/mods-enabled. Do you have a directory /etc/apache2/mods-available? You must, or your Apache installation would be completely broken. Can you look in /etc/apache2/mods-available to see if there is a PHP module listed there as available? Yes, you're right. I missed half the output, sorry. But there is no PHP module there, which is why I tried apt-get install libapache2-mod-php7.3. [SNIP] Well, you are definitely missing the module file. It should be in that package: apt-file search php7.3.load libapache2-mod-php7.3: /etc/apache2/mods-available/php7.3.load I recommend this: sudo apt-get install --reinstall libapache2-mod-php7.3 After that recheck the contents of /etc/apache2/mods-available to see if the file is there. dpkg: error processing package libapache2-mod-php7.3 (--configure): installed libapache2-mod-php7.3 package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: libapache2-mod-php7.3 E: Sub-process /usr/bin/dpkg returned an error code (1) Now what? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Apache2/PHP7 fails in Buster
On 16/01/2020 14:52, Roberto C. Sánchez wrote: On Thu, Jan 16, 2020 at 02:39:21PM +, Tony van der Hoff wrote: On 16/01/2020 14:35, Roberto C. Sánchez wrote: On Thu, Jan 16, 2020 at 02:27:16PM +, Tony van der Hoff wrote: Hi, I have a up to date Buster system as a fresh install (not upgrade). My PHP scripts, which used to work fine under Stretch, are now failing - the browser just shows the script source. a2enmod php7.3 shows ERROR: Module php7.3 does not exist! apt-get install libapache2-mod-php7.3 shows libapache2-mod-php7.3 is already the newest version (7.3.11-1~deb10u1) OK, so what is going wrong, please? What is the output of `ls -l /etc/apache2/mods-*'? [SNIP] That looks like the contents of /etc/apache2/mods-enabled. Do you have a directory /etc/apache2/mods-available? You must, or your Apache installation would be completely broken. Can you look in /etc/apache2/mods-available to see if there is a PHP module listed there as available? Yes, you're right. I missed half the output, sorry. But there is no PHP module there, which is why I tried apt-get install libapache2-mod-php7.3. /etc/apache2/mods-available: total 564 -rw-r--r-- 1 root root 100 Apr 2 2019 access_compat.load -rw-r--r-- 1 root root 377 Apr 2 2019 actions.conf -rw-r--r-- 1 root root 66 Apr 2 2019 actions.load -rw-r--r-- 1 root root 843 Apr 2 2019 alias.conf -rw-r--r-- 1 root root 62 Apr 2 2019 alias.load -rw-r--r-- 1 root root 76 Apr 2 2019 allowmethods.load -rw-r--r-- 1 root root 76 Apr 2 2019 asis.load -rw-r--r-- 1 root root 94 Apr 2 2019 auth_basic.load -rw-r--r-- 1 root root 96 Apr 2 2019 auth_digest.load -rw-r--r-- 1 root root 100 Apr 2 2019 auth_form.load -rw-r--r-- 1 root root 72 Apr 2 2019 authn_anon.load -rw-r--r-- 1 root root 72 Apr 2 2019 authn_core.load -rw-r--r-- 1 root root 85 Apr 2 2019 authn_dbd.load -rw-r--r-- 1 root root 70 Apr 2 2019 authn_dbm.load -rw-r--r-- 1 root root 72 Apr 2 2019 authn_file.load -rw-r--r-- 1 root root 78 Apr 2 2019 authn_socache.load -rw-r--r-- 1 root root 74 Apr 2 2019 authnz_fcgi.load -rw-r--r-- 1 root root 90 Apr 2 2019 authnz_ldap.load -rw-r--r-- 1 root root 72 Apr 2 2019 authz_core.load -rw-r--r-- 1 root root 96 Apr 2 2019 authz_dbd.load -rw-r--r-- 1 root root 92 Apr 2 2019 authz_dbm.load -rw-r--r-- 1 root root 104 Apr 2 2019 authz_groupfile.load -rw-r--r-- 1 root root 94 Apr 2 2019 authz_host.load -rw-r--r-- 1 root root 74 Apr 2 2019 authz_owner.load -rw-r--r-- 1 root root 94 Apr 2 2019 authz_user.load -rw-r--r-- 1 root root 3374 Apr 2 2019 autoindex.conf -rw-r--r-- 1 root root 70 Apr 2 2019 autoindex.load -rw-r--r-- 1 root root 64 Oct 13 21:21 brotli.load -rw-r--r-- 1 root root 64 Apr 2 2019 buffer.load -rw-r--r-- 1 root root 889 Apr 2 2019 cache_disk.conf -rw-r--r-- 1 root root 89 Apr 2 2019 cache_disk.load -rw-r--r-- 1 root root 62 Apr 2 2019 cache.load -rw-r--r-- 1 root root 95 Apr 2 2019 cache_socache.load -rw-r--r-- 1 root root 70 Apr 2 2019 cern_meta.load -rw-r--r-- 1 root root 115 Apr 2 2019 cgid.conf -rw-r--r-- 1 root root 60 Apr 2 2019 cgid.load -rw-r--r-- 1 root root 58 Apr 2 2019 cgi.load -rw-r--r-- 1 root root 76 Apr 2 2019 charset_lite.load -rw-r--r-- 1 root root 60 Apr 2 2019 data.load -rw-r--r-- 1 root root 83 Apr 2 2019 dav_fs.conf -rw-r--r-- 1 root root 79 Apr 2 2019 dav_fs.load -rw-r--r-- 1 root root 58 Apr 2 2019 dav.load -rw-r--r-- 1 root root 68 Apr 2 2019 dav_lock.load -rw-r--r-- 1 root root 58 Apr 2 2019 dbd.load -rw-r--r-- 1 root root 395 Oct 13 21:21 deflate.conf -rw-r--r-- 1 root root 84 Apr 2 2019 deflate.load -rw-r--r-- 1 root root 64 Apr 2 2019 dialup.load -rw-r--r-- 1 root root 157 Apr 2 2019 dir.conf -rw-r--r-- 1 root root 58 Apr 2 2019 dir.load -rw-r--r-- 1 root root 64 Apr 2 2019 dump_io.load -rw-r--r-- 1 root root 60 Apr 2 2019 echo.load -rw-r--r-- 1 root root 58 Apr 2 2019 env.load -rw-r--r-- 1 root root 66 Apr 2 2019 expires.load -rw-r--r-- 1 root root 72 Apr 2 2019 ext_filter.load -rw-r--r-- 1 root root 89 Apr 2 2019 file_cache.load -rw-r--r-- 1 root root 64 Apr 2 2019 filter.load -rw-r--r-- 1 root root 66 Apr 2 2019 headers.load -rw-r--r-- 1 root root 176 Apr 2 2019 heartbeat.load -rw-r--r-- 1 root root 182 Apr 2 2019 heartmonitor.load -rw-r--r-- 1 root root 1240 Oct 13 21:21 http2.conf -rw-r--r-- 1 root root 62 Apr 2 2019 http2.load -rw-r--r-- 1 root root 62 Apr 2 2019 ident.load -rw-r--r-- 1 root root 68 Apr 2 2019 imagemap.load -rw-r--r-- 1 root root 82 Apr 2 2019 include.load -rw-r--r-- 1 root root 402 Apr 2 2019 info.conf -rw-r--r-- 1 root root 60 Apr 2 2019 info.load -rw-r--r-- 1 root root 116 Apr 2 2019 lbmethod_bybusyness.load -rw-r--r-- 1 root root 116 Apr 2 2019 lbmethod_byrequests.load -rw-r--r-- 1 root root 114 Apr 2 2019 lbmethod_bytraffic.load -rw-r--r-- 1
Re: Apache2/PHP7 fails in Buster
On 16/01/2020 14:35, Roberto C. Sánchez wrote: On Thu, Jan 16, 2020 at 02:27:16PM +, Tony van der Hoff wrote: Hi, I have a up to date Buster system as a fresh install (not upgrade). My PHP scripts, which used to work fine under Stretch, are now failing - the browser just shows the script source. a2enmod php7.3 shows ERROR: Module php7.3 does not exist! apt-get install libapache2-mod-php7.3 shows libapache2-mod-php7.3 is already the newest version (7.3.11-1~deb10u1) OK, so what is going wrong, please? What is the output of `ls -l /etc/apache2/mods-*'? lrwxrwxrwx 1 root root 36 Oct 29 11:58 access_compat.load -> ../mods-available/access_compat.load lrwxrwxrwx 1 root root 28 Oct 29 11:58 alias.conf -> ../mods-available/alias.conf lrwxrwxrwx 1 root root 28 Oct 29 11:58 alias.load -> ../mods-available/alias.load lrwxrwxrwx 1 root root 33 Oct 29 11:58 auth_basic.load -> ../mods-available/auth_basic.load lrwxrwxrwx 1 root root 33 Oct 29 11:58 authn_core.load -> ../mods-available/authn_core.load lrwxrwxrwx 1 root root 33 Oct 29 11:58 authn_file.load -> ../mods-available/authn_file.load lrwxrwxrwx 1 root root 33 Oct 29 11:58 authz_core.load -> ../mods-available/authz_core.load lrwxrwxrwx 1 root root 38 Nov 4 10:12 authz_groupfile.load -> ../mods-available/authz_groupfile.load lrwxrwxrwx 1 root root 33 Oct 29 11:58 authz_host.load -> ../mods-available/authz_host.load lrwxrwxrwx 1 root root 33 Oct 29 11:58 authz_user.load -> ../mods-available/authz_user.load lrwxrwxrwx 1 root root 32 Oct 29 11:58 autoindex.conf -> ../mods-available/autoindex.conf lrwxrwxrwx 1 root root 32 Oct 29 11:58 autoindex.load -> ../mods-available/autoindex.load lrwxrwxrwx 1 root root 27 Nov 4 15:03 cgid.conf -> ../mods-available/cgid.conf lrwxrwxrwx 1 root root 27 Nov 4 15:03 cgid.load -> ../mods-available/cgid.load lrwxrwxrwx 1 root root 26 Nov 4 15:05 cgi.load -> ../mods-available/cgi.load lrwxrwxrwx 1 root root 30 Oct 29 11:58 deflate.conf -> ../mods-available/deflate.conf lrwxrwxrwx 1 root root 30 Oct 29 11:58 deflate.load -> ../mods-available/deflate.load lrwxrwxrwx 1 root root 26 Oct 29 11:58 dir.conf -> ../mods-available/dir.conf lrwxrwxrwx 1 root root 26 Oct 29 11:58 dir.load -> ../mods-available/dir.load lrwxrwxrwx 1 root root 26 Oct 29 11:58 env.load -> ../mods-available/env.load lrwxrwxrwx 1 root root 29 Oct 29 11:58 filter.load -> ../mods-available/filter.load lrwxrwxrwx 1 root root 30 Nov 3 10:33 include.load -> ../mods-available/include.load lrwxrwxrwx 1 root root 27 Oct 29 11:58 mime.conf -> ../mods-available/mime.conf lrwxrwxrwx 1 root root 27 Oct 29 11:58 mime.load -> ../mods-available/mime.load lrwxrwxrwx 1 root root 34 Nov 4 15:05 mpm_prefork.conf -> ../mods-available/mpm_prefork.conf lrwxrwxrwx 1 root root 34 Nov 4 15:05 mpm_prefork.load -> ../mods-available/mpm_prefork.load lrwxrwxrwx 1 root root 34 Oct 29 11:58 negotiation.conf -> ../mods-available/negotiation.conf lrwxrwxrwx 1 root root 34 Oct 29 11:58 negotiation.load -> ../mods-available/negotiation.load lrwxrwxrwx 1 root root 28 Jan 16 14:02 proxy.conf -> ../mods-available/proxy.conf lrwxrwxrwx 1 root root 33 Jan 16 14:02 proxy_fcgi.load -> ../mods-available/proxy_fcgi.load lrwxrwxrwx 1 root root 28 Jan 16 14:02 proxy.load -> ../mods-available/proxy.load lrwxrwxrwx 1 root root 33 Oct 29 11:58 reqtimeout.conf -> ../mods-available/reqtimeout.conf lrwxrwxrwx 1 root root 33 Oct 29 11:58 reqtimeout.load -> ../mods-available/reqtimeout.load lrwxrwxrwx 1 root root 31 Oct 29 11:58 setenvif.conf -> ../mods-available/setenvif.conf lrwxrwxrwx 1 root root 31 Oct 29 11:58 setenvif.load -> ../mods-available/setenvif.load lrwxrwxrwx 1 root root 29 Oct 29 11:58 status.conf -> ../mods-available/status.conf lrwxrwxrwx 1 root root 29 Oct 29 11:58 status.load -> ../mods-available/status.load lrwxrwxrwx 1 root root 30 Nov 4 10:07 userdir.conf -> ../mods-available/userdir.conf lrwxrwxrwx 1 root root 30 Nov 4 10:07 userdir.load -> ../mods-available/userdir.load -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Apache2/PHP7 fails in Buster
Hi, I have a up to date Buster system as a fresh install (not upgrade). My PHP scripts, which used to work fine under Stretch, are now failing - the browser just shows the script source. a2enmod php7.3 shows ERROR: Module php7.3 does not exist! apt-get install libapache2-mod-php7.3 shows libapache2-mod-php7.3 is already the newest version (7.3.11-1~deb10u1) OK, so what is going wrong, please? Thanks -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: failed upgrade to Buster
On 28/10/2019 09:47, Jonas Smedegaard wrote: Hi Tony, Quoting Tony van der Hoff (2019-10-28 10:17:13) I've just attempted to upgrade from Jessie to buster. All went well until the dist-upgrade stage, when it ran out of space in my /usr partition. which has 14G allocated. 1.4G of this appears to be the doc/ folder, which seems excessive. It has, for instance all the language files, whereas I only require en-GB. Can anyone please advise on how to get rid of this chaff? You might like the package localepurge Please read the warning in the package description carefully, though. Thanks for your swift reply, Jonas. I didn't try your suggestion, because in the meantime I decided that after many upgrades, the system was in such a messy state, that it would benefit from a full reload. So, I set about installing it from the latest netinst .iso image, which went quite smoothly. Sadly, on reboot, I get the error: file /grub/i386-pc/normal.mod not found. Entering rescue mode... Now what to do? Cheers, Tony
failed upgrade to Buster
Hi all, I've just attempted to upgrade from Jessie to buster. All went well until the dist-upgrade stage, when it ran out of space in my /usr partition. which has 14G allocated. 1.4G of this appears to be the doc/ folder, which seems excessive. It has, for instance all the language files, whereas I only require en-GB. Can anyone please advise on how to get rid of this chaff? Cheers, Tony
Re: New Linux User needs some guidance
On 07/10/2019 19:04, Thomas Schmitt wrote: > Hi, > > lwhona...@gmail.com wrote: >> I was under the impression, if I copied the dvd image to a usb stick, >> I could boot from the stick and start the install. > > This is true. You have to put it as image onto the raw USB stick device. > > https://www.debian.org/CD/faq/#write-usb > proposes for GNU/Linux something like > cp debian-10.0.0-amd64-netinst.iso /dev/sdd > where /dev/sdd is the device file representing the USB stick. I've been following this thread with interest, as right from the start it talks about "copying" the .iso image to the ssd. At risk of displaying some ignorance, and attracting flames, I think this is misleading and take issue with the FAQ. cp copies a file onto s file system, bit that's not what's wanted here. To create a bootable image from a .iso, you need 'dd', i.e. sudo dd bs=4M \ if=/path-todebian-10.iso\ of=/dev/sdx\ oflag=sync Make sure you identify the correct usb stick for sdx, or you may end up overwriting something important. This is explained in detail at https://linuxize.com/post/create-bootable-debian-10-usb-stick-on-linux/ It worked for me. Good luck, Tony -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Debian Installer, Manual Partitioning is a Joke
On 29/09/2019 21:32, Liam O'Toole wrote: > On Sun, 29 Sep, 2019 at 10:56:54 -0400, Wayne Sallee wrote: >> Debian really needs to work on the manual partitioning part of the >> installation. >> >> It's absolutely pathetic. >> >> Wayne Sallee >> wa...@waynesallee.com >> http://www.WayneSallee.com >> > > Thank you for your contribution. I look forward to reading your > proposals for improving Debian, and how you intend to contribute. > Don't feed the trolls. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: upgrade fails
On 24/09/2019 12:35, The Wanderer wrote: > On 2019-09-24 at 07:11, Tony van der Hoff wrote: > >> tony@tony-lx:~$ sudo apt-get upgrade >> [sudo] password for tony: >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Calculating upgrade... Done >> The following packages have been kept back: >> linux-image-amd64 >> 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. >> >> Can anyone tell me why, please? > > Not for certain without more information. > > The most likely answer is that to upgrade that package, apt-get would > have to install one or more new packages that you don't already have > installed; 'apt-get update' will never install or remove packages, only > upgrade existing ones. > > If you want to let it install new packages or remove installed packages > in order to complete the upgrade, run 'apt-get dist-upgrade' instead. > > Or you might try using 'apt upgrade' or similar; I don't use the 'apt' > command myself, so I'm not familiar with exactly how things work on that > side of the fence, but I understand that the behavior is different and > it may match more closely to what you're expecting. > Thanks, Wanderer, dist-upgrade worked fine. Embarrassed to admit I forgot all about that command. Must be having senior moments :( -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
upgrade fails
tony@tony-lx:~$ sudo apt-get upgrade [sudo] password for tony: Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: linux-image-amd64 0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded. Can anyone tell me why, please? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: About /dev/sr impatience with automatic tray loading
On 11/12/18 17:31, Greg Wooledge wrote: > On Tue, Dec 11, 2018 at 06:22:56PM +0100, Thomas Schmitt wrote: >> Dan Ritter wrote: >>> The English use it more than Americans do. >> >> In school it was a big deal to distinguish "will" and "shall". >> (I was very eager to forget the exact rules when nobody cared any more.) > > Americans (at least in my part of the country) never use "shall" at > all. To us, it simply sounds archaic. We'd expect it in the King James > Bible, or in certain kinds of fantasy literature. > Not the bible, but pretty close: https://www.ietf.org/rfc/rfc2119.txt -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
strange DHCP behaviour
Hi, I havea laptop running fully up to date Stretch with NetworkManager,
set to use DH|Cp via wireless.
The DHCP server is another Stretch system, with the stanzas
host tony-lt {
hardware ethernet 0c:60:76:6c:e6:6f;
fixed-address 192.168.1.199;
}
subnet 192.168.1.0 netmask 255.255.255.0
{
range 192.168.1.200 192.168.1.254;
option routers 192.168.1.10;
}
That MAC is correct for the laptop.
I an expecting to see 192.168.1.199 as the laptop address, but no, if a
gives:
wlan0: mtu 1500 qdisc mq state UP
group default qlen 1000
link/ether 0c:60:76:6c:e6:6f brd ff:ff:ff:ff:ff:ff
inet 192.168.1.253/24 brd 192.168.1.255 scope global dynamic wlan0
valid_lft 479sec preferred_lft 479sec
Finally, the server shows:
Oct 23 14:23:38 routerpi dhcpd[1068]: DHCPREQUEST for 192.168.1.253 from
0c:60:76:6c:e6:6f (tony-lt) via eth0
Oct 23 14:23:38 routerpi dhcpd[1068]: DHCPACK on 192.168.1.253 to
0c:60:76:6c:e6:6f (tony-lt) via eth0
Oct 23 14:23:53 routerpi dhcpd[1068]: reuse_lease: lease age 15 (secs)
under 25% threshold, reply with unaltered, existing lease for 192.168.1.253
Oct 23 14:23:53 routerpi dhcpd[1068]: DHCPREQUEST for 192.168.1.253 from
0c:60:76:6c:e6:6f (tony-lt) via eth0
Oct 23 14:23:53 routerpi dhcpd[1068]: DHCPACK on 192.168.1.253 to
0c:60:76:6c:e6:6f (tony-lt) via eth0
So, my question: why is the server handing out .253, when it is
configured to provide .199?
What is this 'reuse-lease' all about?
I've tried 'dhclient -r wlan 0; dhclient -v wlan0' on the laptop, to no
avail.
Any suggestions, please?
--
Tony van der Hoff | mailto:t...@vanderhoff.org
Ariège, France |
Re: Wanted - Debian(preferred)/Linux handheld
On 20/08/18 16:16, Glenn English wrote: > On Sun, Aug 19, 2018 at 1:35 PM Eric S Fraga wrote: >> On Thursday, 16 Aug 2018 at 14:28, Glenn English wrote: >>> It's all over Amazon (search: planet gemini pda computer), but, as >>> best I can tell, there's no computer. >> I'm not sure I understand what you mean by "there's no computer." The >> Gemini is not vapourware. It exists. > When I looked the other day, there were lots of books and such, but no > hardware. Gemini was there, but their computer wasn't. > Try Here: https://www.amazon.co.uk/Gemini-4G-WiFi-Space-Grey/dp/B07DNG5YMG/ref=sr_1_1?ie=UTF8=1534779869=8-1=gemini+pda -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Packagekit spamming syslog
On 02/05/18 17:52, Kenneth Parker wrote: > You might want to bring this up, on the Packagekit email list: > > http://lists.freedesktop.org/mailman/listinfo/packagekit > > (Note: I am not a Packagekit expert. I got this from the Debian Wiki > Page on Packagekit). > > Kenneth Parker > > On Wed, May 2, 2018, 11:30 AM Tony van der Hoff <li...@vanderhoff.org > <mailto:li...@vanderhoff.org>> wrote: > > Running fully up to date stretch, I'm seeing the following in my > syslog > every 5 minutes: > > May 2 15:55:25 tony-lx PackageKit: refresh-cache transaction > /144833_aadbeecc from uid 1000 finished with success after 2225ms > May 2 15:55:27 tony-lx PackageKit: get-updates transaction > /144834_dacaaceb from uid 1000 finished with success after 1502ms > May 2 15:55:27 tony-lx PackageKit: get-updates transaction > /144835_cdcacaca from uid 1000 finished with success after 452ms > May 2 15:55:28 tony-lx PackageKit: get-updates transaction > /144837_aabccdcd from uid 1000 finished with success after 496ms > May 2 15:55:29 tony-lx PackageKit: get-updates transaction > /144838_bddedcad from uid 1000 finished with success after 451ms > > Can someone please explain why PackageKit needs to update so > often, and > maybe how to tame it. > > Thanks, > Tony > > -- > Tony van der Hoff | mailto:t...@vanderhoff.org > <mailto:t...@vanderhoff.org> > Buckinghamshire, England | > Thanks for replying, Kenneth. Whilst not solved, I think I'm out of the woods. See my reply to Curt for the details. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Packagekit spamming syslog
On 02/05/18 17:19, Curt wrote: > On 2018-05-02, Tony van der Hoff <li...@vanderhoff.org> wrote: >> Running fully up to date stretch, I'm seeing the following in my syslog >> every 5 minutes: >> >> May 2 15:55:25 tony-lx PackageKit: refresh-cache transaction >> /144833_aadbeecc from uid 1000 finished with success after 2225ms >> May 2 15:55:27 tony-lx PackageKit: get-updates transaction >> /144834_dacaaceb from uid 1000 finished with success after 1502ms >> May 2 15:55:27 tony-lx PackageKit: get-updates transaction >> /144835_cdcacaca from uid 1000 finished with success after 452ms >> May 2 15:55:28 tony-lx PackageKit: get-updates transaction >> /144837_aabccdcd from uid 1000 finished with success after 496ms >> May 2 15:55:29 tony-lx PackageKit: get-updates transaction >> /144838_bddedcad from uid 1000 finished with success after 451ms >> >> Can someone please explain why PackageKit needs to update so often, and >> maybe how to tame it. > There's a bug report looks relevant: > > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=881787 > > Jason Rodrigues in that thread suspects the KDE update notifier (he > removed 'apper', finding no other palliative measure). > > Of course if you're not running KDE (or apper) it must be--implacable > logic--something else. Thanks for your reply, Curt.I saw that bug report, and uninstalled Apper, but no difference, so I re-installed it. I am indeed running KDE, but see no option to control this behaviour. I have to add that I initially became aware of this because my syslog had grown to 26GiB, and I unfairly blamed it on these messages. I then reconfigured logrotate, and the syslog is now kept to a more reasonable size, so the problem is no longer significant.. Thanks again for your interest. Tony
Packagekit spamming syslog
Running fully up to date stretch, I'm seeing the following in my syslog every 5 minutes: May 2 15:55:25 tony-lx PackageKit: refresh-cache transaction /144833_aadbeecc from uid 1000 finished with success after 2225ms May 2 15:55:27 tony-lx PackageKit: get-updates transaction /144834_dacaaceb from uid 1000 finished with success after 1502ms May 2 15:55:27 tony-lx PackageKit: get-updates transaction /144835_cdcacaca from uid 1000 finished with success after 452ms May 2 15:55:28 tony-lx PackageKit: get-updates transaction /144837_aabccdcd from uid 1000 finished with success after 496ms May 2 15:55:29 tony-lx PackageKit: get-updates transaction /144838_bddedcad from uid 1000 finished with success after 451ms Can someone please explain why PackageKit needs to update so often, and maybe how to tame it. Thanks, Tony -- Tony van der Hoff | mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: More then 2800 spams from the list...
On 19/03/18 17:38, Miles Fidelman wrote: > > Comments at end. > Where they should be. If you can avoid the HTML, and change your sig.sep to , you're on your way to becoming a hero on this list.
Re: unison compatibility in stretch
On 13/12/17 17:49, Tony van der Hoff wrote: > On 13/12/17 17:29, Anders Andersson wrote: >> On Wed, Dec 13, 2017 at 5:44 PM, Tony van der Hoff <li...@vanderhoff.org> >> wrote: >>> On 13/12/17 15:40, Curt wrote: >>>> Sorry for butting in once again, but you do have unison-all installed, >>>> the metapackage which allows specifically for the -addversionno "kludge" by >>>> bringing in versions 2.32 and 2.40 as per the following post curiously >>>> similar to your case (two machines, one with Debian Jessie and one with >>>> Debian Stretch) >>>> >>>> https://unix.stackexchange.com/questions/233504/how-to-use-multiple-versions-of-unison-on-one-system >>>> >>>> and then working around the eventual minor version number truncation >>>> bug, if indeed it still exists, as per my previous cryptic message. >>>> >>> I'm fed up with trying bodgy work-arounds, which really should not be >>> required. I have now spent so much time on this issue that I've become >>> thoroughly disenchanted with Unison (which is great when it works) that >>> I'm taking my custom elsewhere. >> Do you have a good alternative? I'm fed up with Unison since a long >> time, because of such an important tool not handling different >> versions, and the impracticality of writing it in yet another >> experimental language requiring its own complete little world to build >> and run. >> > As mentioned upthread, "Syncthing" [https://docs.syncthing.net] seems to > do much the same as Unison, hopefully more sensibly. I'm going to give > it a try over the next few days, and I'll report back here. > Well, "the next few days" turned out to be a drawn-out frustrating struggle, with no benefit. Syncthing appears to be an extremely powerful file synchronization tool, with an emphasis on security, which in theory would make it an excellent replacement for unison. However, after many days struggling wit its configuration through two firewalls and a NAT router, trying to synchronize 3 systems, with more to add, I've given up. The machines appear to connect, and some meta-data is transferred, but no data transfers take place. I've decided to give up on Syncthing, and revert to Unison, which means upgrading my server, but hey, what are holidays for? Cheers, Tony
Re: system boots to terminal -Solved
On 28/12/17 15:05, Felix Miata wrote: > Tony van der Hoff composed on 2017-12-28 14:39 (UTC): > >> I should have said I'm using KDE, so I guess gdm stanzas are inappropriate. >> Anyway, I'm seeing: >> $ cat /etc/X11/default-display-manager >> /usr/bin/sddm >> Should I dpkg-reconfigure that? > If that doesn't get the job done, don't be surprised. Cross-distro, sddm is > anything but the most reliable of DMs. For any who want restoration of all DM > features lost with KDM's demise, Trinity Desktop offers TDM. Otherwise, give > lightdm a try. TDM is the only DM I use on Stretch. Thanks, all for the useful tips. Indeed, dpkg-reconfigure had the desired effect Cheers, Tony
Re: system boots to terminal
On 28/12/17 10:59, Floris wrote: > Op Thu, 28 Dec 2017 11:41:22 +0100 schreef Tony van der Hoff > <li...@vanderhoff.org>: > >> Hi, >> >> Since upgrading Jessie to Stretch, I find my system boots to a terminal, >> instead of a desktop. I can log in, run startx, and the desktop then >> appears. I then need to log in again. >> >> So, how do I get my system to boot straight to the desktop? >> >> Cheers, Tony >> > Thanks for your swift reply, Floris; much appreciated. > Things you could try: > > - Is systemd set to boot into graphical mode? > $ systemctl get-default > graphical.target > > If you get an other output run: > # systemctl set-default graphical.target > > Yes, I'm seeing that response. > - Reconfigure gdm3 and make sure gdm is the default display manager > # dpkg-reconfigure gdm3 > $ cat /etc/X11/default-display-manager > /usr/sbin/gdm3 > I should have said I'm using KDE, so I guess gdm stanzas are inappropriate. Anyway, I'm seeing: $ cat /etc/X11/default-display-manager /usr/bin/sddm Should I dpkg-reconfigure that? Cheers, Tony
system boots to terminal
Hi, Since upgrading Jessie to Stretch, I find my system boots to a terminal, instead of a desktop. I can log in, run startx, and the desktop then appears. I then need to log in again. So, how do I get my system to boot straight to the desktop? Cheers, Tony
Re: unison compatibility in stretch
On 13/12/17 17:29, Anders Andersson wrote: > On Wed, Dec 13, 2017 at 5:44 PM, Tony van der Hoff <li...@vanderhoff.org> > wrote: >> On 13/12/17 15:40, Curt wrote: >>> Sorry for butting in once again, but you do have unison-all installed, >>> the metapackage which allows specifically for the -addversionno "kludge" by >>> bringing in versions 2.32 and 2.40 as per the following post curiously >>> similar to your case (two machines, one with Debian Jessie and one with >>> Debian Stretch) >>> >>> https://unix.stackexchange.com/questions/233504/how-to-use-multiple-versions-of-unison-on-one-system >>> >>> and then working around the eventual minor version number truncation >>> bug, if indeed it still exists, as per my previous cryptic message. >>> >> I'm fed up with trying bodgy work-arounds, which really should not be >> required. I have now spent so much time on this issue that I've become >> thoroughly disenchanted with Unison (which is great when it works) that >> I'm taking my custom elsewhere. > Do you have a good alternative? I'm fed up with Unison since a long > time, because of such an important tool not handling different > versions, and the impracticality of writing it in yet another > experimental language requiring its own complete little world to build > and run. > As mentioned upthread, "Syncthing" [https://docs.syncthing.net] seems to do much the same as Unison, hopefully more sensibly. I'm going to give it a try over the next few days, and I'll report back here.
Re: unison compatibility in stretch
On 13/12/17 15:40, Curt wrote: > On 2017-12-13, Tony van der Hoff <li...@vanderhoff.org> wrote: >> It seems the unison developers are a little careless with compatibility >> issues. This situation has arisen previously, then overcome by unison-all. >> >> Thanks for your suggestion of syncthing; I'll give that a go... > Sorry for butting in once again, but you do have unison-all installed, > the metapackage which allows specifically for the -addversionno "kludge" by > bringing in versions 2.32 and 2.40 as per the following post curiously > similar to your case (two machines, one with Debian Jessie and one with > Debian Stretch) > > https://unix.stackexchange.com/questions/233504/how-to-use-multiple-versions-of-unison-on-one-system > > and then working around the eventual minor version number truncation > bug, if indeed it still exists, as per my previous cryptic message. > Yes, thanks Curt. I have unison-all installed, and I've seen that post, and followed the suggestions, without success. Unison-all is simply a meta-package, which depennds on all available unison versions. Since stretch only has 6.40 in its repo, it can only pull that one in. I'm fed up with trying bodgy work-arounds, which really should not be required. I have now spent so much time on this issue that I've become thoroughly disenchanted with Unison (which is great when it works) that I'm taking my custom elsewhere.
Re: unison compatibility in stretch
On 13/12/17 13:35, Eric S Fraga wrote: > On Wednesday, 13 Dec 2017 at 12:49, Tony van der Hoff wrote: > > [...] > > unison is a fantastic tool but these incompatibilities make it > incredibly frustrating to use every now and again. > > You could consider the following options: > > 1. build unison yourself on each system from source. > 2. try other tools such as syncthing. > > Hope you get this sorted! > It seems the unison developers are a little careless with compatibility issues. This situation has arisen previously, then overcome by unison-all. Thanks for your suggestion of syncthing; I'll give that a go... Cheers, Tony
Re: unison compatibility in stretch
On 12/12/17 11:58, Eric S Fraga wrote: > On Monday, 11 Dec 2017 at 10:36, Tony van der Hoff wrote: > > [...] > >> No: >> >> tony@tony-lx:~$ unison -addversionno tony >> Contacting server... >> bash: unison-2.48: command not found > But you do need to install the various versions you may to use on the > server. Then the client can request to use the version that it has by > using that option. > > So install unison-2.48? > The server is running Jessie, the repository does not contain 2.48. There appears to be no backport. The client is running Stretch. Its repository does not contain anything other than 2.48. >From what I can see froom googling, there is an incompatibility in one of the underlying libraries (ocaml?), which prevents Unison 2.48 being built for Jessie, or Unison 2.40 being built for Stretch. There doesn't appear to be an alternative for both jessie and stretch. What a mess!
Re: unison compatibility in stretch
On 12/12/17 08:50, Curt wrote: > On 2017-12-11, Tony van der Hoff <li...@vanderhoff.org> wrote: >> On 10/12/17 19:40, Eric S Fraga wrote: >>> On Sunday, 10 Dec 2017 at 12:25, Tony van der Hoff wrote: >>> >>> [...] >>> >>>> In the passt, I've always worked round this by installing the lower >>>> version on my desktop and adjusted the links. This appears no lnger to >>>> be possible. >>>> >>>> Does anyone know how to get round this? (I've no immediate intention to >>>> upgrade the server). >>> There is the -addversionno option which allows use to use different >>> versions of unison on the server end. Try this out (without adjusting >>> any links). >>> >> No: > What, no? Yes (WVSVNTB). > >> tony@tony-lx:~$ unison -addversionno tony >> Contacting server... >> bash: unison-2.48: command not found >> Fatal error: Lost connection with the server >> >> > * workaroundable via symlink version number truncation bug > Thanks for your reply, Curt, but we appear to speak different languages ;) WVSVNTB? could you please reduce the brevity of your solution? Cheers, Tony
Re: The process for the file protocol died unexpectedly.
On 11/12/17 12:01, Tony van der Hoff wrote: > On 10/12/17 11:48, Tony van der Hoff wrote: >> Hi, >> >> After upgrading Jessie to Stretch, using KDE, I am seeing the error message >> >> "The process for the file protocol died unexpectedly." >> >> when opening Dolphin in su mode. No files are shown. >> >> The same happens when invoking Dolphin from a root text console. >> >> >> This does feature in Google searches, but for dates around 2010, so >> unlikely to be relevant. >> >> >> Has anyone else here encountered this, and maybe found a work-round? >> >> >> Cheers, Tony >> >> > Nobody? Never mind, I rebooted, and it now works.
Re: The process for the file protocol died unexpectedly.
On 10/12/17 11:48, Tony van der Hoff wrote: > Hi, > > After upgrading Jessie to Stretch, using KDE, I am seeing the error message > > "The process for the file protocol died unexpectedly." > > when opening Dolphin in su mode. No files are shown. > > The same happens when invoking Dolphin from a root text console. > > > This does feature in Google searches, but for dates around 2010, so > unlikely to be relevant. > > > Has anyone else here encountered this, and maybe found a work-round? > > > Cheers, Tony > > Nobody?
Missing key
Dragging up an old thread from the archive: On Thu, 22 Jun 2017 12:25:07 -0300 Henrique Holschuh wrote: > On Thu, 22 Jun 2017, Charles E. Blair wrote: > When I type "apt-get > upgrade" I get > this message, and things stop: > > W: There is no > public key available for the following key IDs: > EF0F382A1A7B6500 > > > I hope there is a simple fix. You can ignore the warning _in this > specific instance_: it is expected, and apt is using another key to > verify the downloads. This warning will be fixed for the Debian 8.9 > oldstable point-release (due in about a month or so), which adds the > missing key. I don't understand what oldstable has to do with it, but while upgrading to stretch, I am seeing the identical error message. I'll ignore it, but shouldn't it have been fixed?
Re: unison compatibility in stretch
On 10/12/17 19:40, Eric S Fraga wrote: > On Sunday, 10 Dec 2017 at 12:25, Tony van der Hoff wrote: > > [...] > >> In the passt, I've always worked round this by installing the lower >> version on my desktop and adjusted the links. This appears no lnger to >> be possible. >> >> Does anyone know how to get round this? (I've no immediate intention to >> upgrade the server). > There is the -addversionno option which allows use to use different > versions of unison on the server end. Try this out (without adjusting > any links). > No: tony@tony-lx:~$ unison -addversionno tony Contacting server... bash: unison-2.48: command not found Fatal error: Lost connection with the server
unison compatibility in stretch
Hi, For years I've been using unison to keep common files amongst my various systems. I now find that stretch provides version 2.48, whereas Jessie provided 2.40, and they are not compatible. My server, which still runs Jessie, will therefore not accept connections from my desktop box. In the passt, I've always worked round this by installing the lower version on my desktop and adjusted the links. This appears no lnger to be possible. Does anyone know how to get round this? (I've no immediate intention to upgrade the server).
The process for the file protocol died unexpectedly.
Hi, After upgrading Jessie to Stretch, using KDE, I am seeing the error message "The process for the file protocol died unexpectedly." when opening Dolphin in su mode. No files are shown. The same happens when invoking Dolphin from a root text console. This does feature in Google searches, but for dates around 2010, so unlikely to be relevant. Has anyone else here encountered this, and maybe found a work-round? Cheers, Tony
Strange warning during jessie to stretch upgrade
Hi, W: APT had planned for dpkg to do more than it reported back (0 vs 4) Affected packages: pypy:armhf Google reveals some bug reports (850327 for Debian), but no resolution. Can anyone tell me what it means, and can it be safely ignored?
Re: When did Debian decide to enable PIE by default?
On 09/08/17 15:48, Gene Heskett wrote: > Interesting Thomas, but what the heck is PIE? I know about PAE, but PIE? > Whats it do? Searching the above wiki returned only this thread. > > Thanks, you too. >> Have a nice day :) >> >> Thomas > > Cheers, Gene Heskett Position-independent executable: https://en.wikipedia.org/wiki/Position-independent_code
Re: No mail after reboot
On 26/04/17 11:31, Henning wrote: On Apr 26, 2017, at 3:39 AM, Tony van der Hoff <li...@vanderhoff.org> wrote: Hi, Running Jessie, postfix/courier on my VPS. I don't often need to restart, which is just as well, as after a reboot, I'm unable to access mail over IMAP. It turns out, that if I run service courier-imap-ssl restart and/or service courier-imap restart, mail functionality is restored. Does anyone have any suggestions as to where to look for a fix to this problem, please? Consult your logs. What is the status of courier directly after the restart? -H Thanks, Henning, next time I reboot, I'll certainly check that.
No mail after reboot
Hi, Running Jessie, postfix/courier on my VPS. I don't often need to restart, which is just as well, as after a reboot, I'm unable to access mail over IMAP. It turns out, that if I run service courier-imap-ssl restart and/or service courier-imap restart, mail functionality is restored. Does anyone have any suggestions as to where to look for a fix to this problem, please?
Re: New motherboard, no network
On 14/03/17 15:33, Greg Wooledge wrote:
On Tue, Mar 14, 2017 at 04:12:15PM +0100, Hans wrote:
Hi Tony,
# PCI device 0x10ec:0x8169 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="6c:fd:b9:00:6f:76", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="bc:ae:c5:29:77:d8", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
You have twice the same entry, but one is pointing to eth0 and the second one
is naming the same as eth1. I suppose, one of it is the card from the old pc.
No, they're different. The PCI ID comments are different (one ends
with 8169 and the other with 8168), the MAC addresses are different,
and the eth0/eth1 names are different.
What happens, if you delete the orphaned entry manually?
You can delte it, and rename the last entry to "eth0" (if this is our primary
card). I am sure, you will know, hich MAC is the active one.
I have doubts about that being a good idea.
I'm more concerned with the fact that apparently some command or other
(I don't remember if he told us what commands he ran) only showed eth0
and not eth1.
Original poster, please include the actual shell commands that you
run along with their output. You should be running commands such as:
ifconfig -a
ip addr list
dmesg | grep eth
(Although for dmesg, we may need to see some context around the matching
lines, even just showing the grep output would be a good start.)
OK, thanks all for your help. It set me on the path to fixing the
problem. I ended up deleting all the rules in
udev/rules.d/70-persistent-net.rules, and rebooting. Both interfaces
came up as desired, so I'm back on-line.
(I actually tried systemctlrestart networking.service before I rebooted,
but that had no effect - wierd)
So, thanks again for the input.
--
Tony van der Hoff| mailto:t...@vanderhoff.org
Buckinghamshire, England |
New motherboard, no network
After many years, my faithful ASUS motherboard died, so I've replaced it
with a Gigabyte GA-F2A68HM-HD2. t booted up fine from my existing disk
set into Jessie, but networking is inoperative. The board has an
on-board network interface, plus an extra PCI network board. Neither
seem to be working, although they are recognised by lspci -v:
###
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 0c)
Subsystem: Gigabyte Technology Co., Ltd Motherboard
Flags: bus master, fast devsel, latency 0, IRQ 74
I/O ports at e000 [size=256]
Memory at fea0 (64-bit, non-prefetchable) [size=4K]
Memory at d080 (64-bit, prefetchable) [size=16K]
Capabilities: [40] Power Management version 3
Capabilities: [50] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [70] Express Endpoint, MSI 01
Capabilities: [b0] MSI-X: Enable- Count=4 Masked-
Capabilities: [d0] Vital Product Data
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Virtual Channel
Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
Capabilities: [170] Latency Tolerance Reporting
Kernel driver in use: r8169
02:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8169 PCI
Gigabit Ethernet Controller (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RTL8169/8110 Family
PCI Gigabit Ethernet NIC
Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 20
I/O ports at d000 [size=256]
Memory at fe92 (32-bit, non-prefetchable) [size=256]
Expansion ROM at fe90 [disabled] [size=128K]
Capabilities: [dc] Power Management version 2
Kernel driver in use: r8169
###
ifconfig only lists one board, which appears inactive:
eth0 Link encap:Ethernet HWaddr 6c:fd:b9:00:6f:76
inet addr:192.168.1.7 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
loLink encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:2124 errors:0 dropped:0 overruns:0 frame:0
TX packets:2124 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:208935 (204.0 KiB) TX bytes:208935 (204.0 KiB)
/etc/udev/70-persistent-net.rules presumably contains the addresses for
the old motherboard:
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x10ec:0x8169 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="6c:fd:b9:00:6f:76", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth0"
# PCI device 0x10ec:0x8168 (r8169)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*",
ATTR{address}=="bc:ae:c5:29:77:d8", ATTR{dev_id}=="0x0",
ATTR{type}=="1", KERNEL=="eth*", NAME="eth1"
So, how do I get the network active?
Thanks,
--
Tony van der Hoff | mailto:t...@vanderhoff.org
cyrus-imap-ssl crashing
Hi, On my jessie-powered VPS I'm handling mail with Postfix and cyrus-imap-ssl. From time to time, I find I'm unable to send mail from my Thunderbird MUA due to my credentials being rejected. this may happen multiple times per day, or only once weekly. Restarting the cyrus-imap-ssl daemon on the server always resolves the issue, but, of course, is inconvenient. I can find no log records suggesting what’s happening, but then I don't really know where to look, or what to look for. The mail server has very low traffic, and only 3 users. Can anyone please suggest a way forward to resolve this issue? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Mysql failed
On 16/11/16 16:10, Joe wrote: On 16/11/2016 15:48, Tony van der Hoff wrote: The following packages have unmet dependencies: mysql-server-5.5 : Depends: mysql-client-5.5 (>= 5.5.50-0+deb8u1) but it is not going to be installed PreDepends: mysql-common (>= 5.5.50-0+deb8u1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. but they ARE installed!! Any suggestions as to what to do next, please? My inclination would be to purge all the remaining mysql components (not the workbench) and try reinstalling. They are different versions, presumably as a result of the failed upgrade, and the older ones may be broken in some way that prevented upgrade. If the apt tools refuse to do the job, as they may since there has already been a problem, escalate (carefully) to dpkg. I did once have a problem that even dpkg wouldn't touch and had to resort to manual file deletion, but that will result in an inconsistent package database, and should be avoided if at all possible. Thanks Joe, you fill me with confidence :( I purged the lot using apt, and the client packages disappeared. Sadly, the error persisted. Being of a somewhat cowardly nature, and having never used dpkg for this sort of thing, I abandoned that tack. Instead, I successfully installed MariaDB from the repository, which was my long-term plan in any case, and now have a working database. Thanks again for your suggestions. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Mysql failed
Hi, I've just discovered that MySQL on my jessie desktop box has died unexpectedly. I'm pretty sure it was working 3/4 days ago. tony@tony-lx:~$ mysql -p Enter password: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Sure enough, that socket doesn't exist. sudo service mysql start returns immediately; no errors in any log. It looks like mysql server is no longer installed: root@tony-lx:~# dpkg-query -l 'mysql*' Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version ArchitectureDescription +++-=-===-===-=== un mysql-client (no description available) un mysql-client-5.0 (no description available) un mysql-client-5.1 (no description available) ii mysql-client-5.5 5.5.50-0+deb8u1 amd64 MySQL database client binaries ii mysql-common 5.6.30-1~bpo8+1 all MySQL database common files, e.g. /etc/mysql/my.cnf un mysql-common-5.6 (no description available) un mysql-server (no description available) un mysql-server-5.0 (no description available) un mysql-server-5.1 (no description available) rc mysql-server-5.5 5.5.53-0+deb8u1 amd64 MySQL database server binaries and system database setup un mysql-server-core (no description available) un mysql-server-core-5.5 (no description available) ii mysql-utilities 1.3.5-2 all collection of scripts for managing MySQL servers ii mysql-workbench 6.2.3+dfsg-7 amd64 MySQL Workbench - a visual database modeling, administration and queuing tool ii mysql-workbench-data 6.2.3+dfsg-7 all MySQL Workbench -- architecture independent data I believe there was an update to mysql package, which unattended-upgrades would have tried to install, and maybe it failed. The mysql server is certainly missing. So, try re-installing: root@tony-lx:~# apt-get -f install mysql-server-5.5 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: mysql-server-5.5 : Depends: mysql-client-5.5 (>= 5.5.50-0+deb8u1) but it is not going to be installed PreDepends: mysql-common (>= 5.5.50-0+deb8u1) but it is not going to be installed E: Unable to correct problems, you have held broken packages. but they ARE installed!! Any suggestions as to what to do next, please? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: A_Message_Regarding_Your_DEBT_Situation. vs78
On 16/11/16 11:46, Jude DaShiell wrote: Why the hell are people discussing obvious spam on this list? Take it private, or let it drop! Most of us are not interested. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: apt-get fails to install pylint3
On 14/11/16 16:45, janm wrote: Hi Tony What if you tell APT specifically to use Backports via "-t jessie-backports"? Please see my simulation install below. Thank you, Jan; that seems to have worked. Best regards, Tony -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
apt-get fails to install pylint3
Hi, I'm trying to install pylint3 on my jessie system. According to synaptic, pylint3 is available from backports, which I've enabled in sources.list. However, it depends on python3-astroid, which it refused to install: # tony@tony-lx:~$ sudo apt-get install pylint3 Reading package lists... Done Building dependency tree Reading state information... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pylint3 : Depends: python3-astroid (>= 1.4.1) but 1.2.1-3 is to be installed E: Unable to correct problems, you have held broken packages. # Has anyone got any suggestions? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
[SOLVED] Re: Upgrade fails
On 29/09/16 12:51, Floris wrote: > Op Thu, 29 Sep 2016 12:44:10 +0200 schreef Tony van der Hoff > <t...@vanderhoff.org>: > >> On 29/09/16 12:11, Floris wrote: >>> Op Thu, 29 Sep 2016 12:07:47 +0200 schreef Tony van der Hoff >>> <t...@vanderhoff.org>: >>> >>> >>> re-enable the deb-multimedia repo >>> (don't forget to run apt-get update) >>> and try to update your system with >>> apt-get dselect-upgrade >>> >>> Floris >>> >> >> Yay, that's fixed it! Thanks, Floris! >> >> Do I now comment out multimedia again? >> > > My experience is that deb-multimedia updates their packages as soon as > possible > and fits great in Debian. So you can leave the repo enabled. > > Floris > Thanks Floris, and Vincent, Kushal, Nicholas who also helped. -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Re: Upgrade fails
On 29/09/16 12:11, Floris wrote: > Op Thu, 29 Sep 2016 12:07:47 +0200 schreef Tony van der Hoff > <t...@vanderhoff.org>: > > > re-enable the deb-multimedia repo > (don't forget to run apt-get update) > and try to update your system with > apt-get dselect-upgrade > > Floris > Yay, that's fixed it! Thanks, Floris! Do I now comment out multimedia again? -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Re: Upgrade fails
On 29/09/16 12:03, Floris wrote: > apt-get purge vlc-data No!! I don't want to lose this lot: The following packages will be REMOVED: akregator* apper* ark* browser-plugin-vlc* dolphin* dragonplayer* gwenview* jovie* juk* k3b* k3b-i18n* k4dirstat* kaccessible* kaddressbook* kate* kblocks* kcalc* kde-baseapps* kde-baseapps-bin* kde-plasma-desktop* kde-runtime* kde-standard* kde-style-oxygen* kde-window-manager* kde-workspace* kde-workspace-bin* kdeaccessibility* kdepasswd* kdepim-kresources* kdepim-runtime* kdeplasma-addons* kdesudo* kdevelop* kdewebdev* kdiff3* kdirstat* kdm* kfilereplace* kfind* kgoldrunner* khelpcenter4* kimagemapeditor* kinfocenter* klinkstatus* klipper* kmag* kmahjongg* kmail* kmenuedit* kmix* kmousetool* kmouth* kmplayer* knotes* kommander* konq-plugins* konqueror* konqueror-nsplugins* konsole* kopete* korganizer* kpat* kscreen* kscreensaver* kscreensaver-xsavers* ksnapshot* ksysguard* kuser* kwalletmanager* kwrite* libakonadi-calendar4* libakonadi-contact4* libcalendarsupport4* libeventviews4* libincidenceeditorsng4* libk3b6* libk3b6-extracodecs* libkateinterfaces4* libkcddb4* libkcompactdisc4* libkdepim4* libkdepimdbusinterfaces4* libkonq-common* libkonq5abi1* libkopete4* libksieveui4* libmailcommon4* libmailimporter4* libmarblewidget19* libmessagecomposer4* libmessagecore4* libmessagelist4* libmessageviewer4* libnoteshared4* libokularcore5* libpimcommon4* libreoffice-kde* libsmokekdecore4-3* libsmokekdeui4-3* libsmokekfile3* libsmokekhtml3* libsmokekio3* libsmokeknewstuff2-3* libsmokeknewstuff3-3* libsmokekparts3* libsmokektexteditor3* libsmokekutils3* libsmokeplasma3* libtemplateparser4* libvlc5* libvlccore5* marble-plugins* okteta* okular* phonon* phonon-backend-vlc* plasma-dataengines-workspace* plasma-desktop* plasma-runners-addons* plasma-scriptengine-python* plasma-scriptengine-ruby* plasma-scriptengine-superkaramba* plasma-scriptengines* plasma-wallpapers-addons* plasma-widget-folderview* plasma-widget-lancelot* plasma-widgets-addons* plasma-widgets-workspace* polkit-kde-1* python-kde4* python3-pykde4* qapt-batch* ruby-kde4* ruby-plasma* software-properties-kde* sweeper* systemsettings* task-kde-desktop* vlc* vlc-data* vlc-nox* vlc-plugin-notify* vlc-plugin-pulse* -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Re: Upgrade fails
On 29/09/16 11:48, Floris wrote: > >> >> The following packages have unmet dependencies: >> libvlccore8 : Depends: vlc-data (= 2.2.4-1~deb8u1) but 1:2.0.6-dmo3 is >> to be installed >> >> Bah! >> > > you have enabled the Deb Multimedia repo. Which is not part of Debian. > Now you have two options: > - remove the repo and use the real Debian packages > - wait for a newer version in the multimedia repo > Nope, it's commented out: deb ftp://ftp.uk.debian.org/debian/ jessie main non-free contrib deb-src ftp://ftp.uk.debian.org/debian/ jessie main non-free contrib deb http://security.debian.org/ jessie/updates main non-free contrib #deb-src http://ftp.uk.debian.org/debian/ jessie/updates main non-free contrib # jessie-updates, previously known as 'volatile' deb ftp://ftp.uk.debian.org/debian/ jessie-updates main non-free contrib #deb-src ftp://ftp.uk.debian.org/debian/ jessie-updates main non-free contrib # jessie-backports #deb http://ftp.uk.debian.org/debian/ jessie-backports main non-free contrib # multimedia # deb http://www.deb-multimedia.org jessie main non-free -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Re: Upgrade fails
On 29/09/16 11:21, Vincent Lefevre wrote: > On 2016-09-29 11:13:17 +0200, Tony van der Hoff wrote: >> Trying apt-get upgrade: >> >> 11:10:17 root@tony-fr:~# apt-get upgrade >> Reading package lists... Done >> Building dependency tree >> Reading state information... Done >> Calculating upgrade... Done >> The following packages have been kept back: >> db5.1-util phonon-backend-vlc vlc vlc-nox vlc-plugin-notify >> vlc-plugin-pulse >> 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. >> >> I have no packages (deliberately) held back., so how do I get out of >> this situation? > > Wait for the dependencies to be satisfied? > Might be a long wait: I'm running Jessie! > You can have more information with an explicit install of some > given package, e.g. > > $ apt install db5.1-util -s > > You should get an error message saying why the package cannot be > upgraded. > Hm, db5.1-util installed without a problem. But this: phonon-backend-vlc : Depends: libvlccore8 (>= 2.0.0) but it is not going to be installed vlc : Depends: libvlccore8 (>= 2.2.0) but it is not going to be installed Recommends: vlc-plugin-samba (= 2.2.4-1~deb8u1) but it is not going to be installed vlc-nox : Depends: libvlccore8 (>= 2.2.0) but it is not going to be installed vlc-plugin-notify : Depends: libvlccore8 (>= 2.2.0) but it is not going to be installed vlc-plugin-pulse : Depends: vlc-data (= 2.2.4-1~deb8u1) but 1:2.0.6-dmo3 is to be installed E: Unable to correct problems, you have held broken packages. I tried, without success, to install libvlccore8: The following packages have unmet dependencies: libvlccore8 : Depends: vlc-data (= 2.2.4-1~deb8u1) but 1:2.0.6-dmo3 is to be installed Bah! -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Upgrade fails
Trying apt-get upgrade: 11:10:17 root@tony-fr:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages have been kept back: db5.1-util phonon-backend-vlc vlc vlc-nox vlc-plugin-notify vlc-plugin-pulse 0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded. I have no packages (deliberately) held back., so how do I get out of this situation? -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
[SOLVED] Re: system gobbles disk space
On 26/09/16 11:42, Tony van der Hoff wrote: > Hi, > > For the last few days, my jessie VM has apparently run out of disk space > overnight. df shows 100% usage on / but du does not show any enormous files. > > If I reboot, the disk usage goes back to 50% on a 40GB volume. Pleased to say, that with various people's help, this problem now seems to be solved. Thanks, all! -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Re: system gobbles disk space
On 27/09/16 17:53, Sven Hartge wrote: > Tony van der Hoff <t...@vanderhoff.org> wrote: > >> However, it wouldn't work in this case. Various other applications >> rely on the names of the compressed files being in a particular >> format, which I can't easily achieve with logrotate. So, I'll stick >> with my original script but add "apachectl graceful" before fiddling >> with the files. > > You should add this _after_ fiddling with the files. Reloading apache > before renaming/rotating the log files will not stop them from being > reopened again. > > You rename/rotate the files _first_ and *then* reload apache to have the > intended effect. > > Grüße, > Sven. > Oops, Thanks! -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: system gobbles disk space
On 27/09/16 13:09, to...@tuxteam.de wrote: > On Tue, Sep 27, 2016 at 10:55:52AM +0200, Tony van der Hoff wrote: >> On 26/09/16 17:04, to...@tuxteam.de wrote: >>> On Mon, Sep 26, 2016 at 04:38:01PM +0200, Tony van der Hoff wrote: >>>> On 26/09/16 16:03, to...@tuxteam.de wrote: >>>>> On Mon, Sep 26, 2016 at 12:54:49PM +0200, Erwan David wrote: >>>>> >>>>>> A possibility is that you have processes writing into deleted files. You >>>>>> can see them with lsof +L1 (as root) >>>>> > >> Thanks again to all who have helped with this. > >> After the overnight run, I'm now seeing this: > > [...] > > Bad Apache, bad :-) > > Seems this "cron job" is doing logrotate's job (or I am misunderstanding). > Well, I guess you're correct. It never occurred to me to use logrotate for this purpose. I imagined that was exclusively for the system packages. Evidently not! However, it wouldn't work in this case. Various other applications rely on the names of the compressed files being in a particular format, which I can't easily achieve with logrotate. So, I'll stick with my original script but add "apachectl graceful" before fiddling with the files. The only snag seems to be that the script now has to run as root. Not a terrible deal. >> This setup has existed for a number of years unchanged, so what's caused >> it to start misbehaving? > I still don't understand what's changed; this server is running oldstable, so should only receive security updates. I guess it's just taken a long time to fill up the file space with deleted files. Ho hum! Thanks for your help. -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Re: system gobbles disk space
On 26/09/16 17:04, to...@tuxteam.de wrote: > On Mon, Sep 26, 2016 at 04:38:01PM +0200, Tony van der Hoff wrote: >> On 26/09/16 16:03, to...@tuxteam.de wrote: >>> On Mon, Sep 26, 2016 at 12:54:49PM +0200, Erwan David wrote: >>> >>>> A possibility is that you have processes writing into deleted files. You >>>> can see them with lsof +L1 (as root) >>> Thanks again to all who have helped with this. After the overnight run, I'm now seeing this: root@shell:~# lsof +L1 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINKNODE NAME mysqld 3164mysql4u REG 254,160 0 589839 /tmp/ibvh7MKT (deleted) mysqld 3164mysql5u REG 254,16 473 0 589840 /tmp/ibT7D133 (deleted) mysqld 3164mysql6u REG 254,160 0 589845 /tmp/ibO9pgne (deleted) mysqld 3164mysql7u REG 254,160 0 589851 /tmp/ibOgMl6y (deleted) mysqld 3164mysql 11u REG 254,160 0 589852 /tmp/ibON9JEJ (deleted) /usr/sbin 4643 www-data2w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 4643 www-data 29w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 4643 www-data 30w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 4643 www-data 31w REG 254,160 0 2180306 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/root.log_20160927 (deleted) /usr/sbin 4643 www-data 32w REG 254,160 0 2180396 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/application.log_20160927 (deleted) /usr/sbin 4643 www-data 33w REG 254,160 0 2180397 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/lib.log_20160927 (deleted) /usr/sbin 4643 www-data 34w REG 254,1610374 0 2180686 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/audit.log_20160927 (deleted) /usr/sbin 4643 www-data 35w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 4643 www-data 36w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 4643 www-data 37w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 4643 www-data 38w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13918 www-data2w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13918 www-data 29w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13918 www-data 30w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13918 www-data 35w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13918 www-data 36w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13918 www-data 37w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13918 www-data 38w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13918 www-data 39w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13920 www-data2w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13920 www-data 29w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13920 www-data 30w REG 254,1622055 0 2180962 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/error.log_20160927 (deleted) /usr/sbin 13920 www-data 31w REG 254,160 0 2180306 /home/vanderhoff/webs/www.rutland-sailing.org.uk/htdocs/rutland_members/log/root
Re: system gobbles disk space
On 26/09/16 16:03, to...@tuxteam.de wrote: > On Mon, Sep 26, 2016 at 12:54:49PM +0200, Erwan David wrote: > >> A possibility is that you have processes writing into deleted files. You can >> see them with lsof +L1 (as root) > > Short and sweet. That's even better :-) > That's great; thanks Tomas and Erwan (and others who replied). So, I'm seeing this: root@shell:~# lsof +L1 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME mysqld 3164 mysql4u REG 254,160 0 589839 /tmp/ibvh7MKT (deleted) mysqld 3164 mysql5u REG 254,160 0 589840 /tmp/ibT7D133 (deleted) mysqld 3164 mysql6u REG 254,160 0 589845 /tmp/ibO9pgne (deleted) mysqld 3164 mysql7u REG 254,160 0 589851 /tmp/ibOgMl6y (deleted) mysqld 3164 mysql 11u REG 254,160 0 589852 /tmp/ibON9JEJ (deleted) My interpretation is that mysql has 5 deleted files of 0 size open which are each taking up an inode. ls /tmp is empty. I guess, if there were many (how many?) such entries, the disk would appear full, if it ran out of inodes. Is that correct? -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
system gobbles disk space
Hi, For the last few days, my jessie VM has apparently run out of disk space overnight. df shows 100% usage on / but du does not show any enormous files. If I reboot, the disk usage goes back to 50% on a 40GB volume. How can I determine what is eating the space? -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Re: SOLVED Re: mysql broken after jessie upgrade
On 22/09/16 16:59, Greg Wooledge wrote: > On Thu, Sep 22, 2016 at 04:02:37PM +0200, Tony van der Hoff wrote: >>>>>> Running Jessie here. Performed apt-get upgrade yesterday, which included >>>>>> a new version of mysql. > >> It turns out that the recent upgrade took mysql from 5.5 to 5.6. It >> uninstalled mysql-server-5.5, but failed to install mysql-server-5.6, >> due to an unmet dependency on mysql-server-core-5.6. > > Sounds like you're getting mysql-server from jessie-backports instead > of jessie. On a pure jessie system, it is still 5.5. > Yes, I am. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
SOLVED Re: mysql broken after jessie upgrade
On 22/09/16 13:59, to...@tuxteam.de wrote: > On Thu, Sep 22, 2016 at 01:07:49PM +0200, Tony van der Hoff wrote: >> On 22/09/16 12:56, to...@tuxteam.de wrote: >>> On Thu, Sep 22, 2016 at 12:43:18PM +0200, Tony van der Hoff wrote: >>>> Hi, >>> >>>> Running Jessie here. Performed apt-get upgrade yesterday, which included >>>> a new version of mysql. >>> >>>> I now cannot connect to mysql: >>>> ERROR 2002 (HY000): Can't connect to local MySQL server through socket >>>> '/var/run/mysqld/mysqld.sock' (2) >>> >>>> Any suggestions on how to fix, please? >>> >>> Is the mysql daemon running? Try "service mysqld status" or however >>> that's named in the brave new systemd world (I'm still in the messy >>> old sysv world, mind you ;-) >>> >> Thanks tomas; > > You might check whether there's a process called (more or less) mysql > around: > > ps wwwaux | grep mysql > Ther was... > you might have a look into wherever mysql places its log files (unless > they've been kidnapped by systemd, in which case I'd have to defer to > smarter people; but I don't believe that). Look somewhere in /var/log/mysql. > No all the log files were there, but empty... > Then you might try to invoke (gasp!) "/etc/init.d/mysql start" (as root) > yourself and see whether it spews any error messages giving any clues. > Nothing... > Then you could issue an "netstat -antp" as root, to see whether the > mysql daemon is listening on some other (non-default) port. > No... It turns out that the recent upgrade took mysql from 5.5 to 5.6. It uninstalled mysql-server-5.5, but failed to install mysql-server-5.6, due to an unmet dependency on mysql-server-core-5.6. I manually installed mysql-server-core-5.6, after which mysql-server-5.6 installed fine. Mysql now starts correctly. Thanks for your help, tony >> Ariège, France | > > Wonderful region, btw. I've got warm and sweet memories from summer > 2015... Very warm and sunny right now. The trees are just starting to change colour. -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Re: mysql broken after jessie upgrade
On 22/09/16 12:56, to...@tuxteam.de wrote: > On Thu, Sep 22, 2016 at 12:43:18PM +0200, Tony van der Hoff wrote: >> Hi, > >> Running Jessie here. Performed apt-get upgrade yesterday, which included >> a new version of mysql. > >> I now cannot connect to mysql: >> ERROR 2002 (HY000): Can't connect to local MySQL server through socket >> '/var/run/mysqld/mysqld.sock' (2) > >> Any suggestions on how to fix, please? > > Is the mysql daemon running? Try "service mysqld status" or however > that's named in the brave new systemd world (I'm still in the messy > old sysv world, mind you ;-) > Thanks tomas; No, it's not: 13:03:23 tony@tony-fr:~$ sudo service mysqld status Failed to dump process list, ignoring: Unit mysqld.service not found. ● mysqld.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) But: 13:03:36 tony@tony-fr:~$ sudo service mysql status ● mysql.service - LSB: Start and stop the mysql database server daemon Loaded: loaded (/etc/init.d/mysql; generated; vendor preset: enabled) Active: active (exited) since Thu 2016-09-22 12:32:43 CEST; 32min ago Docs: man:systemd-sysv-generator(8) Process: 21125 ExecStart=/etc/init.d/mysql start (code=exited, status=0/SUCCESS) -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
mysql broken after jessie upgrade
Hi, Running Jessie here. Performed apt-get upgrade yesterday, which included a new version of mysql. I now cannot connect to mysql: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) Any suggestions on how to fix, please? -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Re: postfix mail filtering
On 31/08/16 15:02, Dan Ritter wrote: On Wed, Aug 31, 2016 at 01:21:13PM +0100, Tony van der Hoff wrote: Hi list, I'm running postfix under Wheezy on my VPS, using a more or less out-of-the-box configuration. My users access their mail via IMAP. I subscribe to a number of mail lists, such as this one. I currently use Thunderbird's filtering capability to sort mail into a number of subdirectories within my inbox, which works fine, but requires me to set up all my workstayions (laptop, home, work) with the same filters. I have now acquired an Android smartphone, which has no filtering capability. In any case, keeping a number of workstations in sync is a pain. So, I'd like to perform the filtering on the server (for my user initially, then perhaps for others). My extensive googling reveals that there are many tutorials for filtering spam, but that's not really my problem. I can't find any tutorials on how to set up filters based on, say subject:, from:, or to: fields, but feel certain such must exist. Can any kind person direct me to a suitable tutorial, please? You can use: - sieve, a language for controlling filtering on IMAP servers. Supported by Thunderbird but not very much else. - procmail, a language for filtering on delivery (postfix will call it) -- widely known, but arcane syntax and requires shell access to edit or place the ~/.procmailrc - maildrop, aka mailfilter, a language for filtering on delivery (postfix will call it, too) -- less widely known, but has syntax that is much more readable than procmail. Requires shell access to place a ~/.mailfilter file. All of these have Debian packages. Thanks for the heads-up, Dan. I'll take a look at maildrop. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: postfix mail filtering
On 31/08/16 13:33, Perry E. Metzger wrote: On Wed, 31 Aug 2016 13:21:13 +0100 Tony van der Hoff <t...@vanderhoff.org> wrote: So, I'd like to perform the filtering on the server (for my user initially, then perhaps for others). My extensive googling reveals that there are many tutorials for filtering spam, but that's not really my problem. What you're looking for is an implementation of the Sieve language/system for mail filtering. You don't say what IMAP server you are using, but Dovecot has an implementation of this called "Pigeonhole" that is very likely what you want. Perry Thanks, Perry, I'm actually using Courier, and Google tells me there is no Sieve plugin for it. I shudder at reconfiguring the system for Dovecot! Thanks for giving me another keyword (sieve) to search! -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
postfix mail filtering
Hi list, I'm running postfix under Wheezy on my VPS, using a more or less out-of-the-box configuration. My users access their mail via IMAP. I subscribe to a number of mail lists, such as this one. I currently use Thunderbird's filtering capability to sort mail into a number of subdirectories within my inbox, which works fine, but requires me to set up all my workstayions (laptop, home, work) with the same filters. I have now acquired an Android smartphone, which has no filtering capability. In any case, keeping a number of workstations in sync is a pain. So, I'd like to perform the filtering on the server (for my user initially, then perhaps for others). My extensive googling reveals that there are many tutorials for filtering spam, but that's not really my problem. I can't find any tutorials on how to set up filters based on, say subject:, from:, or to: fields, but feel certain such must exist. Can any kind person direct me to a suitable tutorial, please? Thanks, Tony -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Icedove crashes after recent update
On 04/08/16 09:53, Peter Hillier-Brook wrote: On 04/08/16 08:18, Emile Antonios wrote: Hello, I've noticed that over the last few weeks Icedove is crashing. I've never had a problem with that before. It typically happens when clicking on or deleting an email. I don't get any error, it just closes. I'm running Jessie KDE same as: http://forums.debian.net/viewtopic.php?f=10=128931 Thanks and regards Emile Ditto here, same environment. Yep, I see that too; sometimes it just disappears without my touching it. Same environment. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: No login secreen on Jessie
On 17/04/16 20:00, Markos wrote: Hi Felix, I didn't know about Trinity project. I'll read about it. It made quite a big bang at the time ... -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: restarting network [SOLVED]
On 29/03/16 15:42, Darac Marjal wrote: On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote: On 29/03/16 14:00, Brian wrote: On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote: On 29/03/16 12:58, pedantsunited wrote: On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote: Any chance of seeing /e/n/i? My thanks to everyone who helped resolve this question, especially Reco and Darjac, who set me on the right path to the solution. It turned out that indeed having two default routes was a killer, but having sorted that, restarting the networking service was upsetting openvpn, which somehow consumed 100% of my network capability, and gave every impression of the network being dead. Disabling openvpn sorted that. As I don't normally use openvpn, I can easily start it on occasions when I need it. I'll get back to sorting out what it's doing wrong when I've got more time. Thanks again, chaps! -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: restarting network
On 29/03/16 18:13, Reco wrote: On Tue, 29 Mar 2016 17:38:07 +0100 Tony van der Hoff <t...@vanderhoff.org> wrote: On 29/03/16 17:20, Reco wrote: On Tue, 29 Mar 2016 17:08:01 +0100 Tony van der Hoff <t...@vanderhoff.org> wrote: On 29/03/16 16:25, Reco wrote: Hi. On Tue, 29 Mar 2016 15:44:16 +0100 Tony van der Hoff <t...@vanderhoff.org> wrote: And - you have yet another default gateway for eth1. No wonder that the kernel refuses to add the same route second time. Reco Thanks, Reco. I've now commented out that line for eth1, but I still get Mar 29 15:37:47 tony-lx networking[24921]: Failed to bring up eth1. Mar 29 15:37:47 tony-lx networking[24921]: done. Now *that* requires actual investigation. What does the following sequence yield: ifdown -v eth1 root@tony-lx:~# ifdown -v eth1 ifdown: interface eth1 not configured Ok, let's try it like this then: ifdown --force eth1 ip l s dev eth1 down ip a d dev eth1 192.168.2.8/24 ip a d dev eth1 2001:8b0:ff60:6a91::8 ifup -v eth1 root@tony-lx:~# ifdown --force eth1 root@tony-lx:~# ip l s dev eth1 down root@tony-lx:~# ip a d dev eth1 192.168.2.8/24 RTNETLINK answers: Cannot assign requested address root@tony-lx:~# ip a d dev eth1 2001:8b0:ff60:6a91::8 RTNETLINK answers: Cannot assign requested address root@tony-lx:~# ifup -v eth1 Configuring interface eth1=eth1 (inet) run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wpasupplicant ip addr add 192.168.2.8/255.255.255.0 broadcast 192.168.2.255 dev eth1 label eth1 ip link set dev eth1 up ip addr add dev eth1 2001:8b0:ff60:6a91::8 ip route add default via fe80::1 dev eth0 RTNETLINK answers: File exists Failed to bring up eth1. Haha, bullseye! The whole mess is caused by exotic 'ip route' "up" hook. So, first things first: ifdown --force eth1 ip l s dev eth1 down ip a d dev eth1 192.168.2.8/24 ip a d dev eth1 2001:8b0:ff60:6a91::8 And then modify your /etc/network/interfaces like this: auto eth1 iface eth1 inet static address 192.168.2.8 netmask 255.255.255.0 network 192.168.2.0 broadcast 192.168.2.255 up /sbin/ip addr add dev eth1 2001:8b0:ff60:6a91::8/128 up /sbin/ip -6 route add default via fe80::1 dev eth1 'ifup -v eth1' should configure the interface cleanly then. As should conventional 'ifup eth1'. Next, ifup (and ifdown for that matter) is kind of paranoid. Every time you tell ifup to do something - it executes each and every 'pre-up' and 'up' in succession and all it takes is one faulty hook to get (in)famous 'Failed to bring up foo' message. The interface in question may be in UP state, and even have some IPs assigned, *but* since something went wrong - the interface must be absent from /run/network/ifstate. ifdown should only proceed if the interface is listed in the ifstate file (unless you supply --force of course). PS To answer your original query. '/sbin/service networking restart' is a valid way of changing network interface configuration *if* the network interface is configured correctly *before* and *after* the change. Else it's more-or-less required to do things a hard way - by manual reconfiguration via iproute (or ifconfig). Reco Well, sadly that was an unmitigated failure, probably due to my cack-handedness. I followed your instructions, and double-checked them, and found I lost *all* networking. I restored .../interfaces settings as they were, but failed to restart networking, and had to reboot. Obviously, Something must have gone wrong. I then got tied up with pressing stuff. I'll try again later. Cheers, -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: restarting network
On 29/03/16 17:20, Reco wrote: On Tue, 29 Mar 2016 17:08:01 +0100 Tony van der Hoff <t...@vanderhoff.org> wrote: On 29/03/16 16:25, Reco wrote: Hi. On Tue, 29 Mar 2016 15:44:16 +0100 Tony van der Hoff <t...@vanderhoff.org> wrote: And - you have yet another default gateway for eth1. No wonder that the kernel refuses to add the same route second time. Reco Thanks, Reco. I've now commented out that line for eth1, but I still get Mar 29 15:37:47 tony-lx networking[24921]: Failed to bring up eth1. Mar 29 15:37:47 tony-lx networking[24921]: done. Now *that* requires actual investigation. What does the following sequence yield: ifdown -v eth1 root@tony-lx:~# ifdown -v eth1 ifdown: interface eth1 not configured Ok, let's try it like this then: ifdown --force eth1 ip l s dev eth1 down ip a d dev eth1 192.168.2.8/24 ip a d dev eth1 2001:8b0:ff60:6a91::8 ifup -v eth1 root@tony-lx:~# ifdown --force eth1 root@tony-lx:~# ip l s dev eth1 down root@tony-lx:~# ip a d dev eth1 192.168.2.8/24 RTNETLINK answers: Cannot assign requested address root@tony-lx:~# ip a d dev eth1 2001:8b0:ff60:6a91::8 RTNETLINK answers: Cannot assign requested address root@tony-lx:~# ifup -v eth1 Configuring interface eth1=eth1 (inet) run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wpasupplicant ip addr add 192.168.2.8/255.255.255.0 broadcast 192.168.2.255 dev eth1 label eth1 ip link set dev eth1 up ip addr add dev eth1 2001:8b0:ff60:6a91::8 ip route add default via fe80::1 dev eth0 RTNETLINK answers: File exists Failed to bring up eth1. root@tony-lx:~# First, if you're configuring eth1, what's the point of setting the route via eth0. Second, if you're configuring ipv6 route, you should use 'ip -6' instead of straight 'ip'. And third, using default link-local ipv6 address as a gateway is kind of weird. Although if ipv6 /128 address mask works for you - who am I to argue. Hah, well, I don't really understand the detail. I got itfrom various howtos and wikis, which I can't now identify. I just kept following instructions - a bit like following yours - until it seemed to work. I have hosts on eth1, which need access to the world through the router, which is on eth0. It didn't seem unreasonable to set up a route via eth0 to do this. It's been running satisfactorily for years like this. It's only recently that I've been able to dedicate the time to chase up this potential problem. root@tony-lx:~# ifup -v eth1 Configuring interface eth1=eth1 (inet) run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wpasupplicant ip addr add 192.168.2.8/255.255.255.0 broadcast 192.168.2.255 dev eth1 label eth1 RTNETLINK answers: File exists Failed to bring up eth1. This seems to be the current source of trouble. I wonder what what indeed? cheers, -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: restarting network
On 29/03/16 16:25, Reco wrote: Hi. On Tue, 29 Mar 2016 15:44:16 +0100 Tony van der Hoff <t...@vanderhoff.org> wrote: And - you have yet another default gateway for eth1. No wonder that the kernel refuses to add the same route second time. Reco Thanks, Reco. I've now commented out that line for eth1, but I still get Mar 29 15:37:47 tony-lx networking[24921]: Failed to bring up eth1. Mar 29 15:37:47 tony-lx networking[24921]: done. Now *that* requires actual investigation. What does the following sequence yield: ifdown -v eth1 root@tony-lx:~# ifdown -v eth1 ifdown: interface eth1 not configured root@tony-lx:~# ifquery eth1 root@tony-lx:~# ifquery eth1 address: 192.168.2.8 netmask: 255.255.255.0 network: 192.168.2.0 broadcast: 192.168.2.255 up: ip addr add dev eth1 2001:8b0:ff60:6a91::8 up: ip route add default via fe80::1 dev eth0 dns-nameservers: 192.168.1.1 dns-search: magpieway.net root@tony-lx:~# ip a l dev eth1 root@tony-lx:~# ip a l dev eth1 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether bc:ae:c5:29:77:d8 brd ff:ff:ff:ff:ff:ff inet 192.168.2.8/24 brd 192.168.2.255 scope global eth1 valid_lft forever preferred_lft forever inet6 2001:8b0:ff60:6a91::8/128 scope global valid_lft forever preferred_lft forever inet6 fe80::beae:c5ff:fe29:77d8/64 scope link valid_lft forever preferred_lft forever root@tony-lx:~# ifup -v eth1 root@tony-lx:~# ifup -v eth1 Configuring interface eth1=eth1 (inet) run-parts --exit-on-error --verbose /etc/network/if-pre-up.d run-parts: executing /etc/network/if-pre-up.d/wpasupplicant ip addr add 192.168.2.8/255.255.255.0 broadcast 192.168.2.255 dev eth1 label eth1 RTNETLINK answers: File exists Failed to bring up eth1. root@tony-lx:~# ip a l dev eth1 root@tony-lx:~# ip a l dev eth1 3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether bc:ae:c5:29:77:d8 brd ff:ff:ff:ff:ff:ff inet 192.168.2.8/24 brd 192.168.2.255 scope global eth1 valid_lft forever preferred_lft forever inet6 2001:8b0:ff60:6a91::8/128 scope global valid_lft forever preferred_lft forever inet6 fe80::beae:c5ff:fe29:77d8/64 scope link valid_lft forever preferred_lft forever root@tony-lx:~# I guess, if it never goes down, it can never come up Cheers, -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: restarting network
On 29/03/16 15:34, Reco wrote: Hi. On Tue, Mar 29, 2016 at 02:10:08PM +0100, Tony van der Hoff wrote: Mar 29 10:15:06 tony-lx networking[21563]: Configuring network interfaces...RTNETLINK answers: File exists Mar 29 10:15:06 tony-lx networking[21563]: Failed to bring up eth1. Mar 29 10:15:06 tony-lx networking[21563]: done. Lines above are something to be expected, because your /etc/network/interfaces tells the kernel to do the impossible: iface eth0 inet static address 192.168.1.7 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 You have default gateway for eth0. All is good so far. iface eth1 inet static address 192.168.2.8 netmask 255.255.255.0 network 192.168.2.0 broadcast 192.168.2.255 gateway 192.168.1.1 And - you have yet another default gateway for eth1. No wonder that the kernel refuses to add the same route second time. Reco Thanks, Reco. I've now commented out that line for eth1, but I still get Mar 29 15:37:47 tony-lx networking[24921]: Failed to bring up eth1. Mar 29 15:37:47 tony-lx networking[24921]: done. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: restarting network
On 29/03/16 14:00, Brian wrote: On Tue 29 Mar 2016 at 13:37:19 +0100, Tony van der Hoff wrote: On 29/03/16 12:58, pedantsunited wrote: On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote: Any chance of seeing /e/n/i? Not until you explain what you're talking about /etc/network/interfaces Ah, OK: # The loopback network interface auto lo iface lo inet loopback # The primary network interface #allow-hotplug eth0 auto eth0 iface eth0 inet static address 192.168.1.7 netmask 255.255.255.0 network 192.168.1.0 broadcast 192.168.1.255 gateway 192.168.1.1 ## up ip addr add dev eth0 2001:8b0:ff60:6a91::7 ## up ip route add default via fe80::1 dev eth0 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.1 2001:8b0:ff60:6a90:5a8b:f3ff:fede:839c dns-search magpieway.net auto eth1 iface eth1 inet static address 192.168.2.8 netmask 255.255.255.0 network 192.168.2.0 broadcast 192.168.2.255 gateway 192.168.1.1 up ip addr add dev eth1 2001:8b0:ff60:6a91::8 up ip route add default via fe80::1 dev eth0 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 192.168.1.1 dns-search magpieway.net -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: restarting network
On 29/03/16 12:58, pedantsunited wrote: On Tue 29 Mar 2016 at 11:14:56 +0100, Tony van der Hoff wrote: Any chance of seeing /e/n/i? Not until you explain what you're talking about -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: restarting network
On 28/03/16 10:49, Tony van der Hoff wrote: What is the recommended way of restarting network services after, say, changing the parameters in /etc/network/interfaces? service networking restart doesn't seem to do the job properly. Thanks, everybody for your very helpful replies ;) It is quite correct that the "deprecated" message has appeared since long before systemd. It is also true to say that this message no longer appears in Jessie. However, maybe I was a little terse in my request for assistance. So, for the pedants: tony@tony-lx:~$ sudo service networking restart [sudo] password for tony: tony@tony-lx:~$ Then, from syslog ** Mar 29 10:14:59 tony-lx avahi-daemon[910]: Withdrawing address record for 192.168.1.7 on eth0. Mar 29 10:14:59 tony-lx avahi-daemon[910]: Leaving mDNS multicast group on interface eth0.IPv4 with address 192.168.1.7. Mar 29 10:14:59 tony-lx avahi-daemon[910]: Interface eth0.IPv4 no longer relevant for mDNS. Mar 29 10:14:59 tony-lx avahi-daemon[910]: Interface eth0.IPv6 no longer relevant for mDNS. Mar 29 10:14:59 tony-lx avahi-daemon[910]: Leaving mDNS multicast group on interface eth0.IPv6 with address 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76. Mar 29 10:14:59 tony-lx NetworkManager[882]: (eth0): link disconnected Mar 29 10:14:59 tony-lx avahi-daemon[910]: Withdrawing address record for 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76 on eth0. Mar 29 10:14:59 tony-lx networking[21457]: Deconfiguring network interfaces...done. Mar 29 10:14:59 tony-lx avahi-daemon[910]: Joining mDNS multicast group on interface eth0.IPv4 with address 192.168.1.7. Mar 29 10:14:59 tony-lx avahi-daemon[910]: New relevant interface eth0.IPv4 for mDNS. Mar 29 10:14:59 tony-lx kernel: [233902.408076] r8169 :04:06.0 eth0: link down Mar 29 10:14:59 tony-lx kernel: [233902.408116] r8169 :04:06.0 eth0: link down Mar 29 10:14:59 tony-lx kernel: [233902.408538] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready Mar 29 10:14:59 tony-lx avahi-daemon[910]: Registering new address record for 192.168.1.7 on eth0.IPv4. Mar 29 10:15:01 tony-lx ntpd[971]: Deleting interface #15 eth0, fe80::6efd:b9ff:fe00:6f76#123, interface stats: received=0, sent=0, dropped=0, active_time=42528 secs Mar 29 10:15:01 tony-lx ntpd[971]: Deleting interface #14 eth0, 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76#123, interface stats: received=48, sent=48, dropped=0, active_time=42528 secs Mar 29 10:15:01 tony-lx ntpd[971]: 2001:67c:564::12 interface 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76 -> (none) Mar 29 10:15:01 tony-lx ntpd[971]: peers refreshed Mar 29 10:15:01 tony-lx NetworkManager[882]: (eth0): link connected Mar 29 10:15:01 tony-lx kernel: [233904.748562] r8169 :04:06.0 eth0: link up Mar 29 10:15:01 tony-lx kernel: [233904.748582] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready Mar 29 10:15:03 tony-lx avahi-daemon[910]: Joining mDNS multicast group on interface eth0.IPv6 with address 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76. Mar 29 10:15:03 tony-lx avahi-daemon[910]: New relevant interface eth0.IPv6 for mDNS. Mar 29 10:15:03 tony-lx avahi-daemon[910]: Registering new address record for 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76 on eth0.*. Mar 29 10:15:05 tony-lx ntpd[971]: Listen normally on 16 eth0 2001:8b0:ff60:6a90:6efd:b9ff:fe00:6f76 UDP 123 Mar 29 10:15:05 tony-lx ntpd[971]: Listen normally on 17 eth0 fe80::6efd:b9ff:fe00:6f76 UDP 123 Mar 29 10:15:05 tony-lx ntpd[971]: peers refreshed Mar 29 10:15:06 tony-lx networking[21563]: Configuring network interfaces...RTNETLINK answers: File exists Mar 29 10:15:06 tony-lx networking[21563]: Failed to bring up eth1. Mar 29 10:15:06 tony-lx networking[21563]: done. ** All good up to the last 3 lines, where it appears that eth1 has not been brought up. In fact, that's a lie; AFAICT interface eth1 is working fine. So, there you have the background for my cry for help. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
restarting network
What is the recommended way of restarting network services after, say, changing the parameters in /etc/network/interfaces? service networking restart doesn't seem to do the job properly. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Grossly OT - WW2 start
On 26/03/16 01:13, Gene Heskett wrote: Thanks Tom. Its hell for an old fart who can still remember his grandfathers tears the night of Dec 7, 1941. Tears because he knew we would declare war. And I believe thats the last war we fully intended to win. Its all been downhill since. Cheers, Gene Heskett Hmm, despite what you guys seem to think, WW2 started on 1 Sept 1939. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: iceweasel now firefox-esr?
On 12/03/16 10:13, Joe wrote: On Sat, 12 Mar 2016 21:04:52 +1100 Andrew McGlashan <andrew.mcglas...@affinityvision.com.au> wrote: On 12/03/2016 4:37 PM, Dale Harris wrote: Huh, why is iceweasel installing firefox-esr now and not even putting in a sym. link from iceweasel to firefox? http://www.pcworld.com/article/3036509/linux/iceweasel-will-be-renamed-firefox-as-relations-between-debian-and-mozilla-thaw.html We knew it was going to happen, we did not expect to have to repair broken links when it did. Presumably it's not coming to Jessie? (yet) If you're using Testing, then you shouldn't be beyond fixing a few symlinks. But, certainly a bug. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Postfix log content
On 05/02/16 13:58, Darac Marjal wrote: On Thu, Feb 04, 2016 at 05:28:54PM +, Tony van der Hoff wrote: Hi, Running Postfix under Jessie. At some time in the past I managed to increase the logging verbosity to track down a problem, which I've solved. I now have a vast amount of data in mail.log, which is obscuring useful messages. I thought it was simply a matter of adding or removing "-v" to the service configuration stanzas in /etc/postfix/master.cf, but on reviewing that file, I see no instances of -v, e.g, smtp inetn-n--smtpd The logged data even includes users passwords in clear, as well as 20-odd lines for each email received (sample attached). Can anyone please suggest any other places to look to reset the default log level This doesn't look like verbose logging to me. I think the problem is just that you have a complex chain of processes for the message to pass through. bendel.d.o connects to you, the message is passed by the greylisting daemon postgrey and is accepted by your system. The message is then forwarded to amavis. At that point postfix is finished with that message. Amavis now checks the message and pronounces it clean. Amavis now connects back to postfix and passes the approved message back in. Postfix delivers the message to the SECOND delivery agent (virtual), which delivers it to your maildir. If you like, you could look at making amavis into what postfix calls a "Before Queue Filter" (and which everyone else calls a milter). There is an amavisd-milter package which will help with that. Basically, instead of accepting the message and THEN checking it for viruses, the message is passed through amavis DURING the smtp session. Postfix will only accept the message if amavis approves it, otherwise the remote host will be told that the message is rejected. This is a nicer solution all around, but it does mean that SMTP sessions will take longer. That is, you might not be able to accept as much mail as you would be able to using amavisd's batch mode. Thanks for he advice; I'll look into it. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Postfix log content
Hi, Running Postfix under Jessie. At some time in the past I managed to increase the logging verbosity to track down a problem, which I've solved. I now have a vast amount of data in mail.log, which is obscuring useful messages. I thought it was simply a matter of adding or removing "-v" to the service configuration stanzas in /etc/postfix/master.cf, but on reviewing that file, I see no instances of -v, e.g, smtp inet n - n - - smtpd The logged data even includes users passwords in clear, as well as 20-odd lines for each email received (sample attached). Can anyone please suggest any other places to look to reset the default log level -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England | Feb 4 17:15:20 shell postfix/smtpd[6383]: connect from bendel.debian.org[82.195.75.100] Feb 4 17:15:21 shell postgrey[3528]: action=pass, reason=client whitelist, client_name=bendel.debian.org, client_address=82.195.75.100, sender=bounce-debian-user=lists_0711=vanderhoff@lists.debian.org, recipient=lists_0...@vanderhoff.org Feb 4 17:15:21 shell postfix/smtpd[6383]: 1F3CE1BE17E: client=bendel.debian.org[82.195.75.100] Feb 4 17:15:21 shell postfix/cleanup[6388]: 1F3CE1BE17E: message-id=<1756206109536220492378@MUZAMMIL> Feb 4 17:15:21 shell postfix/cleanup[6388]: 1F3CE1BE17E: resent-message-id=<ISDj4wy8-NK.A.p7.gc4sWB@bendel> Feb 4 17:15:21 shell postfix/qmgr[2749]: 1F3CE1BE17E: from=
Re: Generating ssh key pairs
On 11/01/16 21:57, Steve Matzura wrote: > Dan, > > On Mon, 11 Jan 2016 14:15:53 -0500, Dan wrote: > >> In general, you want your SFTP users to send you their own >> public keys, and you drop them into ~user/.ssh/authorized_keys > > That's going to be difficult, as most of my users wouldn't know a > public key from their house key (LOL). I was hoping it would be > simpler than that. > I'm not about to do it for you, but I would think that it would be fairly straightforward to write a minimal script for them to generate a key pair, and install the public key appropriately on the server. -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: sexist content in the package openclipart2-png
On 02/01/16 08:52, Richard Hector wrote: > > I'm also aware that the respondents to this thread so far appear to be > (apologies if I'm mistaken) male; I'm not sure whether the women of > the list have deliberately withheld comment? > Well, I suspect that the more level-headed members of this list (and I would most certainly include the females) have all withheld comment. -- Tony van der Hoff | mailto:t...@vanderhoff.org Ariège, France |
Backports
What is the coorect way to request the inclusion of a backport of a package in testing (python3-pygame) to stable? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: apt-get error messages
On 08/12/15 13:41, Chris Bannister wrote: *groan* *sigh* ... I wonder why there's not a 'dpkg --print-architectures' which prints out *all* the architectures it knows about. Because you haven't written it yet? -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
Re: Recommendations for interactive use shell
On 28/10/15 17:30, Mario Castelán Castro wrote: Hello. For interactive use, I have only seriously used Bash and Fish <http://fishshell.com/>. Oh, yes; from that web site: "Finally, a command line shell for the 90s" Woo, cutting edge, or what! -- Tony van der Hoff| mailto:t...@vanderhoff.org Buckinghamshire, England |
