• Pragmatist (unregistered) in reply to Nagesh
    Nagesh:
    Server Maint teams do this all the time. Today we are running on server # X,tomorrow on # Y. That's reason we have to get updated tnsnames.ora files from server main team. We never know where our development database is going to show up on Monday. Due to this we have to patch our local tns files so that our connectivity to DB is maintained.

    I never think of this as a WTF, though.

    You really should think of it as a WTF I'm afraid.

    You can point your /network/admin directory at a shared location using environment variables, and have as many people as you want share the same sqlnet.ora and tnsnames.ora.

    None of that will prevent TRWTF being Oracle of course though

    P.S. - ignore my previous, quoteless post

  • Yu (unregistered)

    I wonder how long it will take for the Safety and Health IT department to notice his noodle?

  • Geggo (unregistered) in reply to Nagesh
    Nagesh:
    Due to this we have to patch our local tns files so that our connectivity to DB is maintained.
    One hint: Oracle can use LDAP in addition to tnsname.ora files. So just have to maintain the central LDAP server. You can even have multiple LDAP server in the case one server goes down. Oracle will ask them in a given order until it gets an answer. Oracle provides its own LDAP server, but personally I prefer OpenDS with Apache Directory Studio as administration GUI.
  • NUXI (unregistered) in reply to Dan
    Dan:
    From one of my intra-office emails (addresses changed to protect the guilty): Received: from SMTPSERVER4 ([1.2.3.4]) by SMTPSERVER1 ([1.2.3.1]) with mapi; Wed, 23 Feb 2011 10:17:48 -0700

    This is all the routing information I got from this message. No indication of the client machine that originated the message.

    Thats because you have an exchange server instead of an email server :P

  • Neil (unregistered) in reply to Dan
    Dan:
    some guy:
    If the app was sending emails, couldn't he have just checked the headers?
    Adam:
    Surely there would have been a Received header indicating the IP address of the machine from which the message originated?
    From one of my intra-office emails (addresses changed to protect the guilty): Received: from SMTPSERVER4 ([1.2.3.4]) by SMTPSERVER1 ([1.2.3.1]) with mapi; Wed, 23 Feb 2011 10:17:48 -0700

    This is all the routing information I got from this message. No indication of the client machine that originated the message.

    TRWTF is using MAPI to send mail.

  • NUXI (unregistered) in reply to trwtf
    trwtf:
    I work safety critical (commercial/military flight controllers) and I stand by my practices. In my business, if you don't have the discipline to follow the specs to the letter then there's a very real risk that people will die. Hoody, for the love of God don't ever go into aerospace.

    This ^^^^^ 100x. I've worked in that area too and its much different. The specs are rigid and you must follow them. If the specs are wrong, you do not just "fix it" while coding, you have to hold meetings to discuss the change. There are also huge restrictions on what language features you can use. Take the JSF coding standard as an example.

    It was really quite an eye opening experience to work on a proejct like that. I'll never again claim that software engineering doesn't exist, it certainly does exist in some parts of the industry.

  • anon (unregistered) in reply to The Bridge
    The Bridge:
    Rob Halford:
    There I was completely wasting, out of work and down All inside its so frustrating as I drift from host to host Feel as though nobody cares if I live or die So I might as well begin to put some action in my life

    Dropping a Log, Dropping a Log! Dropping a Log, Dropping a Log! Dropping a Log, Dropping a Log! Dropping a Log, Dropping a Log!

    You don't know what it's like!

    You don't have a clue!

  • anon (unregistered) in reply to Charles Duffy
    Charles Duffy:
    Nagesh:
    I never think of this as a WTF, though.

    If you don't have an easy way to tell where everything is, it's a WTF.

    I'm a DevOps type -- and all the infrastructure I deploy has a query interface; you can easily ask for "role:memcache" or "role:cluster_foo" and get a list of who's where. Moreover, we have central log shipping and management, and our developers (who don't have access to the production servers themselves) can query those logs without help.

    ...so yeah, not having any documentation or query interface or centralized logging, and relying on just one person who knows where everything is (and trusting that they won't get fired / quit / get hit by a bus) is very much a WTF.

    Charles, your organization is probably the exception and not the rule. One place I worked at a couple years ago stored all such information in word docs on file share somewhere. They (the server admins, DBA's, etc) forced the developers to fill out these word docs when new apps were going into production. As time goes on when the server admins, dba's etc would change locations of the apps they would never bother to update the word docs or keep track of anything. The whole IT department was quite the WTF!!!

  • (cs)
    cindy:
    find for all kinds of watches and handbags

    http://replica038.com

    How did you get pass Akismet?

  • (cs)

    "... He's in a meeting in Building C until six." ..."

    I see what you did there.

  • ccj (unregistered)

    "Rick counted to pi before hanging up the phone" TRWTF is that he never hung up the phone, and that the rest of the article is unreachable

Leave a comment on “Dropping a Log”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article