• (disco)
    > find '.*brain.*'
    > ERR_FILE_NOT_FOUND
    
  • (disco)

    Can't shift-delete? Dodged that one. Then you wonder how many people they "helped" with that script before and after.

  • (disco)

    Why do companies insist on shoving their programmers through the same helpdesk process that accounts and marketing have to use? If the helpdesk guys knew anything, they'd be programmers.

  • (disco)

    Dahl, Andy [14:23]: S%Topt S%TOP %

    SCREEN CONTROL TERMINATED BY Dahl, Andy [14:23]

    Loving the expression of urgency by typos.

  • (disco)

    Windows search apparently just ignores all punctuation in your search filter, so all those dots and stars and parentheses weren't really doing anything anyway...

  • (disco) in reply to eViLegion
    eViLegion:
    If the helpdesk guys knew anything, they'd be programmers.

    After the helpdesk guys have had to deal with enough programmers, they might have learned something.

  • (disco) in reply to kupfernigk
    kupfernigk:
    they might have learned something
    Unlikely. It seems it's a requirement to _not_ learn anything, but to follow the workflow script to completion. You get docked major QA points for deviating from the flow...
  • (disco)

    Are temp files really still a problem? Sure, once upon a time they could be a threat to the free space on the drive, but aside from browser cache files, what damage could having old junk really do in today's world?

  • (disco) in reply to Tsaukpaetra

    Admittedly this was over a decade ago but I ran into a case where a program sometimes would crash due to the contents of the temp directory. It was really strange as it was my code and all I was doing with the temp directory at that point was opening a log file and the log file wasn't the culprit, killing it had no effect on the crash. Unfortunately, the problem only occurred on factory-floor machines and it wasn't practical to leave one around long enough for me to come over (I was 2 hours away) and figure out what was really going on.

  • (disco) in reply to LorenPechtel

    Yes, in older days there was a real ceiling on the number of files a folder could hold, so it's definitely possible other processes were filling said folder. Folder Size Limits I suppose trwtf would have been using the temp folder for logging a non-temporary process.

  • (disco) in reply to Tsaukpaetra

    A few years ago, Acrobat Reader would crap all over itself when it's temp subdirectory would get too many files. Don't know if that's been fixed - I just have a process that kills off temp files over a month old.

  • (disco) in reply to Tsaukpaetra

    That wasn't the issue--you're not going to hit the files in a folder limit while opening an existing file.

  • (disco) in reply to LorenPechtel

    Unless some other process was using a tool to forcibly "clean" the temp directory, which tool had the capability to break open file locks, which one of them happened to belong to your application, and said application may or may not have had exception handling for when it's file handles are ripped from it.

  • (disco) in reply to eViLegion

    Most sysadmins started out on a first-line helpdesk. Further in their career they might be called Enterprise Admin, System Admin, root or even God, but in the end they are still a helpdesk - but by now the Nth line. Your disdain for helpdesks is just as unselective as this admittedly not-too-smart operator's script.

    On a side note: I support programmers every day. They're so superior that they complain about "System Idle" eating all of their processor power...

  • (disco) in reply to Tsaukpaetra

    Nothing of the sort was going on. This was a vanilla W98 install with only my program on it.

  • (disco) in reply to LorenPechtel

    Wow, that is definitely odd. Perhaps the Gremlins just woke up every now and then? ;)

  • (disco) in reply to dcon

    If you open an email attachment in Outlook (up to and including 2010, not sure about 2013), it will save the file to a temporary folder then open it with the assigned program. If you open another file with the same name, it will save it to the same folder, with a (1) appended, then (2), and so on, until (99), at which point, you won't be able to open these attachments anymore until you clear the (hidden) folder. Generally this bites users who receive some sort of scheduled report in an email, when the file name of the report is always the same.

  • (disco) in reply to Tsaukpaetra
    Tsaukpaetra:
    Are temp files really still a problem? Sure, once upon a time they could be a threat to the free space on the drive, but aside from browser cache files, what damage could having old junk really do in today's world?

    If your software reads its old temp files on startup or at some point during execution, that could cause crashes, corruption, etc. The obvious solution is to not read old temp files, but sometimes you have crash recovery and have to balance that with resilience.

  • (disco) in reply to Tsaukpaetra
    Tsaukpaetra:
    Unlikely. It seems it's a requirement to not learn anything, but to follow the workflow script to completion. You get docked major QA points for deviating from the flow...

    I didn't say the learning involved staying in the job.

  • (disco) in reply to Tsaukpaetra
    Tsaukpaetra:
    Are temp files really still a problem? Sure, once upon a time they could be a threat to the free space on the drive, but aside from browser cache files, what damage could having old junk really do in today's world?
    Exhausting the file count, which makes the build server unable to build, which is actually the cause of about 20% of false negatives in our CI system at my current workplace? The other 80% is even bigger WTF - our testing software is completely unreliable.
  • (disco) in reply to Gaska

    I... don't even know what to say to that... You build system is capable of generating billions of files?!

  • (disco) in reply to abarker
    > find '.*brain.*'
    > Found file memberlist-of-clubrain.xls
    
  • (disco) in reply to Tsaukpaetra
    Tsaukpaetra:
    I... don't even know what to say to that...
    Me neither. There are only a handful of people in this company who know what's actually going on during testing.
  • (disco)

    Time to stop using the company laptop and just move any work onto your own pc... or dual boot it. Another case of avoiding work to do work

  • (disco) in reply to Tsaukpaetra

    It's unfortunate but true. It's a management goal to standardize any CS effort. You, as CS staff, receive warning for talking to the customer for time excess the defined limit, even if your goal is to provide better service. I'm not surprised for sudden drop of the phone call to CS after talking to them to some minute because I understand that they have a target to meet. (Not that I'm not annoyed, though. So usually the next step is to request to talk to a supervisor. :grin: )

  • (disco) in reply to anotherusername

    It also ignores numbers. You can't search for a file with "123" in the name. (facepalm)

  • (disco) in reply to LorenPechtel

    I can tell you don't work for Adobe.

  • (disco) in reply to Tsaukpaetra
    Tsaukpaetra:
    Are temp files really still a problem? Sure, once upon a time they could be a threat to the free space on the drive, but aside from browser cache files, what damage could having old junk really do in today's world?

    I'll bring up this story once again: one time, I had a mysterious case of vanishing hard drive space. Turns out, I had 700 GB of temp files.

    700 GB. Given that I had a 1TB drive, 70% of my drive was taken up just by the Temp folder.

    So yes, it's possible to have all of the free space on the drive taken up by temp files.

  • (disco) in reply to Masaaki_Hosoi

    and this frienmds is why i mount /tmp as tmpfs file type.

    out of temp space? reboot!

  • (disco) in reply to accalia
    accalia:
    and this frienmds is why i mount /tmp as tmpfs file type.

    out of temp space? reboot!

    Doesn't help when it's your package manager swallowing /var/tmp whole...

    Filed under: the joys of ebuilds on a subpar /var...

  • (disco) in reply to tarunik
    tarunik:
    Filed under: the joys of ebuilds on a subpar /var...

    ...

    gentoo? YICK!

    that's worse than ArchLinux!

  • (disco) in reply to accalia

    Hey, Arch is fine!

    ...once you configure it, which, depending on you H4XX0R 5K1LL2, can take two days up to two years.

  • (disco) in reply to Gaska

    you forgot about updating it.

    it has a nasty habit of having critical packages stop working after updates.

    not something i want to deal with thank you very much.

    I'll run it to test something out in a VM but for long term primary usage give me something debian/ubuntu based

  • (disco) in reply to accalia
    accalia:
    it has a nasty habit of having critical packages stop working after updates.
    Nah. Happened twice to me so far - once was when they've moved /lib64 to /usr/lib and I didn't read the install notes, and another when Skype stopped working after updating glib2 (but that one is M$'s fault).
  • (disco) in reply to Gaska

    Skype on Linux?

    TIL.

  • (disco) in reply to mott555
    mott555:
    Skype on Linux?

    Yep, it's an older version, but it still works a treat

  • (disco) in reply to tarunik

    It's not older - it's entirely different from Windows version, past or present.

  • (disco)

    (As to Windows search: I've resorted to FIND as fallback, or a one-line batch with FOR /R and FIND.. In XP, you could at least switch back to W2K search functionality, which just did its job.)

    My first thought when reading about (.*temp.*) was, if Shakespeare would have had a computer, nobody would miss The_Tempest.drama. (Because nobody would know about it, that is.)

  • (disco) in reply to PWolff

    A lot of the time I'll just use dir pattern /s /b and scroll through the results, or add >list.txt to redirect the output to a text file.

Leave a comment on “Classic WTF: A Temporary Problem”

Log In or post as a guest

Replying to comment #453378:

« Return to Article