Announcement

Collapse
No announcement yet.

Red Hat Talks Up debuginfod As The New Debug Info Web Server

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #11
    Originally posted by kloczek View Post
    There are many private networks which are not even physcaly connected to the public network.
    If they will stop provide debuginfo packages it will be yet another reason to move away from RH.

    And do not mention that OS like Solaris does not need any dist debuinfo resources to diagnose issues to the level allowing support to figure out what is wrong.
    kloczek Is that was dtrace does? Are there no debuginfo packages on Solaris?

    Comment


    • #12
      Originally posted by RahulSundaram View Post
      Yes, you already said that. What is your point?
      His point is that there's no way to run a proxy on a network that has not interaction at all with the outside (as opposed to network that ARE connected to the outside through a proxy). In some premices, there is NO internet end-point to which the proxy could connect and be proxying to the closed internal network.

      On the other hand, as others have pointed out, it is possible to run a debuginfod server yourself. Thus on such "never touches the outside" networks, it would be possible to run a local instance for debuging purpose and feed it with the good old "station wagon full of harddrives or optical discs" method.


      Comment


      • #13
        Originally posted by DrYak View Post

        His point is that there's no way to run a proxy on a network that has not interaction at all with the outside
        Not true. A internal infrastructure can act as a proxy and as I pointed out in my original repo, debuginfod itself is optional. You can continue using debuginfo packages if you wish

        Comment

        Working...
        X