Tag Archives: program

wiggle: A little room for wiggle

I have wiggle on my list for this morning, but I don’t know if I can show a very useful case for it.

2015-01-25-j3dmt61-wiggle

I understand from the program description that wiggle is designed to patch code where patch itself can’t, because of conflicting changes or some other error.

Personally I couldn’t come up with something so intricate to show what patch couldn’t do, but wiggle could. It’s another one of those situations where I’m trying to find a broken case for a program, so I can demonstrate another program. :\

Which isn’t very easy if you’re not one of the people who immediately sees the use of wiggle anyway. I’m guessing if you read through the description of wiggle and say to yourself, “Hmm, that could be useful to me. …” then you’re already way ahead of me.

So I’ll leave it at that. I should mention that wiggle is in Debian and AUR; both wiggle and wiggle-git stopped on warnings for me, so you might want to disable warnings that are treated as errors when you build it.

Of course, the Debian version runs fine. There’s the convenience of a precompiled distro. Then again, the Debian package page links to a dead home page, so there’s the convenience of AUR, too. … 😉

kill: For one simple reason

I kept back the kill command from coreutils because there’s one thing it can do, one flag in particular, that I felt I should mention. kill itself has a lot of options for stopping programs — gracefully or ungracefully — but the most helpful thing it does for me is this:

kill -USR1 9003

where 9003 (or whatever) is the PID of my old friend dd, the cool tool with no output whatsoever. Except that when it gets a -USR1 flag from kill, it actually spits out a little information.

kmandla@6m47421: ~$ dd if=/dev/zero of=/dev/null
9482411+0 records in
9482411+0 records out
4854994432 bytes (4.9 GB) copied, 12.4079 s, 391 MB/s

So in a worst-case scenario, when I’m wondering if dd is actually still running or has fallen into a trance state and maybe never coming back, kill and the -USR1 flag at least tells me if it has a pulse.

I know kill does other stuff too, but I do enjoy the irony of sending the kill command to see if a program is still alive. :\