Skip Navigation

Programmer Humor @lemmy.ml

Ephera @lemmy.ml

12mo ago

Spent 10 minutes debugging...

15 comments

10 minutes? That's it. That's easily a 3 hour time sink.
- Well, in this case, it was a graphical program that was doing it, and I really could've recognized that the file was being created by that. I had just kind of forgotten that I opened this graphical program a few days ago on a different workspace...
- OP is clearly boasting about how smart they are.

Only 10 minutes? Those are rookie numbers
- Or pro numbers, depending on how you look at it.

lsof is a good tool would recommend it whenever something weird is happen, tho you gotta be root for it
- Another is checking modified time of the directory

I'm curious you'd see it in ls -l Did inode change? I remember making the same mistake. I think everyone sees this sometime during the career
- The inode does change, yeah:
  The regular ls -l doesn't show the inode on my system, though. I only realized it when I had assigned more permissions to the file and those got reset by deleting the file. The last-modified timestamp also gets updated each time, but I only spotted that afterwards...
  
  Give me your dotfiles or I will sneak into your home and tie all the sleeves of your shirts into knots
  
  That's a pretty terminal! Mind telling how you did it?

It's usually 10 mins to debug, and 3 hours explaining, categorizing, identifying the scope of it exists everywhere else...

Kinda similar. I remember having a file I could t delete. But I could move it to a new folder and delete that folder and the file would delete.

15 comments