Spam acknowledging of ham at the inbound message of flaming does not seem to affect the ham thereafter.
kiyoshi のすべての投稿
webwork2@murakoshi-site
1.Again work on jtg1.japantourguide:Akismet activated key 52beeb76581d
2. Experienced many times “cannot login”. They were kind of cleared by renaming plugins and themes using ftp.
3. Finally became in good shape by recovering appropriate themes adventure and adventure-child.
4. There remains: on mobile (at least my m03), contact form submit button barely accessed.
webwork @murakoshi site
- After many troubles, restoring site and databases backups @2019.10.24 recovered almost everything.
- Backup site and databases @2019.10.30.
- But japantourguide.net cannot be logged in. Forget about this for the moment.
- and work on jsst4.japantourguide.net. It was working fine under wp4.9.12 ; updating all the plugins caused that strange black boxes; deactivating Autoptimize cleard that strange boxes.
- Based above, on japansightseeigtour.jp, deactivated Autoptimize, balack boxes gone.: Good Job!
- Back on jsst4: placed debug agent @wp-config.php;activated Akismet;reCAPTCHA set as jihsankn; akismet set on Mt.fuji contact; successfully reject trivial spam.;failed to introduce flamingo because of wp version.;now wp vesion up to 5.2.4 succesfully;seemingly all right;php version up to 7.3(CGI);php version up require message gone; still everything seems fine.;Now backup the site and related databases.
- Now work on jtg1: at the beginning, jtg1 site was not completely secure, but by clearing the discussion acceptance, the site turned to be secure.;activate Akismet key52beeb76581d;wp3.9.29 was running all right.; update to wp3.9.23?;still cannot get appropriate wp update;
- Because php update to 7.3(CGI) on jsst4 went without any problem, same php update was performed on japansightseeing, without any problem.
- jtg1 has the problem of inability of automatic wp core update, thus try manual update.; Following the procedure described at wp official site manual update to latest wp 5.4.2 went rather smoothly. Everything is seemingly O.K.;
- Now work on japantourguide: Could not be logged in. Manual wp update seemed only one choice.; Following the official procedure, updated to wp 5.4.2. Still could not be logged in 2 notices and 2 warnings.; Renaming pluginsX,was able to be logged in without any notices and warnings.; Activated akismet key
52beeb76581d; - Remaining issues:1.Akismet&CF7&reCAPTCHA does’t work at japantourguide; 2.Either php7.1 or7.3 makes FATAL ERROR at japansightseeingtour/dashboard when clicking plugins at sidebar.
- japansightseeingtour: update php7.3 was O.K. by deactivating WP-editor, thus deleted this plugin.;Noteworthily,PHP Compatibility Checker could not detect the WP-Editor imcomatibilily to PHP7.1 nor 7.3.; This site claims to be healthy by Site Health Checker @2019/11/04. Remains: cannot set akismet protect on Homepage contact.
ffftp access .ftpaccess
@lolipop: .ftpaccess wil be set or cleared by FTPアクセス制限: should check this!
FTPアクセス制限 page also tells current connecting host address.
debian-nakym xfce gtk
- Applicaions->application manager->xfce-appearance->font->14
- install pkg-config;
- Don’t forget: make clean;
dual boot on NewKiyoshi
- On Win10: download:
http://cdimage.debian.org/cdimage/unofficial/non-free/firmware/ current/firmware.zip→usb/firmware→展開 - On debian: prepare iwlwifi
dual boot on M-NotePC3
- Shrink windows(C:) to 144.38GB leaving 78.13GB unallocated.
- Prepare Win recovery usb for safety on ADATA-UV150(RedSort)(8.44/28.8GB)(nominal32GB).
- Important!!:Win10高速スタート解除;コントロールパネル➝ハードウェアとサウンド➝電源オプション➝システム設定➝現在利用可能でない設定を変更➝高速スタートアップ:uncheck→変更保存:
- Insert Debian Install USB (ELECOM MF-KCU3A?)
- BIOS設定:1.secure boot :disabled 2. Boot optionPriorities:Top Boot Option #1:[UEFI:ELECOM MF-KCU3A1100,Partition 1]; UEFI setting: all enabled.→Boot: UEFI Boot: Enabled
- Debian installer started successfully.
- wifidriver preparation is advised, but you can neglect this and just go ahead.
- Mirror cannot be used by error. Proceed without mirror.
- Selected all the available softwares.
- Select default display manager: gdm3
NDOT firmware SC&AD -C
- onAVRdragon: spare C (This was porgrammed @edco@2019.07
- (mega164P) sig: 0x1E 0x94 0x0A;fuse read: 0xF7, 0x99, 0xFF; means:JTAGEN,SPIEN,Fullswing Xtal 16Kclk+65ms, lockbit read: 0xFF;
- onAVRdragon:2019-07-12-2(programmed @edco@2019-07)
- (mega164P) sig: 0x1E 0x94 0x0A;fuse read : 0xF7, 0x99, 0xFF; means:JTAGEN,SPIEN,Fullswing Xtal 16Kclk+65ms, lockbit read: 0xFF;
- onAVRdragon: SCAD-U4-C 04/30 8(programmed @2010?/04-30)
- (mega164P) sig read: 0x1E 0x94 0x0A;fuse read:0xF7,0xD9,0xFF;meansSPIE, Fullswing Xtal 16Kclk+65ms; lockbit read: 0xFF;
- Note@2010/01/06 says:mega164Pfuse:high byte: default 0x99 (may not work) ,JTAG disabled 0xD9 (This is safer)
- Above check and discussion explains why new SCAD mega164P did not work!!
session autologout debian-oldKiyoshi
gnomeclassic:
system tools ->settings->power->
Black screen->Never, Automatic suspend->off, When Power Button pressed->Nothing
Debian session timeout
in the “/etc/ssh/sshd_config” file as you said
TCPKeepAlive yes
ClientAliveInterval 30
ClientAliveCountMax 3000
this 4 hours is okey for me,