init does not respawn mgetty
by Don Russell
I created a new file in /etc/event.d in the hope that mgetty would be
started automatically, and respawned when it ends.
Well, it starts fine on system restart, but when mgetty ends, that's
it... no respawn. :-(
This is Fedora 9
I created this ttyS1 file in /etc/event.d, which I modeled after an
existing file (tty1) :
# ttyS1 - mgetty
#
# This service maintains an mgetty on ttyS1 from the point the system is
# started until it is shut down again.
# DNR 2008-10-29
description "mgetty for Caller ID modem"
start on stopped rc2
start on stopped rc3
start on stopped rc4
start on stopped rc5
start on started prefdm
stop on runlevel 0
stop on runlevel 1
stop on runlevel 6
exec /usr/local/sbin/mgetty -n 2 ttyS1
respawn
But, after mgetty answers an incoming call, and ends... it is not
respawned... so a second call is never answered.
Where do I find documentation on the contents of these files in
/etc/event.d or is there a different mechanism I should be using for
such things?
Thanks
15 years, 4 months
[Thanks][Everything running just fine]
by Jorge Boscan Etura
Hello
I have an hp dv6139eu laptop running F8 and this is to say that
it works just fine, it is being used 24/7, no crash.
Thank you Fedora Team!!
--
[Jorge J. Boscán Etura]
quando omni flunkus moritatus
15 years, 4 months
ATA Problem with Kernel 2.6.26.6-79
by Andrig T. Miller
After booting the with the latest 2.6.26.6-79 kernel on Fedora 9, my system
became extremely slow. To the point that Gnome menus would take 20-30
seconds just to drop down. Loading applications as simple as gedit would
take a minute or two. In looking into this problem, I opened a terminal and
started top. It showed my system at nearly 100% wait time on the CPU. Then
I started poking around the logs (/var/log/messages), and I kept seeing the
following errors, repeat over and over again:
Nov 4 03:08:54 localhost kernel: ata1.00: exception Emask 0x0 SAct 0x0 SErr
0x0 action 0x0
Nov 4 03:08:54 localhost kernel: ata1.00: BMDMA stat 0x24
Nov 4 03:08:54 localhost kernel: ata1.00: cmd
c8/00:a0:09:9a:3d/00:00:00:00:00/e0 tag 0 dma 81920 in
Nov 4 03:08:54 localhost kernel: res 51/40:00:18:9a:3d/00:00:00:00:00/e0
Emask 0x9 (media error)
Nov 4 03:08:54 localhost kernel: ata1.00: status: { DRDY ERR }
Nov 4 03:08:54 localhost kernel: ata1.00: error: { UNC }
Nov 4 03:10:48 localhost kernel: ata1.00: configured for UDMA/100
Nov 4 03:10:48 localhost kernel: ata1: EH complete
So, I thought I had my hard disk failing, and I was very concerned. I found
some posts where others were having the same problem, but no one really
thought it was an issue. All the other posts where for RAID setups though,
on servers, so they may not see the interactivity issues that I was seeing.
So, as an experiment, I booted the older 2.6.26.5-45 kernel, and guess
what? No ata error messages in /var/log, and the responsiveness of my
system has returned to normal.
This clearly looks like a bug in the ata code somewhere to me.
Any ideas?
15 years, 4 months
Re: Preventing USB automount
by Steve Berg
john wendel wrote:
> Tom Horsley wrote:
>> On Mon, 3 Nov 2008 15:18:55 -0600 (CST)
>> "Steve Berg" <sberg(a)mississippi.com> wrote:
>>
>>> Is there an easy rule to create for udev that will turn off that
function?
>
> Or you could take the easy way out (like I do), "chkconfig haldaemon
off". I don't miss it at all.
>
> Regards,
>
> John
>
Yep, that does work, unfortunately it also breaks a few things I don't
want to break
So far I've managed to tweak the rule in 50-udev-default.rules so I at
least get an email notification that a usb device has been attached. Now
I need to do that and prevent the mounting of said device.
Maybe somebody can offer advice on this: If I leave the libusb section in
50-udev-default.rules file and put my new rule that does notification in a
20-local.rules I understand that the 20 file is a higher priority. But
does that also mean that if a new device gets a hit in the 20 file that it
will ignore the rule in 50? Or should I be commenting out the libusb
entry in 50 so it's disabled and only the 20-local.rules file will take
action?
--
* Stephen Berg *
* sberg(a)mississippi.com *
* http://iceberg.3c0x1.com *
* Sinners can repent, *
* But stupid is forever. *
--
* Stephen Berg *
* sberg(a)mississippi.com *
* http://iceberg.3c0x1.com *
* Sinners can repent, *
* But stupid is forever. *
15 years, 4 months
fancyheadings.sty in F9?
by Globe Trotter
Hi,
I have an old LaTeX document which uses fancyheadings package. It used to be in the tetex distributions. However, it does not appear to be around in TeXlive on F9. What are my alternatives?
Can someone please help me with this?
Many thanks and best wishes,
Trotter
15 years, 4 months
Can't load cpuspeed
by Boggiano
Hi all,
I can't run cpuspeed on my wife's notebook:it's a Acer Aspire 3630 and
it use a Intel Celeron CPU.
FC8 and kernel 2.6.26.6-49.fc8.
I even can't load the acpi_cpufreq module, this is the error message:
FATAL: Error inserting acpi_cpufreq
(/lib/modules/2.6.26.6-49.fc8/kernel/arch/x86/kernel/cpu/cpufreq/acpi-cpufreq.ko):
No such device
And BTW, what is the correct value I have to in the file
/etc/sysconfig/cpuspeed in the line DRIVER ?
I put down here some info, please let me know if you need others.
Thanks
Ale
>cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 6
model : 13
model name : Intel(R) Celeron(R) M processor 1.60GHz
stepping : 8
cpu MHz : 1600.097
cache size : 1024 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 apic mtrr pge mca
cmov pat clflush dts acpi mmx fxsr sse sse2 ss tm pbe nx up bts
bogomips : 3201.58
clflush size : 64
power management:
>cat /proc/acpi/processor/CPU0/throttling
state count: 8
active state: T0
state available: T0 to T7
states:
*T0: 100%
T1: 87%
T2: 75%
T3: 62%
T4: 50%
T5: 37%
T6: 25%
T7: 12%
>dmesg |grep -i cpu
Initializing cgroup subsys cpuset
PAT disabled. Not yet verified on this CPU type.
ACPI: SSDT 3BDF64B2, 01FB (r1 PmRef CpuPm 3000 INTL 20030224)
SMP: Allowing 1 CPUs, 0 hotplug CPUs
PERCPU: Allocating 41384 bytes of per cpu data
NR_CPUS: 32, nr_cpu_ids: 1
Initializing CPU#0
CPU 0 irqstacks, hard=c07cb000 soft=c07ab000
SLUB: Genslabs=12, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
Initializing cgroup subsys cpuacct
CPU: L1 I cache: 32K, L1 D cache: 32K
CPU: L2 cache: 1024K
Intel machine check reporting enabled on CPU#0.
CPU0: Intel(R) Celeron(R) M processor 1.60GHz stepping 08
Brought up 1 CPUs
CPU0 attaching sched-domain:
ACPI: CPU0 (power states: C1[C1] C2[C2] C3[C3])
ACPI: Processor [CPU0] (supports 8 throttling states)
Switched to high resolution mode on CPU 0
cpuidle: using governor ladder
cpuidle: using governor menu
15 years, 4 months
Re: screen + vim + paste -> not happy
by Bryn M. Reeves
Dave Feustel wrote:
> Have you tried pasting into vim running in an xterm session?
> (Past the text by going into insert and then pressing shift+insert).
Yes - running vim outside screen (xterm, gnome-terminal etc.) works
fine. Running it in screen, in either an xterm or a gnome-terminal gives
the problematic behaviour. Xorg CPU usage is noticably higher with
gnome-terminal and the delay (several minutes for gnome-terminal)
between pasting and some text appearing in the editor feels slightly
less, but the same basic problem persists.
There is no problem when pasting into vim running in a plain xterm (no
screen).
Regards,
Bryn.
15 years, 4 months
screen + vim + paste -> not happy
by Bryn M. Reeves
Hi Folks,
I've hit an odd problem when pasting large amounts of text into vim
running inside a screen session.
Steps to reproduce:
1. open a new file in vim (e.g. vim /tmp/foo) and enter insert mode
2. select a large amount of text (a few hundred lines or so)
3. paste (middle click or ctrl-c/ctrl-v) into the editor
At this point, Xorg CPU usage shoots up to close to 100%, the desktop
feels very unresponsive and the terminal window that vim is running in
flashes between a blue background with black borders and all-black.
A few minutes later, some or all of the text will appear (possibly with
some whitespace changes) in the editor and life goes back to normal. I'm
seeing this on two different systems with different graphics drivers
(i945 & nv).
I cannot reproduce this behaviour outside of screen and I've also
managed to make vim lock up a couple of times while running within
screen on f9 (I don't have exact steps to reproduce this - it seems like
some keystroke sequences trigger it but I can't make it happen at will).
I'll open a bugzilla for this, but figured I'd post it here in case
anyone's seen something similar.
Regards,
Bryn.
15 years, 4 months
mplayer dependencies on RPM Fusion
by Andras Simon
It seems that mplayer's dependencies on RPM Fusion include (perhaps
indirectly) mencoder, samba-common and samba-winbind. Are these really
necessary? This does matter on a netbook with 4G SSD.
Andras
15 years, 4 months