Re: BOINC again !? -- BINGO, BINGO and BINGO
Matthew Saltzman wrote: But it seems to me that it should be easy enough to cater for all users, by having a setting in some /etc/NM.conf which will allow NM to start with a specific connection before anyone logs in _if that is what one wants_, or if not requires the user to authenticate before connection. http://fedoraproject.org/wiki/Bugs/F9Common#networkmanager-static I read this, and followed the instructions there as well as I could, creating the following /etc/sysconfig/network-scripts/ifcfg-eth1 -- DEVICE=eth1 ONBOOT=yes BOOTPROTO=dhcp NM_CONTROLLED=Yes HWADDR=00:02:2D:21:03:C9 IPADDR=192.168.2.19 NETWORK=192.168.2.0 GATEWAY=192.168.2.2 TYPE=Wireless DHCP_HOSTNAME=mary.gayleard.com IPV6INIT=no ESSID=dd-wrt KEY=secret -- But the effect of installing this was to stop NM working. (It had been working perfectly.) Actually, WiFi appeared to be working from the flashing lights on my WiFi card, but I got the message Network unavailable. In any case, as far as I could see NM (or nm-applet) did not start up until I logged in, as usual, so even if this had worked I don't think it would improved matters. As I said before, the fact that NM starts late does not actually worry me too much, I just find it puzzling. To date I have 4 files in /etc/NetworkManager/dispatcher.d/ to run various programs (eg NFS mount) which have to wait for a network connection. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Patrick O'Callaghan wrote: Occasionally I try to access the internet from a WiFi hotspot but my experience in Ireland is that this is rarely as simple as it sounds. (Last time I tried in a pub here it turned out that they wanted me to pay the equivalent of several pints of beer.) OT, but there used to be a place in Westmoreland St. Dublin that allowed you unlimited Wifi for the cost of a cup of coffee. We spent a whole afternoon there a couple of years ago. Unfortunately, they've gone out of business ... Completely OT, but the story of this cafe (Bewley's) was very sad. The owner (Vincent Bewley) was a quaker saint who gave all the shares in his very successful group of cafes to the staff (with shares distributed equally, I believe) ... This might have succeeded in heaven, but not on earth. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Fri, 2008-07-04 at 14:58 +0100, Timothy Murphy wrote: Matthew Saltzman wrote: But it seems to me that it should be easy enough to cater for all users, by having a setting in some /etc/NM.conf which will allow NM to start with a specific connection before anyone logs in _if that is what one wants_, or if not requires the user to authenticate before connection. http://fedoraproject.org/wiki/Bugs/F9Common#networkmanager-static I read this, and followed the instructions there as well as I could, creating the following /etc/sysconfig/network-scripts/ifcfg-eth1 -- DEVICE=eth1 ONBOOT=yes BOOTPROTO=dhcp NM_CONTROLLED=Yes HWADDR=00:02:2D:21:03:C9 IPADDR=192.168.2.19 NETWORK=192.168.2.0 GATEWAY=192.168.2.2 TYPE=Wireless DHCP_HOSTNAME=mary.gayleard.com IPV6INIT=no ESSID=dd-wrt KEY=secret -- But the effect of installing this was to stop NM working. (It had been working perfectly.) Actually, WiFi appeared to be working from the flashing lights on my WiFi card, but I got the message Network unavailable. In any case, as far as I could see NM (or nm-applet) did not start up until I logged in, as usual, so even if this had worked I don't think it would improved matters. First, I haven't actually tired this yet, as I haven't had time to install F9 on any of my machines. But I will have a chance sometime soon, maybe this weekend. nm-applet doesn't start until you log in, but NetworkManager starts at boot if it is set to do so. My understanding is that NM (the service) should start an interface at boot if ifcfg-device is set up correctly. It's likely that mobile users wouldn't want an interface to come up if it wasn't under their control (through nm-applet). As I said before, the fact that NM starts late does not actually worry me too much, I just find it puzzling. To date I have 4 files in /etc/NetworkManager/dispatcher.d/ to run various programs (eg NFS mount) which have to wait for a network connection. I think I've seen that the NM service will be set to start earlier in the boot sequence in a soon-to-be-released update. The longer-term solution would be to have services that require a network understand how to wait for one to come up (through dBus, for example). -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Matthew Saltzman wrote: But it seems to me that it should be easy enough to cater for all users, by having a setting in some /etc/NM.conf which will allow NM to start with a specific connection before anyone logs in _if that is what one wants_, or if not requires the user to authenticate before connection. http://fedoraproject.org/wiki/Bugs/F9Common#networkmanager-static I read this, and followed the instructions there as well as I could, First, I haven't actually tired this yet, as I haven't had time to install F9 on any of my machines. But I will have a chance sometime soon, maybe this weekend. I've tried it with various versions of ifcfg-eth1 . (It was suggested to me that giving an IPADDR when using dhcp might confuse NM.) In any case, my experience has been that as soon as I move ifcfg-eth1 to /etc/sysconfig/network-script/ , NM stops working, with the message You have been disconnected ... (So at least NM must be looking at this file. I'm pretty sure it didn't do that earlier in its life.) nm-applet doesn't start until you log in, but NetworkManager starts at boot if it is set to do so. My understanding is that NM (the service) should start an interface at boot if ifcfg-device is set up correctly. It's likely that mobile users wouldn't want an interface to come up if it wasn't under their control (through nm-applet). Depends what you mean by a mobile user. Personally, I would like NM to try to connect to the last ESSID it succeeded in connecting to, and if it can't connect then ask me which of the ESSIDs it sees I want to connect to. Just like Windows XP, in fact, which seems to me to have this about right. I think I've seen that the NM service will be set to start earlier in the boot sequence in a soon-to-be-released update. The longer-term solution would be to have services that require a network understand how to wait for one to come up (through dBus, for example). Actually, it is not too difficult to start them in /etc/NetworkManager/dispatcher.d/ . I just don't think it is a very rational arrangement. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Fri, 2008-07-04 at 12:33 -0400, Matthew Saltzman wrote: Since this subject is bout Boinc and solved, shouldn't another thread be started, at least about what your currently talking about so can be followed from archives a little easier? Otherwise, who would know to search for boinc when discussing NM stuff? LOL Sorry, not ranting on your discussion, I don't care, just bringing up a suggestion for future fedoraers haha (is that a word?) -- Mike Chambers Fedora Project - Ambassador, Bug Zapper, Tester, User, etc.. [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Fri, 2008-07-04 at 15:03 +0100, Timothy Murphy wrote: Patrick O'Callaghan wrote: Occasionally I try to access the internet from a WiFi hotspot but my experience in Ireland is that this is rarely as simple as it sounds. (Last time I tried in a pub here it turned out that they wanted me to pay the equivalent of several pints of beer.) OT, but there used to be a place in Westmoreland St. Dublin that allowed you unlimited Wifi for the cost of a cup of coffee. We spent a whole afternoon there a couple of years ago. Unfortunately, they've gone out of business ... Completely OT, but the story of this cafe (Bewley's) was very sad. The owner (Vincent Bewley) was a quaker saint who gave all the shares in his very successful group of cafes to the staff (with shares distributed equally, I believe) ... This might have succeeded in heaven, but not on earth. Bewley's actually was extremely successful for over 150 years until it closed in 2004. The Grafton St. branch has since reopened under new management but of course it's not the same. I think they still have the amazing stained-glass windows though. Anyway, the place I'm talking about wasn't Bewley's, or indeed even remotely in the same class. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Rahul Sundaram wrote: Sorry, Rahul, you have lost me here. When I say that NM waits until the user logs in I mean that NetworkManager does not connect me to my AP until I login. Again, you are confusing between NM and nm-applet. I don't think so. I am using the term NetworkManager - as I think most people do - to mean NM and any associated programs which it may start. Therefore any application that requires me to be connected has to wait until I login. This doesn't worry me particularly, but it does puzzle me. I am asking the reason for this delay. I believe I already answered that. NM was initially designed to manage wireless networks easily where it makes more sense to connect after you login. Refer http://www.redhat.com/magazine/003jan05/features/networkmanager/ Thanks for that reference, which looks pretty good at a quick first glance. I guess I start from a different point to yourself and the NM developer(s). I and my family use WiFi on laptops in my house, to connect to the desktop connected to the internet. Occasionally I try to access the internet from a WiFi hotspot but my experience in Ireland is that this is rarely as simple as it sounds. (Last time I tried in a pub here it turned out that they wanted me to pay the equivalent of several pints of beer.) But 99% of the time we are using laptops to connect to a fixed AP. In other words, for me WiFi is simply a replacement for ethernet. I suspect that is the case for a large majority of WiFi users. In fact, for people like me - which as I say I suspect is most users - the standard network service would be fine if it worked. It used to work reasonably well under Redhat-9 (and earlier) but it has never worked properly under Fedora, for me. But it seems to me that it should be easy enough to cater for all users, by having a setting in some /etc/NM.conf which will allow NM to start with a specific connection before anyone logs in _if that is what one wants_, or if not requires the user to authenticate before connection. Perhaps if there was some minimal documentation for NM this might be clear. Perhaps if you will volunteer to contribute, it would have been done by now. If you want to wait for someone else to do the work, it is going to be done when others find time and interest to do it. It would be very foolish for me to try to document NM. I recall with horror a HOWTO written by Karl you-know-who which was guaranteed to sow utter confusion in any reader. But it always surprises me that a developer who must have spent weeks if not months thinking about his pet project has never found it useful for him/her-self if no-one else to set down the basic principles of the project. I often think one of the advantages of democracy is that when politicians and bureaucrats are forced to document what they are doing they usually find that this increases their own understanding, and so improves their performance. Actually, the document you pointed to seems to me a pretty good starting point. But the question it does not answer, and which it is obvious many users would like an answer to, is: What can I do if NetworkManager does not connect me to my AP? How can I tell where it has broken down? And what steps can I take to solve the problem? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Thu, 2008-07-03 at 16:40 +0100, Timothy Murphy wrote: Occasionally I try to access the internet from a WiFi hotspot but my experience in Ireland is that this is rarely as simple as it sounds. (Last time I tried in a pub here it turned out that they wanted me to pay the equivalent of several pints of beer.) OT, but there used to be a place in Westmoreland St. Dublin that allowed you unlimited Wifi for the cost of a cup of coffee. We spent a whole afternoon there a couple of years ago. Unfortunately, they've gone out of business ... poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Thu, 2008-07-03 at 16:40 +0100, Timothy Murphy wrote: Rahul Sundaram wrote: Sorry, Rahul, you have lost me here. When I say that NM waits until the user logs in I mean that NetworkManager does not connect me to my AP until I login. Again, you are confusing between NM and nm-applet. I don't think so. I am using the term NetworkManager - as I think most people do - to mean NM and any associated programs which it may start. Therefore any application that requires me to be connected has to wait until I login. This doesn't worry me particularly, but it does puzzle me. I am asking the reason for this delay. I believe I already answered that. NM was initially designed to manage wireless networks easily where it makes more sense to connect after you login. Refer http://www.redhat.com/magazine/003jan05/features/networkmanager/ Thanks for that reference, which looks pretty good at a quick first glance. I guess I start from a different point to yourself and the NM developer(s). I and my family use WiFi on laptops in my house, to connect to the desktop connected to the internet. Occasionally I try to access the internet from a WiFi hotspot but my experience in Ireland is that this is rarely as simple as it sounds. (Last time I tried in a pub here it turned out that they wanted me to pay the equivalent of several pints of beer.) But 99% of the time we are using laptops to connect to a fixed AP. In other words, for me WiFi is simply a replacement for ethernet. I suspect that is the case for a large majority of WiFi users. In fact, for people like me - which as I say I suspect is most users - the standard network service would be fine if it worked. It used to work reasonably well under Redhat-9 (and earlier) but it has never worked properly under Fedora, for me. But it seems to me that it should be easy enough to cater for all users, by having a setting in some /etc/NM.conf which will allow NM to start with a specific connection before anyone logs in _if that is what one wants_, or if not requires the user to authenticate before connection. http://fedoraproject.org/wiki/Bugs/F9Common#networkmanager-static Perhaps if there was some minimal documentation for NM this might be clear. Perhaps if you will volunteer to contribute, it would have been done by now. If you want to wait for someone else to do the work, it is going to be done when others find time and interest to do it. It would be very foolish for me to try to document NM. I recall with horror a HOWTO written by Karl you-know-who which was guaranteed to sow utter confusion in any reader. But it always surprises me that a developer who must have spent weeks if not months thinking about his pet project has never found it useful for him/her-self if no-one else to set down the basic principles of the project. I often think one of the advantages of democracy is that when politicians and bureaucrats are forced to document what they are doing they usually find that this increases their own understanding, and so improves their performance. Actually, the document you pointed to seems to me a pretty good starting point. But the question it does not answer, and which it is obvious many users would like an answer to, is: What can I do if NetworkManager does not connect me to my AP? How can I tell where it has broken down? And what steps can I take to solve the problem? -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- LAST POST
On Sat, 2008-06-28 at 19:57 -0700, Craig White wrote: On Sat, 2008-06-28 at 22:52 -0400, William Case wrote: [SNIP] report it just like you did above...if the packager has questions, he'll ask but I would suggest that you file it against NetworkManager package. It's important to work out all of the issues with NetworkManager to solve them once and for all. Craig I reported it as a bug. Just got the following reply: https://bugzilla.redhat.com/show_bug.cgi?id=453317 Boinc is probably starting so soon after NetworkManager that the network is not up yet. It's technically a bug in Boinc that it doesn't wait for a network connection and periodically re-try to send/grab the data. But for the moment, you can add the line: NETWORKWAIT=yes to /etc/sysconfig/network and startup will block for 10 seconds or until a network connection is up, whichever is sooner. I added the suggested line, because it probably covers all instances of shutdowns, crashes etc. whereas the rc.local solution only works with a normal clean startup. Thanks all. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Andrew Kelly wrote: There is also a large amount of work that needs to be done on fixing software that doesn't react well to network connections disappearing underneath them as happens often with wireless networks on laptops and mobile systems. Rahul As much as I am not a fan of NetworkManager, I think I have to give that post an A'men. 'Specially that last sentence. NM is a worthy target for criticism, but it shouldn't be a punching boy for other applications weaknesses. But this was a specific, concrete query. Why does NM wait until the user has logged in to start? I don't think you can blame other applications for problems this causes. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
Mike Evans wrote: For machines with a wired connection I have been in the habit of disabling NM and using the good old network service. Works like a dream and doesn't need tampering with. You can do that through the Admin-services gui if you don't like fiddling with the links in the init directories. But most people nowadays use a WiFi connection, at least on laptops, so the advice to use the good old network service is not much help. as the network service is much, much worse than NM with WiFi in my experience. Both are completely undocumented, so one is in the world of magic. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Timothy Murphy wrote: But this was a specific, concrete query. Why does NM wait until the user has logged in to start? That's a wrong assumption. NM doesn't wait until the user has started. It is a system service which starts at boot. nm-applet(GNOME) or Knetworkmanager (KDE) is just a frontend to the system service called NM. It is possible to write a console frontend to do a similar task for the non-desktop case but NM atleast initially was designed to make wireless network access easier. It has grown additional functionality over time however. Rahul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Rahul Sundaram wrote: But this was a specific, concrete query. Why does NM wait until the user has logged in to start? That's a wrong assumption. NM doesn't wait until the user has started. It is a system service which starts at boot. nm-applet(GNOME) or Knetworkmanager (KDE) is just a frontend to the system service called NM. It is possible to write a console frontend to do a similar task for the non-desktop case but NM atleast initially was designed to make wireless network access easier. It has grown additional functionality over time however. Sorry, Rahul, you have lost me here. When I say that NM waits until the user logs in I mean that NetworkManager does not connect me to my AP until I login. Therefore any application that requires me to be connected has to wait until I login. This doesn't worry me particularly, but it does puzzle me. I am asking the reason for this delay. Perhaps if there was some minimal documentation for NM this might be clear. The standard network service, on the rare occasions when it works for me, does not wait for me to login. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Timothy Murphy wrote: Sorry, Rahul, you have lost me here. When I say that NM waits until the user logs in I mean that NetworkManager does not connect me to my AP until I login. Again, you are confusing between NM and nm-applet. Therefore any application that requires me to be connected has to wait until I login. This doesn't worry me particularly, but it does puzzle me. I am asking the reason for this delay. I believe I already answered that. NM was initially designed to manage wireless networks easily where it makes more sense to connect after you login. Refer http://www.redhat.com/magazine/003jan05/features/networkmanager/ Perhaps if there was some minimal documentation for NM this might be clear. Perhaps if you will volunteer to contribute, it would have been done by now. If you want to wait for someone else to do the work, it is going to be done when others find time and interest to do it. Rahul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Wed, 2008-07-02 at 16:30 +0100, Timothy Murphy wrote: Rahul Sundaram wrote: But this was a specific, concrete query. Why does NM wait until the user has logged in to start? That's a wrong assumption. NM doesn't wait until the user has started. It is a system service which starts at boot. nm-applet(GNOME) or Knetworkmanager (KDE) is just a frontend to the system service called NM. It is possible to write a console frontend to do a similar task for the non-desktop case but NM atleast initially was designed to make wireless network access easier. It has grown additional functionality over time however. Sorry, Rahul, you have lost me here. When I say that NM waits until the user logs in I mean that NetworkManager does not connect me to my AP until I login. Therefore any application that requires me to be connected has to wait until I login. This doesn't worry me particularly, but it does puzzle me. I am asking the reason for this delay. Perhaps if there was some minimal documentation for NM this might be clear. The standard network service, on the rare occasions when it works for me, does not wait for me to login. Think about how accessing wireless systems works. If you have to authenticate, then you have to be logged in to do it (or you have to preconfigure it). If you are a mobile user, you may have to do it several times--NM makes the process about as convenient as possible. Authentication should be tied to a user: user A should not necessarily be able to authenticate to user B's WAP unless user A also knows the key. (Apropos another thread, that's why the keyring is used to store encrypted keys.) NM was originally designed primarily for mobile machines that may connect to many different networks or no network, so management by a logged-in user is a reasonable assumption. The F9 NM supposedly also has the ability to set system-level access parameters (including static IPs) and connect at boot, but that mostly makes sense for workstations and servers. (I'm still running F8, so I haven't figured out how to do it yet.) -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Wed, 2008-07-02 at 11:09 -0400, Matthew Saltzman wrote: Think about how accessing wireless systems works. If you have to authenticate, then you have to be logged in to do it (or you have to preconfigure it). If you are a mobile user, you may have to do it several times--NM makes the process about as convenient as possible. Authentication should be tied to a user: user A should not necessarily be able to authenticate to user B's WAP unless user A also knows the key. (Apropos another thread, that's why the keyring is used to store encrypted keys.) This actually raises an interesting point. The various discussions of wireless authentication I've seen don't clearly distinguish between the user and the device in all cases. Sometimes they do (e.g. when using WPA in an enterprise mode which requires authenticating the actual user to a central server) and other times they don't (such as the very common PSK mode where everyone just knows the magic passphrase). What happens in the following scenario: User A logs in to his laptop and authenticates. Without logging out, User B comes along and logs in as well (on a different virtual console). Can User B now access the network without needing to authenticate again? If so, NM is treating the authentication as per-device, if not, then it's per-user. Does it depend on the WPA mode? I don't know. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Wed, 2008-07-02 at 14:15 -0430, Patrick O'Callaghan wrote: On Wed, 2008-07-02 at 11:09 -0400, Matthew Saltzman wrote: Think about how accessing wireless systems works. If you have to authenticate, then you have to be logged in to do it (or you have to preconfigure it). If you are a mobile user, you may have to do it several times--NM makes the process about as convenient as possible. Authentication should be tied to a user: user A should not necessarily be able to authenticate to user B's WAP unless user A also knows the key. (Apropos another thread, that's why the keyring is used to store encrypted keys.) This actually raises an interesting point. The various discussions of wireless authentication I've seen don't clearly distinguish between the user and the device in all cases. Sometimes they do (e.g. when using WPA in an enterprise mode which requires authenticating the actual user to a central server) and other times they don't (such as the very common PSK mode where everyone just knows the magic passphrase). What happens in the following scenario: User A logs in to his laptop and authenticates. Without logging out, User B comes along and logs in as well (on a different virtual console). Can User B now access the network without needing to authenticate again? If so, NM is treating the authentication as per-device, if not, then it's per-user. Does it depend on the WPA mode? I don't know. Ooh, good point. The answer is, once the link is up, it's tied to the device. I think you can even log out of your session and into another without taking the link down (but I haven't tried that). I'll leave it to Dan Williams (NM developer) to address possible alternative architectures. poc -- Matthew Saltzman Clemson University Math Sciences mjs AT clemson DOT edu http://www.math.clemson.edu/~mjs -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Timothy Murphy: Perhaps if there was some minimal documentation for NM this might be clear. Rahul Sundaram: Perhaps if you will volunteer to contribute, it would have been done by now. If you want to wait for someone else to do the work, it is going to be done when others find time and interest to do it. How could anybody without the needed information write documentation for it? And trying to figure out documentation by reading the source code, apart from being a difficult task, is only going to sensible if the authors don't change what the program does. Program authors have to write the documentation. Anybody else doing it will just be documenting guesswork. -- [EMAIL PROTECTED] ~]$ uname -r 2.6.25.6-55.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Tom Horsley wrote: I don't think any problems in NetworkManager will ever be considered bugs until RedHat foists it on their paying RHEL customers There is a little problem with that theory. Both Red Hat and upstream bugzilla shows a considerable amount of bugs being filed and fixed on a regular basis and RHEL 5 already includes NetworkManager as a fully supported component. There is also a large amount of work that needs to be done on fixing software that doesn't react well to network connections disappearing underneath them as happens often with wireless networks on laptops and mobile systems. Rahul -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !?
On Fri, 2008-06-27 at 22:52 -0700, Craig White wrote: [big snip] yum install mod_ssl service httpd restart Port 443 now appears in netstat. Thanks. Boinc still not working -- but that is an application problem to be figured out in the morning. seems hard to believe that mod_ssl wasn't already installed. What packages are required by boinc? Are they installed? Sounds like you built it from source and not from rpm packaging. Had it working fine in Fedora 8 when it was an rpm install from the Boinc site. If you are wondering; it is a distributed computing program working on cancer, dengue fever cures etc. This time it was packaged in the Fedora 9 repo site. I downloaded and installed it with yum (yumex). Thanks Craig. I actually learned a lot about a subject(s) I had been putting off too long. I appreciate your help. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !?
Craig White kirjoitti viestissään (lähetysaika lauantai, 28. kesäkuuta 2008): don't know anything about BOINC but do you have/need httpd running (sounds like it) You don't need httpd to run the BOINC client. It doesn't need any incoming firewall ports open either. I think this thread got sidetracked somewhere, I don't believe the OP wants to run a BOINC project server. -- Markku Kolkka [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !?
On Fri, 2008-06-27 at 23:22 -0400, William Case wrote: On Fri, 2008-06-27 at 21:19 -0400, John Munn wrote: You need to open the ports in your firewall (iptables). Didn't have iptables running. I do now with ports 80 and 443 set as trusted -- still nothing. Do I have to move or link some file(s) from /var/lib/boinc to $HOME? don't know anything about BOINC but do you have/need httpd running (sounds like it) /sbin/service httpd status /sbin/service httpd start Boinc does not require httpd to be running on the local system. -- Mike Burger http://www.bubbanfriends.org Visit the Dog Pound II BBS telnet://dogpound2.citadel.org or http://dogpound2.citadel.org To be notified of updates to the web site, visit: https://www.bubbanfriends.org/mailman/listinfo/site-update or send a blank email message to: [EMAIL PROTECTED] -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !?
Hi Markku; On Sat, 2008-06-28 at 12:37 +0300, Markku Kolkka wrote: Craig White kirjoitti viestissään (lähetysaika lauantai, 28. kesäkuuta 2008): don't know anything about BOINC but do you have/need httpd running (sounds like it) You don't need httpd to run the BOINC client. It doesn't need any incoming firewall ports open either. I think this thread got sidetracked somewhere, I don't believe the OP wants to run a BOINC project server. You are right. I don't want to run a server. I just want to get the boinc applications (boinc-clent and boincmgr) that I downloaded (yumed) from the Fedora 9 repo up and running. And, I want to keep it running after I re-boot. My problem is I keep getting this error message from bonicmgr: BOINC is unable to communicate with a project and needs an Internet connection. Please connect to the Internet, then select the 'retry communications' item off the advanced menu. I am connected to the internet. I have selected the 'retry communications item off the advanced menu. I always get: Sat 28 Jun 2008 09:39:50 AM EDT|World Community Grid|Sending scheduler request: Requested by user. Requesting 2 seconds of work, reporting 0 completed tasks and Sat 28 Jun 2008 09:39:55 AM EDT|World Community Grid| Scheduler request failed: Couldn't resolve host name I never had this problem when I installed in F8 from the boinc site rpm. Boinc works in F9 immediately after a new install. By the way, time wasn't wasted last night. I did delve into learning about matters I should have dealt with before. But... Any suggestions on how I get my boinc working. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !?
On Sat, Jun 28, 2008 at 7:50 AM, William Case [EMAIL PROTECTED] wrote: But... Any suggestions on how I get my boinc working. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 Greetings William, I have used the following site to get my boinc going: http://www.gaztronics.net/rc/boinc.php Hope this helps -- Virtually, Tom Weniger Registered Linux user #243493 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
Hi; I give up. I am filing a bug. On Sat, 2008-06-28 at 09:48 -0600, Tom Weniger wrote: On Sat, Jun 28, 2008 at 7:50 AM, William Case [EMAIL PROTECTED] wrote: But... Any suggestions on how I get my boinc working. -- Greetings William, I have used the following site to get my boinc going: http://www.gaztronics.net/rc/boinc.php Hope this helps I have followed all of the advice given here. I greatly appreciate everyone's effort to help. However, I still have the original problem. When I yum erase boinc-client and boincmgr and start over with a fresh yum install -- boinc works. It is finding all my projects and running them successfully. Boincmgr reports accurately what boinc is doing and responds to my commands. It is now running in the background. If I where to shutdown my computer and restart, boinc won't restart even though service boinc is running. I can't be more definite than that because I don't have a clue what the problem is. I am not a complete beginner, and no package should be this difficult (two days now) to analyze and get running. The only solution is to file a Fedora bug on boinc and put up with being seared at by the packagers and maintainers. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sat, 2008-06-28 at 14:30 -0400, William Case wrote: Hi; I give up. I am filing a bug. On Sat, 2008-06-28 at 09:48 -0600, Tom Weniger wrote: On Sat, Jun 28, 2008 at 7:50 AM, William Case [EMAIL PROTECTED] wrote: But... Any suggestions on how I get my boinc working. -- Greetings William, I have used the following site to get my boinc going: http://www.gaztronics.net/rc/boinc.php Hope this helps I have followed all of the advice given here. I greatly appreciate everyone's effort to help. However, I still have the original problem. When I yum erase boinc-client and boincmgr and start over with a fresh yum install -- boinc works. It is finding all my projects and running them successfully. Boincmgr reports accurately what boinc is doing and responds to my commands. It is now running in the background. If I where to shutdown my computer and restart, boinc won't restart even though service boinc is running. I can't be more definite than that because I don't have a clue what the problem is. I am not a complete beginner, and no package should be this difficult (two days now) to analyze and get running. The only solution is to file a Fedora bug on boinc and put up with being seared at by the packagers and maintainers. I believe that what Patrick was trying to tell you is that if you are using NetworkManager, then it's entirely possible that networking isn't fully operational when boinc service starts at bootup which would cause it to fail. That can probably be verified by merely issuing '/sbin/service boinc restart' (assuming that restart is an option for the boinc sysv script). If that works, then it might just be easier to put that command in /etc/rc.d/rc.local (/sbin/service boinc restart) Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sat, 2008-06-28 at 12:51 -0700, Craig White wrote: On Sat, 2008-06-28 at 14:30 -0400, William Case wrote: Hi; I give up. I am filing a bug. On Sat, 2008-06-28 at 09:48 -0600, Tom Weniger wrote: On Sat, Jun 28, 2008 at 7:50 AM, William Case [EMAIL PROTECTED] wrote: But... Any suggestions on how I get my boinc working. -- Greetings William, I have used the following site to get my boinc going: http://www.gaztronics.net/rc/boinc.php Hope this helps I have followed all of the advice given here. I greatly appreciate everyone's effort to help. However, I still have the original problem. When I yum erase boinc-client and boincmgr and start over with a fresh yum install -- boinc works. It is finding all my projects and running them successfully. Boincmgr reports accurately what boinc is doing and responds to my commands. It is now running in the background. If I where to shutdown my computer and restart, boinc won't restart even though service boinc is running. I can't be more definite than that because I don't have a clue what the problem is. I am not a complete beginner, and no package should be this difficult (two days now) to analyze and get running. The only solution is to file a Fedora bug on boinc and put up with being seared at by the packagers and maintainers. I believe that what Patrick was trying to tell you is that if you are using NetworkManager, then it's entirely possible that networking isn't fully operational when boinc service starts at bootup which would cause it to fail. That can probably be verified by merely issuing '/sbin/service boinc restart' (assuming that restart is an option for the boinc sysv script). If that works, then it might just be easier to put that command in /etc/rc.d/rc.local (/sbin/service boinc restart) Exactly. poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
Hi Craig; On Sat, 2008-06-28 at 12:51 -0700, Craig White wrote: On Sat, 2008-06-28 at 14:30 -0400, William Case wrote: Hi; I give up. I am filing a bug. On Sat, 2008-06-28 at 09:48 -0600, Tom Weniger wrote: On Sat, Jun 28, 2008 at 7:50 AM, William Case [EMAIL PROTECTED] wrote: But... Any suggestions on how I get my boinc working. -- I believe that what Patrick was trying to tell you is that if you are using NetworkManager, then it's entirely possible that networking isn't fully operational when boinc service starts at bootup which would cause it to fail. That can probably be verified by merely issuing '/sbin/service boinc restart' (assuming that restart is an option for the boinc sysv script). If that works, then it might just be easier to put that command in /etc/rc.d/rc.local (/sbin/service boinc restart) Craig Yes, I am using NetworkManager. I have tried one last test. I removed and re-installed boinc. With that, boinc was able to connect to WCG and download 2 more work units. Boinc has only been able to connect to WCG to get work units on a new install -- never after a re-boot. Boinc is processing those work units now. I have since shut down my computer and rebooted. Since the work units are on my machine, my computer is continuing to process those units. It will take approximately 6 hrs to finish processing them. I am waiting to see if then it can automagically re-connect to WCG and obtain further work units. If it can't I will try Patrick's Network Manager solution. If that works, I then have to decide whether this is a Network Manager bug; a Boinc bug; or both. Of course, if boincmgr does successfully reconnect to WCG and download additional work units, I will write the whole thing off as my screwing around too much while Boinc was just trying to do its thing. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up. --correction
[snip] If that works, I then have to decide whether this is a Network Manager bug; a Boinc bug; or both. Of course, if boincmgr does successfully bug; a Boinc bug; or both. Of course, if boinc-clent does successfully reconnect to WCG and download additional work units, I will write the whole thing off as my screwing around too much while Boinc was just trying to do its thing. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sat, 2008-06-28 at 16:19 -0400, William Case wrote: If it can't I will try Patrick's Network Manager solution. If that works, I then have to decide whether this is a Network Manager bug; a Boinc bug; or both. Of course, if boincmgr does successfully reconnect to WCG and download additional work units, I will write the whole thing off as my screwing around too much while Boinc was just trying to do its thing. service boinc restart a relatively simple fix. If you were to file a bug report, I would file it against NetworkManager as this would mean that boinc works when networking is fully functional. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sun, 2008-06-29 at 06:48 +0800, Ed Greshko wrote: Craig White wrote: On Sat, 2008-06-28 at 16:19 -0400, William Case wrote: If it can't I will try Patrick's Network Manager solution. If that works, I then have to decide whether this is a Network Manager bug; a Boinc bug; or both. Of course, if boincmgr does successfully reconnect to WCG and download additional work units, I will write the whole thing off as my screwing around too much while Boinc was just trying to do its thing. service boinc restart a relatively simple fix. If you were to file a bug report, I would file it against NetworkManager as this would mean that boinc works when networking is fully functional. If the analysis of NM starting too late in the boot process is correct, wouldn't one of these make life a bit more tolerable? Keeping in mind that I don't use F9, NM, or BOINC. :-) 1. Change the script number in /etc/init.d of NM to a lower number than BOINC or change BOINC number to one higher than NM. 2.Do not configure BOINC to start a boot time in the usual manner but add a server boinc start to rc.local. I too don't use NM or BOINC but I do use F9 On F8, this clearly was a problem... # grep chkconfig /etc/init.d/NetworkManager # chkconfig: - 98 02 but on F9, I would have thought that this would have solved some of these issues... # grep chkconfig /etc/init.d/NetworkManager # chkconfig: - 27 84 which would have it start up much earlier (of course if this was an upgrade instead of clean install, I don't know if the sequences are adjusted when the upgrade is accomplished). I don't have BOINC installed but I have to believe that the startup sequence number would already have it loading after NM. I would think that moving it up from 98 to 27 would have solved many of the reported issues but perhaps not...I just don't know and as you say, I don't personally use NM. My own personal preference would be to leave NM enabled at boot time and put '/sbin/server boinc restart' in rc.local only because sometimes I look at boot time services and would want to know that the 'intent' was to start it up. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
Hi Patrick and Craig; Thanks a million, I would and thousands of others would never have guessed NetworkManager was BOINC's problem in a thousand years. On Sat, 2008-06-28 at 12:51 -0700, Craig White wrote: On Sat, 2008-06-28 at 14:30 -0400, William Case wrote: I believe that what Patrick was trying to tell you is that if you are using NetworkManager, then it's entirely possible that networking isn't fully operational when boinc service starts at bootup which would cause it to fail. That can probably be verified by merely issuing '/sbin/service boinc restart' (assuming that restart is an option for the boinc sysv script). If that works, then it might just be easier to put that command in /etc/rc.d/rc.local (/sbin/service boinc restart) Craig As I said, after re-installing Boinc and then re-booting, I ran a new set of the work units to the end. No new units would download. boincmgr complained about a lack of a connection -- BINGO. I re-booted just to see. No joy -- BINGO I then added '/sbin/service boinc-client restart' to /etc/rc.d/rc.local and re-booted once again. --BINGO Everything was up and running. New work units were down loaded automatically and boinc is happily processing away as I write. N.B. For anyone following this saga and has a similar problem notice one correction. The line is '/sbin/service boinc-client restart', not '/sbin/service boinc restart'. Re: Bug reporting. I think this bug is worth reporting, although you probably know better which details to report regarding NetworkManager. Some poor unlucky shmuck could get caught from 2 days to a week trying to figure out what was wrong. Once again, thanks very much to both of you, and the others that tried to give me a hand. -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Sat, 2008-06-28 at 22:52 -0400, William Case wrote: Hi Patrick and Craig; Thanks a million, I would and thousands of others would never have guessed NetworkManager was BOINC's problem in a thousand years. On Sat, 2008-06-28 at 12:51 -0700, Craig White wrote: On Sat, 2008-06-28 at 14:30 -0400, William Case wrote: I believe that what Patrick was trying to tell you is that if you are using NetworkManager, then it's entirely possible that networking isn't fully operational when boinc service starts at bootup which would cause it to fail. That can probably be verified by merely issuing '/sbin/service boinc restart' (assuming that restart is an option for the boinc sysv script). If that works, then it might just be easier to put that command in /etc/rc.d/rc.local (/sbin/service boinc restart) Craig As I said, after re-installing Boinc and then re-booting, I ran a new set of the work units to the end. No new units would download. boincmgr complained about a lack of a connection -- BINGO. I re-booted just to see. No joy -- BINGO I then added '/sbin/service boinc-client restart' to /etc/rc.d/rc.local and re-booted once again. --BINGO Everything was up and running. New work units were down loaded automatically and boinc is happily processing away as I write. N.B. For anyone following this saga and has a similar problem notice one correction. The line is '/sbin/service boinc-client restart', not '/sbin/service boinc restart'. Re: Bug reporting. I think this bug is worth reporting, although you probably know better which details to report regarding NetworkManager. Some poor unlucky shmuck could get caught from 2 days to a week trying to figure out what was wrong. Once again, thanks very much to both of you, and the others that tried to give me a hand. report it just like you did above...if the packager has questions, he'll ask but I would suggest that you file it against NetworkManager package. It's important to work out all of the issues with NetworkManager to solve them once and for all. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Sat, 2008-06-28 at 22:52 -0400, William Case wrote: Thanks a million, I would and thousands of others would never have guessed NetworkManager was BOINC's problem in a thousand years. Lucky guesses sometimes work out :-) poc -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sun, 2008-06-29 at 06:48 +0800, Ed Greshko wrote: If the analysis of NM starting too late in the boot process is correct, wouldn't one of these make life a bit more tolerable? Keeping in mind that I don't use F9, NM, or BOINC. :-) 1. Change the script number in /etc/init.d of NM to a lower number than BOINC or change BOINC number to one higher than NM. While I don't use BOINC, I've had had similar issues with other programs, and moving network manager's start up position has helped with some, but not with others. Moving those other things start up position further back has helped with a few more, but not all. I have two concerns with doing that sort of thing: I shouldn't have to do so much mangling to get things to work that are expected to work in their current configuration. And I might have to keep on fiddling around if updates undo my mangling. 2.Do not configure BOINC to start a boot time in the usual manner but add a server boinc start to rc.local. I've had to do something similar. It strikes me that something is *really* broken with Network Manager. Other services wait until they start before returning to the next item in the startup sequence. Network Manager seems to be returning as ready, before it is, and buggering up other things that follow. -- [EMAIL PROTECTED] ~]$ uname -r 2.6.25.6-55.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- BINGO, BINGO and BINGO
On Sat, 2008-06-28 at 22:52 -0400, William Case wrote: I then added '/sbin/service boinc-client restart' to /etc/rc.d/rc.local and re-booted once again. --BINGO Seeing as the problem's with Network Manager, I'd move the restart script away from the rc.local file to the scripts that Network Manager runs. That way, if your network breaks then restarts (internet dropouts, etc.), the service will restart. Look inside /etc/NetworkManager/dispatcher.d/ for examples. -- [EMAIL PROTECTED] ~]$ uname -r 2.6.25.6-55.fc9.i686 Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists. -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !? -- I give up.
On Sun, 2008-06-29 at 14:10 +0930, Tim wrote: It strikes me that something is *really* broken with Network Manager. Other services wait until they start before returning to the next item in the startup sequence. Network Manager seems to be returning as ready, before it is, and buggering up other things that follow. I think that they've been intensely focused on quick startup from boot times. Damn the torpedoes...full speed ahead. That's why it's so important to bugzilla these things. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !?
You need to open the ports in your firewall (iptables). John William Case wrote: Hi; I am having newbie problems with boinc, ports and SELinux -- I think. Networks and SELinux are two subjects I have put off learning to any rudimentary depth. So here goes. I can get Boinc to connect to the World Community Grid immediately after first download and install. (I have removed it and re-installed to test this). But after a reboot I can no longer connect to any of the project sites. I went to the WCG forum and explained my problem. The response was -- open ports 80 and 443. 'netstat' does not list 80 or 443 as present, i.e, as active. SELinux is in permissible mode. SELinux gives the following for those two ports. http_port_t tcp s0 80 http_port_t tcp s0 443 So ... where do I go from here? -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !?
On Fri, 2008-06-27 at 21:19 -0400, John Munn wrote: You need to open the ports in your firewall (iptables). Didn't have iptables running. I do now with ports 80 and 443 set as trusted -- still nothing. Do I have to move or link some file(s) from /var/lib/boinc to $HOME? John William Case wrote: Hi; I am having newbie problems with boinc, ports and SELinux -- I think. Networks and SELinux are two subjects I have put off learning to any rudimentary depth. So here goes. I can get Boinc to connect to the World Community Grid immediately after first download and install. (I have removed it and re-installed to test this). But after a reboot I can no longer connect to any of the project sites. I went to the WCG forum and explained my problem. The response was -- open ports 80 and 443. 'netstat' does not list 80 or 443 as present, i.e, as active. SELinux is in permissible mode. SELinux gives the following for those two ports. http_port_t tcp s0 80 http_port_t tcp s0 443 So ... where do I go from here? -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !?
Hi Craig; On Fri, 2008-06-27 at 21:54 -0700, Craig White wrote: On Sat, 2008-06-28 at 00:44 -0400, William Case wrote: Hi Craig; On Fri, 2008-06-27 at 20:55 -0700, Craig White wrote: On Fri, 2008-06-27 at 23:22 -0400, William Case wrote: On Fri, 2008-06-27 at 21:19 -0400, John Munn wrote: You need to open the ports in your firewall (iptables). Didn't have iptables running. I do now with ports 80 and 443 set as trusted -- still nothing. Do I have to move or link some file(s) from /var/lib/boinc to $HOME? don't know anything about BOINC but do you have/need httpd running (sounds like it) /sbin/service httpd status /sbin/service httpd start Half-way there. Now port 80 is showing on netstat but not 443. Never thought to check httpd service. Every new install before Fedora 9 automagically set httpd as a default service. That is not a complaint -- just a weak wristed excuse. httpd should start both 80 443 and thus should show a Listener on both ports in netstat... # netstat -an|grep 443 tcp0 0 :::443 :::* LISTEN Nope. Still not there. check /var/log/httpd/error_log /httpd/error_log [Sat Jun 28 00:29:16 2008] [notice] SELinux policy enabled; httpd running as context unconfined_u:system_r:httpd_t:s0 [Sat Jun 28 00:29:16 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Sat Jun 28 00:29:16 2008] [notice] Digest: generating secret for digest authentication ... [Sat Jun 28 00:29:16 2008] [notice] Digest: done [Sat Jun 28 00:29:16 2008] [notice] Apache/2.2.8 (Unix) DAV/2 configured -- resuming normal operations It is still a bit Greek to me; but seems to be alright. and /var/log/httpd/ssl_error_log for clues about problems. I have no httpd/ssl_error_log chkconfig httpd on will make sure that httpd always starts up when you restart Shttpd was already set for all 4 runlevels -- Regards Bill; Fedora 9, Gnome 2.22.2 Evo.2.22.2, Emacs 22.2.1 -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Re: BOINC again !?
On Sat, 2008-06-28 at 01:45 -0400, William Case wrote: Hi Craig; On Fri, 2008-06-27 at 21:54 -0700, Craig White wrote: On Sat, 2008-06-28 at 00:44 -0400, William Case wrote: Hi Craig; On Fri, 2008-06-27 at 20:55 -0700, Craig White wrote: On Fri, 2008-06-27 at 23:22 -0400, William Case wrote: On Fri, 2008-06-27 at 21:19 -0400, John Munn wrote: You need to open the ports in your firewall (iptables). Didn't have iptables running. I do now with ports 80 and 443 set as trusted -- still nothing. Do I have to move or link some file(s) from /var/lib/boinc to $HOME? don't know anything about BOINC but do you have/need httpd running (sounds like it) /sbin/service httpd status /sbin/service httpd start Half-way there. Now port 80 is showing on netstat but not 443. Never thought to check httpd service. Every new install before Fedora 9 automagically set httpd as a default service. That is not a complaint -- just a weak wristed excuse. httpd should start both 80 443 and thus should show a Listener on both ports in netstat... # netstat -an|grep 443 tcp0 0 :::443 :::* LISTEN Nope. Still not there. check /var/log/httpd/error_log /httpd/error_log [Sat Jun 28 00:29:16 2008] [notice] SELinux policy enabled; httpd running as context unconfined_u:system_r:httpd_t:s0 [Sat Jun 28 00:29:16 2008] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec) [Sat Jun 28 00:29:16 2008] [notice] Digest: generating secret for digest authentication ... [Sat Jun 28 00:29:16 2008] [notice] Digest: done [Sat Jun 28 00:29:16 2008] [notice] Apache/2.2.8 (Unix) DAV/2 configured -- resuming normal operations It is still a bit Greek to me; but seems to be alright. and /var/log/httpd/ssl_error_log for clues about problems. I have no httpd/ssl_error_log chkconfig httpd on will make sure that httpd always starts up when you restart Shttpd was already set for all 4 runlevels yum install mod_ssl service httpd restart seems hard to believe that mod_ssl wasn't already installed. What packages are required by boinc? Are they installed? Sounds like you built it from source and not from rpm packaging. Craig -- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
