attn Frank
by Scott Berry
Frank,
Goofed up on the ip.
The ip address is:
67.54.156.70
Sorry about that.
16 years, 11 months
RE: How to install rshd on Fedora 7.
by 小波 顾
Thanks, the applications are different DB2 instances on the same computer, so security is not an issue.
> Date: Tue, 3 Jul 2007 15:22:17 -0400> From: tom.horsley(a)att.net> To: fedora-list(a)redhat.com> Subject: Re: How to install rshd on Fedora 7.> > On Tue, 3 Jul 2007 17:35:58 +0800> 小波 顾 <guxiaobo1982(a)hotmail.com> wrote:> > > 2. How to config rshd running as a service on Fedora 7? I have read some articles about using initd, but fedora 7 uses xinetd, which I am not familiar with.> > Not much different, you just need to make sure the rsh-server rpm is> installed and edit the /etc/xinetd.d/rshd script (or whatever> it happens to be named) to say "disabled=no" instead of> the default "disabled=yes".> > Something like:> > yum install rsh-server> chkconfig --level 2345 xinetd on> (edit /etc/xinetd.d/rshd here using your favorite editor)> /etc/init.d/xinetd restart> > should get things running.> > That, and you'll also have to wade through the> 10,477 mails you'll get telling you never to run rshd because> it is insecure :-).> > -- > fedora-list mailing list> fedora-list(a)redhat.com> To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
_________________________________________________________________
Make every IM count. Download Windows Live Messenger and join the i’m Initiative now. It’s free.
http://im.live.com/messenger/im/home/?source=TAGWL_June07
16 years, 11 months
khubd is at 100%-what is causing this?
by John Cox
I'm using FC7. Whenever I use my USB drive or pen drive, khubd starts
as it should but won't stop. It stays at 100% on one of the CPUs.
I can't kill it. I don't have this problem on my laptop.
How can I track down what is hanging up khubd?
16 years, 11 months
Firefox won't click
by Konstantin Svist
Hi,
I'm having a problem with Firefox: every once in a while
(intermittently) it doesn't follow the URL I click and/or doesn't go
back/forward in history. It just "blinks a little bit as if it started
the process of changing pages, but immediately stops and stays on the
same page.
If it's a normal URL, I click a few more times or reload the page and it
starts working. Sometimes, though, it happens when I click on a button
in web store(s) - the button becomes disabled (so as to not let me
submit my order twice) but the request doesn't actually get to the store.
I have some extensions that might be making this happen... here are the
ones that I think are relevant:
Adblock Plus
Fasterfox
Redirect Remover (set in "allow redirects" mode)
Tab Mix Plus
Does anyone else have this problem?
Thx
16 years, 11 months
M2N-MX sound problem
by Paul Erickson
For some reason, I can only get sound from one of the channels on my
M2N-MX board. A google search
indicates that others have encountered this, but the solutions seem to
be for other distributions.
Any thoughts?
--
----------------------------------------------------------------
cheers, Paul - VA7NT - email: va7nt(a)telus.net
"Those who hear not the music, think the dancers mad."
“Tolerance becomes a crime when applied to evil.” - Thomas Mann
"That state which separates it's warriors from it's scholars will have it's thinking done by cowards and fighting done by fools" - Thucydides - The Pelopenisia
"The Malice of the wicked is reinforced by the weakness of the virtuous." - Churchill
16 years, 11 months
right permission set for /tmp
by Gianluca Cecchi
What should it be the correct set of permissions for /tmp on a fc7 system?
Does this change if /tmp is itself a mounted filesytem or not?
I just verified that on my fc7 I have now
$ ll -d /tmp
drwxr-xr-x 46 1000 users 36864 2007-07-03 23:10 /tmp
where user id 1000 is not assigned to any user..... and so it seems only
root can wrtite to it....
I recently had a power failure and I needed to fsck my fs.
I think that the problem I posted at
https://www.redhat.com/archives/fedora-list/2007-July/msg00433.html
could be related with these wrong settings....
Thanks
16 years, 11 months
Re: gdmgreeter refuses to start in fc7
by Gianluca Cecchi
On Tue, 03 Jul 2007 16:09:16 -0600 Karl Larsen wrote:
> Relax. What you think your tar changed is not changed. the permissions you
show are what I have. There is no way tar will change directories.
Karl
It is not so.
See below. We work starting in /tmp. Try yourself.
[root@localhost tmp]# cd /tmp
[root@localhost tmp]# mkdir a
[root@localhost tmp]# chmod 755 a
[root@localhost tmp]# ll -d a
drwxr-xr-x 2 root root 4096 2007-07-04 00:34 a
[root@localhost tmp]# cd a
[root@localhost a]# tar jcvf ../a.tar.bz2 ./
./
[root@localhost a]# tar jtvf ../a.tar.bz2
drwxr-xr-x root/root 0 2007-07-04 00:34:27 ./
(more files following if a contained any files/directories but for the
example it is the directory itself the problem)
[root@localhost a]# cd ..
[root@localhost tmp]# mkdir b
[root@localhost tmp]# chmod 777 b
[root@localhost tmp]# ll -d b
drwxrwxrwx 2 root root 4096 2007-07-04 00:35 b
[root@localhost tmp]# cd b
[root@localhost b]# tar jxvf /tmp/a.tar.bz2
./
[root@localhost b]# ll -d .
drwxr-xr-x 2 root root 4096 2007-07-04 00:34 .
So if you untar, AS ROOT, into a directory an archive that contains the root
directory itself, you overwrite the permissions of the dir.
You (I actually ;-)
- should not use root
- verify archive before extracting
- create archive without the leading ./ dir itself
16 years, 11 months
gdmgreeter refuses to start in fc7
by Gianluca Cecchi
After I convinced my wife to use Linux and three days of satisfied use of
fc7, today it seems the gdm greeter refuses to start... ;-(
I'm not at the PC but I connected remotely.
She says that at the screen she gets "the greeter refused to start,
retry...". If she presses ok the same happens.
Already tried to restart but the same...
In messages I have:
Jul 3 14:40:34 localhost gdmgreeter[3129]: The accessibility registry was
not found.
Jul 3 14:40:38 localhost gdm[3025]: failsafe dialog failed (inhibitions: 0
0)
Jul 3 14:40:38 localhost gdm[3025]: failsafe dialog failed (inhibitions: 0
1)
Jul 3 14:40:57 localhost gdmgreeter[3180]: The accessibility registry was
not found.
Jul 3 14:41:02 localhost gdm[3025]: failsafe dialog failed (inhibitions: 0
0)
Jul 3 14:41:02 localhost gdm[3025]: failsafe dialog failed (inhibitions: 0
1)
Strange is that
[root@localhost log]# ps -ef|grep -E "X|gdm" | grep -v grep
gives:
root 1733 1 0 14:39 ? 00:00:00 /sbin/mount.ntfs-3g
/dev/sda1 /XP -o rw,nls=utf8
root 3025 1 0 14:40 ? 00:00:00 /usr/sbin/gdm-binary
-nodaemon
root 3107 1 0 14:40 ? 00:00:00 /usr/sbin/gdm-binary
-nodaemon
root 3185 3025 0 14:40 ? 00:00:00 /usr/sbin/gdm-binary
-nodaemon
root 3187 3185 0 14:40 tty7 00:00:01 /usr/bin/Xorg :0 -br -audit
0 -auth /var/gdm/:0.Xauth -nolisten tcp vt7
gdm 3205 3185 0 14:41 ? 00:00:00 /usr/sbin/gdm-binary
-nodaemon
gdm 3208 3025 0 14:41 ? 00:00:00 /usr/sbin/gdm-binary
-nodaemon
yesterday I used without problems the system that is an x86_64 updated fc7.
I updated several not apparently related packages:
In yum.log I have:
Jul 02 23:31:52 Updated: xvidcore.x86_64 1.1.3-1.lvn7
Jul 02 23:31:53 Updated: livna-config-display.noarch 0.0.14a-1.lvn7
Jul 02 23:31:53 Updated: k3b-extras-nonfree.x86_64 1.0.2-1.lvn7
then I manually installed these:
Jul 03 00:54:33 Installed: xmlrpc-c.x86_64 1.06.11-2.fc7
Jul 03 00:54:36 Installed: cmake.x86_64 2.4.6-3.fc7
Strange to say, yesterday I was proposed to upgrade gnome-menus to
2.19.4but I deselected it
It seems strange as this should be a devel package not in mainstream fc7, or
not?
After the problem today I tried to upgrade it
Jul 03 14:37:49 Updated: gnome-menus.x86_64 2.19.4-1.fc7
But nothing changes...
In its changelog I can misteriously see:
* Sun Jun 17 2007 Colin Walters <walters(a)redhat.com> - 2.19.4-1
- Update to 2.19.4
* Tue May 29 2007 Matthias Clasen <mclasen(a)redhat.com> - 2.18.2-1
- Update to 2.18.2
???
In /var/log/gdm I have:
[root@localhost gdm]# ls -lrt
total 32
-rw-r--r-- 1 root root 793 2007-04-27 22:59 : 20.log.2
-rw-r--r-- 1 root root 791 2007-05-16 22:05 :20.log.1
-rw-r--r-- 1 root root 888 2007-06-14 18:47 :20.log
-rw-r--r-- 1 root root 792 2007-07-03 14:19 :0.log.4
-rw-r--r-- 1 root root 792 2007-07-03 14:40 : 0.log.3
-rw-r--r-- 1 root root 879 2007-07-03 14:40 :0.log.2
-rw-r--r-- 1 root root 792 2007-07-03 14:40 :0.log.1
-rw-r--r-- 1 root root 792 2007-07-03 14:40 :0.log
In :0.log
X Window System Version 1.3.0
Release Date: 19 April 2007
X Protocol Version 11, Revision 0, Release 1.3
Build Operating System: Fedora Core 7 Red Hat, Inc.
Current Operating System: Linux localhost.localdomain 2.6.21-1.3228.fc7 #1
SMP Tue Jun 12 14:56:37 ED
T 2007 x86_64
Build Date: 11 June 2007
Build ID: xorg-x11-server 1.3.0.0-9.fc7
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Jul 3 14:40:59 2007
(==) Using config file: "/etc/X11/xorg.conf"
(II) Module already built-in
In :0.log.2 I have this line more:
AUDIT: Tue Jul 3 14:40:51 2007: 3136 Xorg: client 2 rejected from local
host (uid 42)
Anyone experiencing this?
If I set KDE as desktop manager in /etc/sysconfig/desktop file, I get the
kdm login screen, but trying to connect I get again the login screen and in
messages:
Jul 3 15:19:45 localhost kdm_greet[5331]: Internal error: memory corruption
detected
Jul 3 15:19:45 localhost kdm: :0[5355]: Can't execute
"/usr/share/config/kdm/Xstartup": No such file or directory
Jul 3 15:19:45 localhost kdm: :0[5448]: Can't execute
"/usr/share/config/kdm/Xreset": No such file or directory
Jul 3 15:19:59 localhost kdm_greet[5453]: Internal error: memory corruption
detected
Jul 3 15:19:59 localhost kdm: :0[5466]: Can't execute
"/usr/share/config/kdm/Xstartup": No such file or directory
Jul 3 15:19:59 localhost kdm: :0[5559]: Can't execute
"/usr/share/config/kdm/Xreset": No such file or directory
Strange that under /usr/share/config/kdm/ there are only Xreset.rpmnew and
Xstartup.rpmnew ....
I renamed them as Xreset and Xstartup but nothing changes
If I set XDM in /etc/sysconfig/desktop I get the xdm login and I'm able to
log in with a primitive X session.... ;-)
Also, doing a startx from init3 I get correctly a root X Windows session....
rpm -vV gdm
gives no errors....
Can anyone point to a solution?
Thanks in advance,
Gianluca
16 years, 11 months
Well it is a what?
by Karl Larsen
I was curious to know what NetworkManager really is. So went hunting
and found:
NM-TOOL(1)
NM-TOOL(1)
nm-tool - utility to report NetworkManager state
SYNOPSIS
nm-tool
DESCRIPTION
The nm-tool utility provides information about NetworkManager,
device,
and wireless networks.
SEE ALSO
NetworkManager(1), NetworkManagerDispatcher(1)
So then the real one:
NETWORKMANAGER(1)
NETWORKMANAGER(1)
NAME
NetworkManager - network management daemon
SYNOPSIS
NetworkManager [--no-daemon] [--enable-test-devices]
DESCRIPTION
The NetworkManager daemon attempts to keep an active network
connection
available at all times. The point of NetworkManager is to
make net-
working configuration and setup as painless and automatic as
possible.
If using DHCP, NetworkManager is intended to replace default
routes,
obtain IP addresses from a DHCP server, and change nameservers
whenever
it sees fit, with the aim of making networking Just Work.
OPTIONS
The following options are supported:
--no-daemon
Do not daemonize. This is useful for debugging.
--enable-test-devices
:
This is NetManagerDispacher
NETWORKMANAGERDISPATCHER(1)
NETWORKMANAGERDISPATCHER(1)
NAME
NetworkManagerDispatcher - daemon that runs commands in
response to
off/online
SYNOPSIS
NetworkManagerDispatcher [--no-daemon]
DESCRIPTION
The NetworkManagerDispatcher daemon runs commands in the
/etc/Network-
Manager/dispatcher.d directory in response to interfaces coming
up and
down. The scripts are run alphabetically. The first parameter
is the
network interface name. The second parameter is up if the
interface is
now up and down if the interface is now down.
OPTIONS
The following options are supported:
--no-daemon
Do not daemonize. This is useful for debugging.
FILES
/etc/NetworkManager/dispatcher.d
SEE ALSO
NetworkManager(1), nm-tool(1)
NETWORKMANAGERDISPATCHER(1)
(END)
So NetManager is a demon and runs in the kernel and tries to keep
the Internet coming always and works outside the normal old methods.
Now the NetManagerDispatcher is another mouth-full that is also a
demon and you can read what it is doing by monitoring messages in the
/etc/NetworkManager/dispature.d/ directory. I jus looked and My F7 has
the NetworkManager/ but no dispature.d directory. Could be you need to
run the demons awhile to get it.
In summary all this is now terminal activity so I think all this
stuff is VERY Beta!
Karl
16 years, 11 months
Network Install Glitch (F7)
by Tim Perry
There appears to be a glitch in anaconda when I do a network install.
It goes something like this, I enter the server name and directory
name as follows
server: fedora.mirror.iweb.ca
directory: releases/7/Fedora/i386/os
and it searches for the files in this location:
ftp://fedora.mirror.iweb.ca//releases/7/Fedora/i386/os
I do back and see this:
server: fedora.mirror.iweb.ca
directory: /releases/7/Fedora/i386/os
and no matter how many times I remove the slash at the beginning of
the directory it returns when I move to the next screen.
So is anyone else having this problem or is it just me...and if it is:
How do I fix it?
Please help!
- Tim "TheBlackWidower"
16 years, 11 months