Re: [Cooker] Bug report on initscripts-7.06-3mdk
On Tue, 2003-02-11 at 21:12, Joseph Wang wrote: > My orinico wireless PCMCIA card will not start up with 7.06-3mdk. It > gets to initializing eth0 > and then hangs. Moving the S11pcmcia link to S08pcmcia so that pcmcia > is initialized before network > allows the card to work, but I get an error message about ifplugd when > it gets to the network > initialization script. > > I believe that it worked as of 7.06-1mdk and am positive that it worked > with 7.04-3mdk If you use pcmcia network cards you can do # chkconfig --level 2345 network off # chkconfig --level 2345 internet off and you won't get the errors and your ethernet connection gets started correctly by pcmcia least it works for me. > >
Re: [Cooker] Bug report on initscripts-7.06-3mdk
James Sparenberg <[EMAIL PROTECTED]> writes: > On Tue, 2003-02-11 at 21:12, Joseph Wang wrote: > > My orinico wireless PCMCIA card will not start up with 7.06-3mdk. It > > gets to initializing eth0 > > and then hangs. Moving the S11pcmcia link to S08pcmcia so that pcmcia > > is initialized before network > > allows the card to work, but I get an error message about ifplugd when > > it gets to the network > > initialization script. > > > > I believe that it worked as of 7.06-1mdk and am positive that it worked > > with 7.04-3mdk > > If you use pcmcia network cards you can do > > # chkconfig --level 2345 network off > # chkconfig --level 2345 internet off > > and you won't get the errors and your ethernet connection gets started > correctly by pcmcia least it works for me. Can you check that you have the last versions of ifplugd, hotplug and initscripts and if the problem continues, send me the logs and your exact config. -- Fred - May the source be with you
Re: [Cooker] Bug report on initscripts-7.06-3mdk
On Thu, 2003-02-13 at 05:04, Frederic Lepied wrote: > James Sparenberg <[EMAIL PROTECTED]> writes: > > > On Tue, 2003-02-11 at 21:12, Joseph Wang wrote: > > > My orinico wireless PCMCIA card will not start up with 7.06-3mdk. It > > > gets to initializing eth0 > > > and then hangs. Moving the S11pcmcia link to S08pcmcia so that pcmcia > > > is initialized before network > > > allows the card to work, but I get an error message about ifplugd when > > > it gets to the network > > > initialization script. > > > > > > I believe that it worked as of 7.06-1mdk and am positive that it worked > > > with 7.04-3mdk > > > > If you use pcmcia network cards you can do > > > > # chkconfig --level 2345 network off > > # chkconfig --level 2345 internet off > > > > and you won't get the errors and your ethernet connection gets started > > correctly by pcmcia least it works for me. > > Can you check that you have the last versions of ifplugd, hotplug and > initscripts and if the problem continues, send me the logs and your > exact config. I did at the time I wrote this and I'm in the process of upgrading now to todays' stuff. The last upgrade broke me badly, and I'm just now getting back to a working system. (Seems that as time goes on I got slower and slower until kdm dropped the ball completely.) The "problem" was that network and internet got started before pcmcia and If pcmcia is moved to start before them, then ifplugd complains that an instance of it is already running. I'll send the info ASAP. James PS... which logs do you need?
solution to pcmcia network problems (was Re: [Cooker] Bug report on initscripts-7.06-3mdk)
On Thu, 2003-02-13 at 22:03, James Sparenberg wrote: > On Thu, 2003-02-13 at 05:04, Frederic Lepied wrote: > > James Sparenberg <[EMAIL PROTECTED]> writes: > > > > > On Tue, 2003-02-11 at 21:12, Joseph Wang wrote: > > > > My orinico wireless PCMCIA card will not start up with 7.06-3mdk. It > > > > gets to initializing eth0 > > > > and then hangs. Moving the S11pcmcia link to S08pcmcia so that pcmcia > > > > is initialized before network > > > > allows the card to work, but I get an error message about ifplugd when > > > > it gets to the network > > > > initialization script. > > > > > > > > I believe that it worked as of 7.06-1mdk and am positive that it worked > > > > with 7.04-3mdk > > > > > > If you use pcmcia network cards you can do > > > > > > # chkconfig --level 2345 network off > > > # chkconfig --level 2345 internet off > > > > > > and you won't get the errors and your ethernet connection gets started > > > correctly by pcmcia least it works for me. > > > > Can you check that you have the last versions of ifplugd, hotplug and > > initscripts and if the problem continues, send me the logs and your > > exact config. > > I did at the time I wrote this and I'm in the process of upgrading now > to todays' stuff. The last upgrade broke me badly, and I'm just now > getting back to a working system. (Seems that as time goes on I got > slower and slower until kdm dropped the ball completely.) The "problem" > was that network and internet got started before pcmcia and If pcmcia is > moved to start before them, then ifplugd complains that an instance of > it is already running. I'll send the info ASAP. Frederic gave me the real reason for this problem in private email. Since lots of people seem to be having it, here it is: Since the pcmcia service starts pcmcia network adapters, there's no reason for them to be started by the network service. Hence /etc/sysconfig/ifcfg-ethX entries for PCMCIA network cards should *NOT* have ONBOOT= set to YES. Set it to NO instead (ONBOOT=NO). This will stop network from trying to bring up the interface; pcmcia will do it instead, and this ought to solve the problems. -- adamw
Re: solution to pcmcia network problems (was Re: [Cooker]Bug report on initscripts-7.06-3mdk)
On Fri, 2003-02-14 at 02:51, Buchan Milne wrote: > James Sparenberg wrote: > > > One question though... what is it in Killall that tries to stop > > Samba... I've noticed it first here testing 9.1 but on my 9.0 and 8.2 > > boxes as well smb gets stopped nmb reports failed then once killall > > starts up it then again attempts to shutdown smb and nmb again. This is > > no show stopper I think I submitted the bug as a p4, but inevitably the > > user who has the least understanding (or capability to understand) is > > the one who panics when they see the FAILED in big read letters. > > Probably a misconfigured samba and the fact that we start/stop smbd and > nmbd together. So, /etc/rc.d/init.d/smb stops smbd, tries to stop nmbd > and fails (was not running or had a name conflict or something like > that), and since both killprocs did not succeed, it does not remove the > lock file, so it is run again. this is the hard part. Since I'm in a shutdown situation how do I check to see if the lockfile is getting removed or not. > > I guess we should put a check in to see if nmbd and smbd are really > running, but it may be better to leave the error so the user knows they > have something to fix? This is the thing... what is the fix. Samba is working quite well so I'm pretty sure the config is good. (printing shares etc are solid.) I really don't do much more than use samba to print on a windows box at home. > > SuSE has split their init scripts for samba into one each for smbd and > nmbd, mainly to allow an nmbd restart (to reregister in WINS for > example) without killing smbd (and the connections). But it makes > complications ... I would rather add another option to the script that > just restarts nmbd ... but I have never had this problem, so I do not > have a setup to test ... killall -HUP nmbd always worked for me. As I said there is no real "problem" here. other than the hassle of explaining to the users that this isn't a real problem. What I really need is a way to pump startup and shutdown info to dev/null so that my "experts" don't see it *grin* > > Buchan
Re: solution to pcmcia network problems (was Re:[Cooker] Bug report on initscripts-7.06-3mdk)
On Fri, 2003-02-14 at 04:35, Buchan Milne wrote: > James Sparenberg wrote: > > On Fri, 2003-02-14 at 02:51, Buchan Milne wrote: > > > >>Probably a misconfigured samba and the fact that we start/stop smbd and > >>nmbd together. So, /etc/rc.d/init.d/smb stops smbd, tries to stop nmbd > >>and fails (was not running or had a name conflict or something like > >>that), and since both killprocs did not succeed, it does not remove the > >>lock file, so it is run again. > > > > > > this is the hard part. Since I'm in a shutdown situation how do I check > > to see if the lockfile is getting removed or not. > > What happens if you stop samba manually? Or if you init 1? Manually stopping samba works and the PID is removed. going to init 1 goes through the same procedure and shows the same results. Let me see if I can capture something this way. James > > > > >>I guess we should put a check in to see if nmbd and smbd are really > >>running, but it may be better to leave the error so the user knows they > >>have something to fix? > > > > > > This is the thing... what is the fix. Samba is working quite well so > > I'm pretty sure the config is good. (printing shares etc are solid.) I > > really don't do much more than use samba to print on a windows box at > > home. > > > > Weird ... will have to bounce a few machines to test, but I do not > remember seeing this ... > > Buchan
[Cooker] Re: solution to pcmcia network problems (was Re: [Cooker] Bug report on initscripts-7.06-3mdk)
On Friday 14 February 2003 07:35 am, Buchan Milne wrote: > James Sparenberg wrote: > > On Fri, 2003-02-14 at 02:51, Buchan Milne wrote: > >>Probably a misconfigured samba and the fact that we start/stop smbd and > >>nmbd together. So, /etc/rc.d/init.d/smb stops smbd, tries to stop nmbd > >>and fails (was not running or had a name conflict or something like > >>that), and since both killprocs did not succeed, it does not remove the > >>lock file, so it is run again. > > > > this is the hard part. Since I'm in a shutdown situation how do I check > > to see if the lockfile is getting removed or not. > > What happens if you stop samba manually? Or if you init 1? > > >>I guess we should put a check in to see if nmbd and smbd are really > >>running, but it may be better to leave the error so the user knows they > >>have something to fix? > > > > This is the thing... what is the fix. Samba is working quite well so > > I'm pretty sure the config is good. (printing shares etc are solid.) I > > really don't do much more than use samba to print on a windows box at > > home. > > Weird ... will have to bounce a few machines to test, but I do not > remember seeing this ... > > Buchan on one of the mail lists this was worked thru and I believe it had to do with the persistant mount point started by some other GUI like Gnomba or linneighborhood.
Re: [Cooker] Re: solution to pcmcia network problems (was Re:[Cooker] Bug report on initscripts-7.06-3mdk)
On Fri, 2003-02-14 at 04:42, et wrote: > On Friday 14 February 2003 07:35 am, Buchan Milne wrote: > > James Sparenberg wrote: > > > On Fri, 2003-02-14 at 02:51, Buchan Milne wrote: > > >>Probably a misconfigured samba and the fact that we start/stop smbd and > > >>nmbd together. So, /etc/rc.d/init.d/smb stops smbd, tries to stop nmbd > > >>and fails (was not running or had a name conflict or something like > > >>that), and since both killprocs did not succeed, it does not remove the > > >>lock file, so it is run again. > > > > > > this is the hard part. Since I'm in a shutdown situation how do I check > > > to see if the lockfile is getting removed or not. > > > > What happens if you stop samba manually? Or if you init 1? > > > > >>I guess we should put a check in to see if nmbd and smbd are really > > >>running, but it may be better to leave the error so the user knows they > > >>have something to fix? > > > > > > This is the thing... what is the fix. Samba is working quite well so > > > I'm pretty sure the config is good. (printing shares etc are solid.) I > > > really don't do much more than use samba to print on a windows box at > > > home. > > > > Weird ... will have to bounce a few machines to test, but I do not > > remember seeing this ... > > > > Buchan > on one of the mail lists this was worked thru and I believe it had to do with > the persistant mount point started by some other GUI like Gnomba or > linneighborhood. Not using either one of those but I'll look into it and see if I can find something. >
