Why Does BASH on Mac OSX Rarely Save to History
-
-
I should point out, now that I think about it, that recalling the commands using the "up arrow" even when I just used it does not work consistently either. It will randomly (as far as I can tell) recall different versions of the commands, including ones I have not run. So I have the issue when I go to run a command twice in a row, I have to check it very carefully because it does not come back up the same always, even when it was the very last command.
-
Does Mac have something like psacct? I thought I read somewhere that it had accton and you could run lastcomm.
-
@johnhooks said:
Does Mac have something like psacct? I thought I read somewhere that it had accton and you could run lastcomm.
I tried lastcomm, but no luck. Does not appear to be available.
-
@scottalanmiller said:
@johnhooks said:
Does Mac have something like psacct? I thought I read somewhere that it had accton and you could run lastcomm.
I tried lastcomm, but no luck. Does not appear to be available.
Oh, sorry. I have almost zero Mac experience. I never wanted to shell out the money for one. I'll look around though.
-
Yeah, this is my first one in a very long time and I'm constantly frustrated with things not working, crashes, things that I'm just confused by or whatever.
I timed the boot time on this yesterday.... 14 seconds from power on to password, 28 seconds from password to second password (why does it always need that twice) and another 14 seconds from second password to usable desktop. I can't remember anything booting that slowly since we were using spinning disks on Windows XP and even then I feel like it was comparable or better plus never required that I log in twice.
-
My machine crashed overnight last night. No idea why. There has to be something wrong with it.
-
That sucks. If it makes you feel any better my Fedora 22 boots in about three seconds (after the bios screen).
-
That's more of what I am used to. Even brand new out of the box this thing booted roughly the same as it does now. Nothing has noticeably changed. The double logins were always needed (I suspect that it crashes after the first boot and boots again, but there is no way to tell and this is how it has always worked and it never tells me there was a crash, just seems to do everything twice.) I can't tell that it takes any longer than when it was fresh from the box.
-
This any help?
https://discussions.apple.com/thread/3922262 -
Sadly no, I get most history, just not all. So can't be permissions. Very different than his issue of no history whatsoever.
-
@scottalanmiller As much of a problem that OS X has given you, I shudder to think: Have you tried Windows 10 or $favoriteLinuxDistro to see if the system runs better under another OS? If not, then it may actually be hardware problems.
-
@dafyre said:
@scottalanmiller As much of a problem that OS X has given you, I shudder to think: Have you tried Windows 10 or $favoriteLinuxDistro to see if the system runs better under another OS? If not, then it may actually be hardware problems.
I can't practically replace the OS on the hardware. That would be nice. A potential alternative is to run Linux in a VM which, from my testing, is completely stable and normal (within the confines of the overall OS staying up and running.)
-
If it is crashing that often you may have something else wrong. I haven't had mine crash in months, but I have a mac pro server that isn't waking up from sleep with out being unplugged for 10 seconds. It only happens about once every other week. Called Apple, they did a online log dump, couldn't find anything but kept putting pressure on them. They agreed to let me bring it into a Apple store for more diagnostics and have told me if they can't figure it out, they will replace it for free.
If I was you I would start keeping a log of system crashes for about a week, then call and start hounding on support because what you are experiencing is not normal. The plus side is Apple stands behind their hardware and their OS so as long as you are still under warrantee, they will cover both.
-
@s.hackleman said:
If it is crashing that often you may have something else wrong. I haven't had mine crash in months, but I have a mac pro server that isn't waking up from sleep with out being unplugged for 10 seconds. It only happens about once every other week. Called Apple, they did a online log dump, couldn't find anything but kept putting pressure on them. They agreed to let me bring it into a Apple store for more diagnostics and have told me if they can't figure it out, they will replace it for free.
Sadly, no Apple Stores in this country, any bordering country, any bordering country to those, or to their bordering countries. I think my nearest store is like six countries away
Apple support is a bit lacking outside of the US and the richest European countries.
-
@s.hackleman said:
The plus side is Apple stands behind their hardware and their OS so as long as you are still under warrantee, they will cover both.
That's not my experience with them supporting clients. I've been escalated to Apple engineering for issues and had them be like "yeah, nothing we can do, this doesn't really work." And they just gave up.
-
@scottalanmiller said:
@s.hackleman said:
The plus side is Apple stands behind their hardware and their OS so as long as you are still under warrantee, they will cover both.
That's not my experience with them supporting clients. I've been escalated to Apple engineering for issues and had them be like "yeah, nothing we can do, this doesn't really work." And they just gave up.
They should know, they're Geniuses.
-
Ha ha. No Geniuses is the name for the L0 techs. This was actually engineering in Cupertino.
-
@scottalanmiller said:
Ha ha. No Geniuses is the name for the L0 techs. This was actually engineering in Cupertino.
Ha I was just kidding. How did you get through to engineering? That's kind of amazing in itself.
-
@johnhooks said:
@scottalanmiller said:
Ha ha. No Geniuses is the name for the L0 techs. This was actually engineering in Cupertino.
Ha I was just kidding. How did you get through to engineering? That's kind of amazing in itself.
There is a way, can't remember how you do it but it wasn't hard. There is an escalation path for business customers running the server OS to get there pretty easily when needed. Unfortunately, engineering had no power to fix the issues and just admitted that they had released the product hoping no one would use what we were using and that it wasn't working and they had no way to fix it and would be removing it in the future.
Total fail.
