[gentoo-user] lsof on fail2ban
AFAIK fail2ban tails log files to find login failures, but when i try lsof its not reading daemon.log/auth.log/whatever for sshd's login failure messages. # ps -ef | grep fail2 root 518 1 0 Jan01 ?00:05:22 /usr/bin/python3.4 /usr/lib64/python-exec/python3.4/fail2ban-server -s /run/fail2ban/fail2ban.sock -p /run/fail2ban/fail2ban.pid -x -b root 21407 21250 0 11:45 pts/100:00:00 grep --colour=auto fail2 # lsof -p 518 | grep var fail2ban- 518 root5w REG 9,126 107 263885 /var/log/fail2ban.log fail2ban- 518 root6u REG 9,12616384 1180229 /var/lib/fail2ban/fail2ban.sqlite3 # What am I missing?
[gentoo-user] metalog: postrotate_cmd
Hi,
what happens when a postrotate_cmd started by metalog never finishes?
Am I assuming right that in ...
,
|postrotate_cmd
| postrotate_cmd = "/path/to/a/program". Run specified pro‐
| gram after a log file has been rotated. The program is
| passed the date, the program name ("metalog"), and the new
| logfile name.
`
... "new logfile name" means the name the old file is renamed to?
--
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us. Finally, this fear has become reasonable.
Re: [gentoo-user] setxkbmap -option ctrl:nocaps
Sid S writes: > You should be using xmodmap OR xsetkbmap OR the configuration file, > not all three (though they shouldn't interfere with each other if > configured properly - they'd just all be doing the same thing). It would be fine if they did what I want :) > If you wish to set Caps_Lock to be Control_L, you need to redefine > keycode 66, not 37 (37 is Control_L by default). Oh, thank you! You're right, I didn't change 66 when I made a new map for this particular keyboard --- not too surprising that things get messed up then. It seems to work now :) > You may also need to add "clear lock" or "clear Lock" before that > line. Sometimes it will or will not work if you don't do this and will > toggle Caps_Lock and press Control_L. Weird. Experiments with that quite some time ago yielded error messages. IIRC some bug was introduced somewhere so these options in the keymap didn't work anymore. Perhaps the bug has been fixed in the meantime, I don't know ... > Alternatively, you can use xsetkbmap like you described. Yes, I looked into that quite a while ago and found it's too complicated for changing a couple keys. That must have been when this bug with xmodmap came up and ctrl:nocaps became required in xorg.conf ... -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
Re: [gentoo-user] setxkbmap -option ctrl:nocaps
Mick writes: > On Sunday 04 Jan 2015 19:53:37 lee wrote: >> Hi, >> >> I'm trying to use the CapsLock key as control key. With 'setxkbmap >> -option ctrl:nocaps' that works --- until I use 'xmodmap' to load my >> keymap. Once the keymap is loaded, the CapsLock key again works as >> CapsLock and not as control. >> >> This worked fine with other distributions. Is there anything special to >> Gentoo which breaks this? >> >> >> Section "InputClass" >> Identifier "keyboard-all" >> Driver "evdev" >> Option "XkbLayout" "de" >> Option "XkbModel" "pc105" >> Option "XkbRules" "xorg" >> Option "XkbOptions" "ctrl:nocaps,terminate:ctrl_alt_bksp" >> MatchIsKeyboard "on" >> EndSection > > What happens if you remove "ctrl:nocaps" above? It doesn't really seem to make a difference. >> ~/.xinitrc: >> [...] >> setxkbmap -option ctrl:nocaps >> xmodmap ~/.Xmodmap >> [...] >> >> >> ~/.Xmodmap: >> [...] >> keycode 37 = Control_L NoSymbol Control_L >> [...] > > and why do you need to specify this in .Xmodap? Because sometimes it doesn't work at all when I don't and because I put that there a long time ago and forgot about it. My ~/.xinitrc is about 20 years old and has been modified as needed over time. I can only say it worked fine with Fedora and used to work with Debian. Since someone keeps changing all the time how to configure your keyboard, and since different distributions might use different ways of doing it, I really don't know anymore how to configure a keybord --- which should be simple and easy to begin with as it used to be. I merely want my keyboard to work ... -- Again we must be afraid of speaking of daemons for fear that daemons might swallow us. Finally, this fear has become reasonable.
Re: [gentoo-user] Suspend problem.
On 01/05/2015 05:04 PM, Zesen Qian wrote: > kirimaks writes: > >> Hi! >> >> I have a problem, when my laptop just stands it freezes after some time. >> > Maybe completely unrelated, but have you turned off security chip[1] > in BIOS? > > [1] > https://wiki.gentoo.org/index.php?title=Suspend_and_hibernate&redirect=no#Can_not_resume_after_suspend Thanks but I don't have it in bios. Moreover genkernel working, so I think it's not a hardware problem.
Re: [gentoo-user] Suspend problem.
kirimaks writes: > Hi! > > I have a problem, when my laptop just stands it freezes after some time. > Maybe completely unrelated, but have you turned off security chip[1] in BIOS? [1] https://wiki.gentoo.org/index.php?title=Suspend_and_hibernate&redirect=no#Can_not_resume_after_suspend -- Zesen Qian (钱泽森)
Re: [gentoo-user] Radeon driver - blank console
Am 05.01.2015 um 14:42 schrieb Helmut Jarausch: Which (framebuffer?) kernel parameters have to set? Try compiling CONFIG_DRM_RADEON as module and do not enable any frame buffers, especially not CONFIG_FB_RADEON, as absurd as it sounds. This should take care of your invisible virtual terminal. Greetings --Flo
Re: [gentoo-user] setxkbmap -option ctrl:nocaps
You should be using xmodmap OR xsetkbmap OR the configuration file, not all three (though they shouldn't interfere with each other if configured properly - they'd just all be doing the same thing). If you wish to set Caps_Lock to be Control_L, you need to redefine keycode 66, not 37 (37 is Control_L by default). You may also need to add "clear lock" or "clear Lock" before that line. Sometimes it will or will not work if you don't do this and will toggle Caps_Lock and press Control_L. Weird. Alternatively, you can use xsetkbmap like you described.
[gentoo-user] Radeon driver - blank console
Hi, the recent update of virtual/opengl forced me to switch from my ati [legacy] driver to the open source driver (radeon) While I got X11 running, my console gets blanked before I can log in on the command line. Which (framebuffer?) kernel parameters have to set? It looks like the kernel or init process (openrc) tries to switch to a higher resolution (on the text console) when the screen (console) gets blanked. (Loggin in "blindly" and invoking startx, I get a running X-server). Many thanks for some pointers, Helmut
[gentoo-user] Suspend problem.
Hi! I have a problem, when my laptop just stands it freezes after some time. In syslog I have a lot of messages like this: Jan 5 03:26:11 localhost kernel: [ 3488.016576] Device suspended Jan 5 03:26:11 localhost kernel: [ 3488.042232] [] ? credit_entropy_bits+0x1df/0x2b0 Jan 5 03:26:11 localhost kernel: [ 3488.042238] [] ? add_interrupt_randomness+0x109/0x1a0 Jan 5 03:26:11 localhost kernel: [ 3488.042245] [] ? ehci_irq+0x1f5/0x2b0 Jan 5 03:26:11 localhost kernel: [ 3488.042252] [] ? add_interrupt_randomness+0x13d/0x1a0 Jan 5 03:26:11 localhost kernel: [ 3488.042260] [] handle_irq_event_percpu+0x3d/0x180 Jan 5 03:26:11 localhost kernel: [ 3488.042266] [] ? handle_irq_event_percpu+0xa7/0x180 Jan 5 03:26:11 localhost kernel: [ 3488.042274] [] handle_irq_event+0x25/0x40 Jan 5 03:26:11 localhost kernel: [ 3488.042281] [] ? handle_simple_irq+0x60/0x60 Jan 5 03:26:11 localhost kernel: [ 3488.042289] [] handle_fasteoi_irq+0x64/0x100 Jan 5 03:26:11 localhost kernel: [ 3488.042296] [] handle_irq+0x69/0x80 Jan 5 03:26:11 localhost kernel: [ 3488.042298][] do_IRQ+0x37/0xd0 Jan 5 03:26:11 localhost kernel: [ 3488.042310] [] common_interrupt+0x2c/0x34 Jan 5 03:26:11 localhost kernel: [ 3488.042317] [] ? rcu_gp_kthread+0xfb/0x590 Jan 5 03:26:11 localhost kernel: [ 3488.042324] [] ? cpuidle_enter_state+0x6f/0x160 Jan 5 03:26:11 localhost kernel: [ 3488.042332] [] cpuidle_enter+0xf/0x20 Jan 5 03:26:11 localhost kernel: [ 3488.042338] [] cpu_startup_entry+0x1fc/0x2f0 Jan 5 03:26:11 localhost kernel: [ 3488.042346] [] rest_init+0x5d/0x60 Jan 5 03:26:11 localhost kernel: [ 3488.042353] [] start_kernel+0x3a6/0x3ac Jan 5 03:26:11 localhost kernel: [ 3488.042361] [] ? set_init_arg+0x49/0x49 Jan 5 03:26:11 localhost kernel: [ 3488.042368] [] i386_start_kernel+0x12e/0x131 Jan 5 03:26:11 localhost kernel: [ 3488.042371] ---[ end trace 0dc8971a83e5fd4c ]--- Jan 5 03:26:11 localhost kernel: [ 3488.052457] [drm:__gen6_gt_force_wake_get] *ERROR* Timed out waiting for forcewake old ack to clear. Jan 5 03:26:11 localhost kernel: [ 3488.059868] [drm:__gen6_gt_wait_for_thread_c0] *ERROR* GT thread status wait timed out Jan 5 03:26:11 localhost kernel: [ 3488.059873] [ cut here ] Jan 5 03:26:11 localhost kernel: [ 3488.059901] WARNING: CPU: 0 PID: 0 at drivers/gpu/drm/i915/intel_uncore.c:132 gen6_gt_check_fifodbg.isra.10+0x3c/0x50 [i915]() Jan 5 03:26:11 localhost kernel: [ 3488.059904] GT wake FIFO error 0x I'm using current gentoo sources (linux-3.17.7-gentoo) but I also tried to use linux-3.18.1, it freezes as well. On genkernel everything working well, so I guess the problem is with kernel configuration. Some kernel sections: # # Power management and ACPI options # CONFIG_SUSPEND=y CONFIG_SUSPEND_FREEZER=y CONFIG_HIBERNATE_CALLBACKS=y CONFIG_HIBERNATION=y CONFIG_PM_STD_PARTITION="" CONFIG_PM_SLEEP=y CONFIG_PM_SLEEP_SMP=y # CONFIG_PM_AUTOSLEEP is not set # CONFIG_PM_WAKELOCKS is not set # CONFIG_PM_RUNTIME is not set CONFIG_PM=y # CONFIG_PM_DEBUG is not set # CONFIG_WQ_POWER_EFFICIENT_DEFAULT is not set CONFIG_ACPI=y CONFIG_ACPI_LEGACY_TABLES_LOOKUP=y CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC=y CONFIG_ACPI_SLEEP=y CONFIG_ACPI_PROCFS_POWER=y # CONFIG_ACPI_EC_DEBUGFS is not set CONFIG_ACPI_AC=m CONFIG_ACPI_BATTERY=m CONFIG_ACPI_BUTTON=m CONFIG_ACPI_VIDEO=m CONFIG_ACPI_FAN=m # CONFIG_ACPI_DOCK is not set CONFIG_ACPI_PROCESSOR=m # CONFIG_ACPI_IPMI is not set CONFIG_ACPI_HOTPLUG_CPU=y # CONFIG_ACPI_PROCESSOR_AGGREGATOR is not set CONFIG_ACPI_THERMAL=m # CONFIG_ACPI_CUSTOM_DSDT is not set # CONFIG_ACPI_INITRD_TABLE_OVERRIDE is not set # CONFIG_ACPI_DEBUG is not set # CONFIG_ACPI_PCI_SLOT is not set CONFIG_X86_PM_TIMER=y CONFIG_ACPI_CONTAINER=y # CONFIG_ACPI_SBS is not set # CONFIG_ACPI_HED is not set # CONFIG_ACPI_CUSTOM_METHOD is not set # CONFIG_ACPI_BGRT is not set # CONFIG_ACPI_REDUCED_HARDWARE_ONLY is not set CONFIG_HAVE_ACPI_APEI=y CONFIG_HAVE_ACPI_APEI_NMI=y # CONFIG_ACPI_APEI is not set # CONFIG_ACPI_EXTLOG is not set # CONFIG_SFI is not set CONFIG_X86_APM_BOOT=y CONFIG_APM=y CONFIG_APM_IGNORE_USER_SUSPEND=y # CONFIG_APM_DO_ENABLE is not set CONFIG_APM_CPU_IDLE=y # CONFIG_APM_DISPLAY_BLANK is not set CONFIG_APM_ALLOW_INTS=y # # CPU Frequency scaling # CONFIG_CPU_FREQ=y CONFIG_CPU_FREQ_GOV_COMMON=y CONFIG_CPU_FREQ_STAT=m CONFIG_CPU_FREQ_STAT_DETAILS=y CONFIG_CPU_FREQ_DEFAULT_GOV_PERFORMANCE=y # CONFIG_CPU_FREQ_DEFAULT_GOV_USERSPACE is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_ONDEMAND is not set # CONFIG_CPU_FREQ_DEFAULT_GOV_CONSERVATIVE is not set CONFIG_CPU_FREQ_GOV_PERFORMANCE=y CONFIG_CPU_FREQ_GOV_POWERSAVE=m CONFIG_CPU_FREQ_GOV_USERSPACE=m CONFIG_CPU_FREQ_GOV_ONDEMAND=m CONFIG_CPU_FREQ_GOV_CONSERVATIVE=m # # x86 CPU frequency scaling drivers # # CONFIG_X86_INTEL_PSTATE is not set # CONFIG_X86_PCC_CPUFREQ is not set CONFIG_X86_ACPI_CPUFREQ=m CONFIG_X86_ACPI_CPUFREQ_CPB=y CONFIG_X86_POWERNOW_K6=m CONFIG_X86_POWERNOW_K7=m CONFIG_X86_POWERNOW_K7_ACPI=y CONFIG_
Re: [gentoo-user] eix-update, run from root, failed to write database file
Am 05.01.2015 um 11:54 schrieb Gevisz: After today's world update, the eix-update command, run under root, failed to "open the database file '/var/cache/eix/portage.eix' for writing." Nevertheless, the same command, run with ordinary user privileges, completed without error. Obviously, while updating, the priviliges are dropped to another user (root shouldn't be overused anyway). In this case, they are most likely dropped to user "portage". Try changing the owner and group of the cache to "portage". $ ls -al /var/cache/eix/portage.eix -rw-rw-r-- 1 portage portage 12302936 Dec 19 16:45 /var/cache/eix/portage.eix Greetings --Flo
[gentoo-user] eix-update, run from root, failed to write database file
After today's world update, the eix-update command, run under root, failed to "open the database file '/var/cache/eix/portage.eix' for writing." Nevertheless, the same command, run with ordinary user privileges, completed without error. Why? # eix-update Reading Portage settings .. Building database (/var/cache/eix/portage.eix) .. [0] 'gentoo' /usr/portage/ (cache: metadata-md5-or-flat) Reading category 163|163 (100%) Finished Applying masks .. Calculating hash tables .. Writing database file /var/cache/eix/portage.eix .. Can't open the database file '/var/cache/eix/portage.eix' for writing (mode = 'wb') # echo $? 1 # ls -al /var/cache/eix/portage.eix -rw-rw-r-- 1 gevis gevis 6336237 Dec 20 14:01 /var/cache/eix/portage.eix $ eix-update Reading Portage settings .. Building database (/var/cache/eix/portage.eix) .. [0] 'gentoo' /usr/portage/ (cache: metadata-md5-or-flat) Reading category 163|163 (100%) Finished Applying masks .. Calculating hash tables .. Writing database file /var/cache/eix/portage.eix .. Database contains 17931 packages in 163 categories. $ echo $? 0
