You are not logged in.
- Topics: Active | Unanswered
#1 2004-05-10 08:42:09
- monolin
- Member
- Registered: 2004-03-06
- Posts: 31
can't start fam in rc.conf
I followed the tip in:
http://bbs.archlinux.org/viewtopic.php? … hlight=fam
and added portmap and fam in my rc.conf file.
I can see the boot messages saying that it has started File Alternation Monitor with [DONE], however when I do
ps aux|grep fam
there is no such daemon.
Then I manually started fam and ps shows there is one in:
/usr/bin/fam
What is the problem? why fam can't start well?
When false is taken for true, true becomes false;
If non-being turns into being, being becomes non-being.
Pages full of fantastic talk
Penned with bitter tears;
All men call the author mad,
None his message hears.
Offline
#2 2004-05-10 10:14:51
- dp
- Member
- From: Aarau, Switzerland
- Registered: 2003-05-27
- Posts: 3,378
- Website
Re: can't start fam in rc.conf
is there maybe anything in the system-logs?
(/var/log/errors /var/log/messages)
The impossible missions are the only ones which succeed.
Offline
#3 2004-05-10 10:33:17
- lanrat
- Member
- From: Poland
- Registered: 2003-10-28
- Posts: 1,274
Re: can't start fam in rc.conf
Check these two things: fam needs portmap to run so it should be placed after portmap in DAEMONS in rc.conf. And when fam is beeing run form rc.conf not inet.d (see man fam) it timeouts very quickly and exits. You have to change timeout value to 0 in /etc/fam/fam.conf (if I remember corretly but I'm sure you will find it).
Offline
#4 2004-05-12 00:26:45
- monolin
- Member
- Registered: 2004-03-06
- Posts: 31
Re: can't start fam in rc.conf
is there maybe anything in the system-logs?
(/var/log/errors /var/log/messages)
in /var/log/errors, I found the following errors occuring repeatedly:
I am running a firewall script, is it affecting fam?
May 13 00:25:53 myhost fam[392]: can't bind to reserved port: Cannot assign requested address
May 13 00:26:02 myhost kdm: :0[523]: PAM unable to dlopen(/lib/security/pam_console.so)
May 13 00:26:02 myhost kdm: :0[523]: PAM [dlerror: /lib/security/pam_console.so: cannot open shared object file: No such file or directory]
May 13 00:26:02 myhost kdm: :0[523]: PAM adding faulty module: /lib/security/pam_console.so
May 13 00:26:02 myhost kde-np(pam_unix)[523]: unrecognized option [service=system-auth]
May 13 00:26:02 myhost kde-np(pam_unix)[523]: unrecognized option [service=system-auth]
May 13 00:26:43 myhost pppd[631]: Cannot determine ethernet address for proxy ARP
May 13 00:58:44 myhost su[826]: pam_authenticate: Authentication failure
May 13 00:58:59 myhost pppoe[634]: read (asyncReadFromPPP): Session 9176: Input/output error
May 13 01:00:21 myhost pppd[3054]: Cannot determine ethernet address for proxy ARP
May 13 01:03:35 myhost pppoe[3055]: read (asyncReadFromPPP): Session 10014: Input/output error
May 13 01:16:23 myhost pppd[3199]: Cannot determine ethernet address for proxy ARP
May 13 01:24:13 myhost pppoe[3200]: read (asyncReadFromPPP): Session 11270: Input/output error
May 13 08:30:04 myhost pppd[3490]: Cannot determine ethernet address for proxy ARP[/code]
When false is taken for true, true becomes false;
If non-being turns into being, being becomes non-being.
Pages full of fantastic talk
Penned with bitter tears;
All men call the author mad,
None his message hears.
Offline
#5 2004-05-12 01:10:58
- lanrat
- Member
- From: Poland
- Registered: 2003-10-28
- Posts: 1,274
Re: can't start fam in rc.conf
I'm not sure but from fam man page:
-L Local-only mode. fam will only accept
requests from clients running on the local
machine. This overrides the local_only flag
in the configuration file. This option is
ignored if fam is started by inetd.
and
local_only If set to true, fam will ignore requests from
remote fams. This is false by default. Set-
ting this option to true is the same as using
the -L command-line option. This option is
ignored if fam is started by inetd.
I suggest changing local_only to true in /etc/fam/fam.conf. Does it help ? (I assume that you have set up timeout to 0, right? And if this error is occuring repatedly then doesn't it mean that fam works? :-))
Offline
#6 2004-05-12 11:40:26
- monolin
- Member
- Registered: 2004-03-06
- Posts: 31
Re: can't start fam in rc.conf
I suggest changing local_only to true in /etc/fam/fam.conf. Does it help ? (I assume that you have set up timeout to 0, right? And if this error is occuring repatedly then doesn't it mean that fam works? :-))
I have set up the timeout to 0 so I assume ps can tell there is a fam daemon running. But in my case, I can't see this daemon.
Do you have fam running in the background? and Do you know a way to tell that fam is working properly?
When false is taken for true, true becomes false;
If non-being turns into being, being becomes non-being.
Pages full of fantastic talk
Penned with bitter tears;
All men call the author mad,
None his message hears.
Offline
#7 2004-05-12 12:02:06
- Mr Green
- Forum Fellow
- From: U.K.
- Registered: 2003-12-21
- Posts: 5,926
- Website
Re: can't start fam in rc.conf
Have you got portmap .....?
Never mind saw you have it....
paste your rc.conf deamons line ....
Mr Green
Mr Green
Offline
#8 2004-05-12 14:57:58
- lanrat
- Member
- From: Poland
- Registered: 2003-10-28
- Posts: 1,274
Re: can't start fam in rc.conf
Ps should thell you that fam is started (not necessary working properly :-)). How do you start fam manually? Try
/etc/rc.d/fam startif you didn't already and see if it generates any errors (look in all logs: dmesg, messages, kernel etc.). And first try ps ax | grep portmap of course just to be sure that portmap is running :-) If it won't work stop first manually (or disable with !) anything you can from the DEAMONS line in rc.conf. You didn't mess with rc.d script or other settings in /etc/fam/fam.conf?
Offline
#9 2004-05-12 15:10:52
- Mr Green
- Forum Fellow
- From: U.K.
- Registered: 2003-12-21
- Posts: 5,926
- Website
Re: can't start fam in rc.conf
Mr Green
Offline