“last” command not working properlyDia command line not workingcopy last command in...
Does the US Armed Forces refuse to recruit anyone with an IQ less than 83?
In search of a pedagogically simple example of asymmetric encryption routine?
What font is used in Code Runner 3 by Nikolai Krill?
I've been fired, was allowed to announce it as if I quit and given extra notice, how to handle the questions?
How dangerous are my worn rims?
Parent asking for money after I moved out
Is there a pattern for handling conflicting function parameters?
Search for something difficult to count/estimate
Determining if auto stats update is in progress
Check reference list in pandas column using numpy vectorization
Is there any problem with students seeing faculty naked in university gym?
Why do personal finance apps focus on outgoings rather than income
How is the speed of nucleons in the nucleus measured?
What is the origin of the minced oath “Jiminy”?
How to "Start as close to the end as possible", and why to do so?
As an interviewer, how to conduct interviews with candidates you already know will be rejected?
Did the Soviet army intentionally send troops (e.g. penal battalions) running over minefields?
How to prove (A v B), (A → C), (B → D) therefore (C v D)
Could the Queen overturn the UK Supreme Court ruling regarding prorogation of Parliament?
Sci-fi story about aliens with cells based on arsenic or nitrogen, poisoned by oxygen
Is right click on tables bad UX
C - Learning Linked Lists, Pointer Manipulation - Store some ints, print and free memory
Young adult short story book with one story where a woman finds a walrus suit and becomes a walrus
Redirect output on-the-fly - looks not possible in Linux, why?
“last” command not working properly
Dia command line not workingcopy last command in terminalupdate_terminal_cwd demystified please?Last command source fileWhy is this command not found?root entries in last command`launchctl export` command not working?Terminal not working, resource unavailable
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{
margin-bottom:0;
}
I read a few guides online that explain how to use the command last to have a list of user logins.
One of the easiest command is:
last -s yesterday -t today
which should show the list of logins from yesterday till today. But when I execute this command on a Mac I receive an:
last: illegal option -- s
usage: last [-#] [-t tty] [-h hostname] [user ...]
This is not how it is supposed to work.
Why -s is not recognised?
terminal command-line login
add a comment
|
I read a few guides online that explain how to use the command last to have a list of user logins.
One of the easiest command is:
last -s yesterday -t today
which should show the list of logins from yesterday till today. But when I execute this command on a Mac I receive an:
last: illegal option -- s
usage: last [-#] [-t tty] [-h hostname] [user ...]
This is not how it is supposed to work.
Why -s is not recognised?
terminal command-line login
add a comment
|
I read a few guides online that explain how to use the command last to have a list of user logins.
One of the easiest command is:
last -s yesterday -t today
which should show the list of logins from yesterday till today. But when I execute this command on a Mac I receive an:
last: illegal option -- s
usage: last [-#] [-t tty] [-h hostname] [user ...]
This is not how it is supposed to work.
Why -s is not recognised?
terminal command-line login
I read a few guides online that explain how to use the command last to have a list of user logins.
One of the easiest command is:
last -s yesterday -t today
which should show the list of logins from yesterday till today. But when I execute this command on a Mac I receive an:
last: illegal option -- s
usage: last [-#] [-t tty] [-h hostname] [user ...]
This is not how it is supposed to work.
Why -s is not recognised?
terminal command-line login
terminal command-line login
asked 8 hours ago
Francesco MantovaniFrancesco Mantovani
1264 bronze badges
1264 bronze badges
add a comment
|
add a comment
|
2 Answers
2
active
oldest
votes

Always use man X directly on the Mac itself to see what is available for command X. The reason is that OS X was originally based on BSD and not GNU (most likely to avoid the GPL) so you should not follow Linux tutorials for MacOS.
add a comment
|
The 'last' command on a Mac has no -s option. Not all Unix commands are implemented the same on a Mac. Mac tends tends to use original BSD commands. As to why 's' isn't an option on the Mac, according to @Mark, it may be due to the difference in BSD (Mac) and GNU (Linux). There are most likely differences between the two.
First part OK. Second part is incorrect. Mac uses BSD commands. GNU, which is what Linux uses, often adds extra non standard options, BSD tends to stick to the older options, So upto BSD and GNU why options differ, not really Apple's choice
– Mark
7 hours ago
thank you. my bad.
– jmh
7 hours ago
add a comment
|
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes

Always use man X directly on the Mac itself to see what is available for command X. The reason is that OS X was originally based on BSD and not GNU (most likely to avoid the GPL) so you should not follow Linux tutorials for MacOS.
add a comment
|

Always use man X directly on the Mac itself to see what is available for command X. The reason is that OS X was originally based on BSD and not GNU (most likely to avoid the GPL) so you should not follow Linux tutorials for MacOS.
add a comment
|

Always use man X directly on the Mac itself to see what is available for command X. The reason is that OS X was originally based on BSD and not GNU (most likely to avoid the GPL) so you should not follow Linux tutorials for MacOS.

Always use man X directly on the Mac itself to see what is available for command X. The reason is that OS X was originally based on BSD and not GNU (most likely to avoid the GPL) so you should not follow Linux tutorials for MacOS.
answered 7 hours ago
Thorbjørn Ravn AndersenThorbjørn Ravn Andersen
5222 gold badges5 silver badges22 bronze badges
5222 gold badges5 silver badges22 bronze badges
add a comment
|
add a comment
|
The 'last' command on a Mac has no -s option. Not all Unix commands are implemented the same on a Mac. Mac tends tends to use original BSD commands. As to why 's' isn't an option on the Mac, according to @Mark, it may be due to the difference in BSD (Mac) and GNU (Linux). There are most likely differences between the two.
First part OK. Second part is incorrect. Mac uses BSD commands. GNU, which is what Linux uses, often adds extra non standard options, BSD tends to stick to the older options, So upto BSD and GNU why options differ, not really Apple's choice
– Mark
7 hours ago
thank you. my bad.
– jmh
7 hours ago
add a comment
|
The 'last' command on a Mac has no -s option. Not all Unix commands are implemented the same on a Mac. Mac tends tends to use original BSD commands. As to why 's' isn't an option on the Mac, according to @Mark, it may be due to the difference in BSD (Mac) and GNU (Linux). There are most likely differences between the two.
First part OK. Second part is incorrect. Mac uses BSD commands. GNU, which is what Linux uses, often adds extra non standard options, BSD tends to stick to the older options, So upto BSD and GNU why options differ, not really Apple's choice
– Mark
7 hours ago
thank you. my bad.
– jmh
7 hours ago
add a comment
|
The 'last' command on a Mac has no -s option. Not all Unix commands are implemented the same on a Mac. Mac tends tends to use original BSD commands. As to why 's' isn't an option on the Mac, according to @Mark, it may be due to the difference in BSD (Mac) and GNU (Linux). There are most likely differences between the two.
The 'last' command on a Mac has no -s option. Not all Unix commands are implemented the same on a Mac. Mac tends tends to use original BSD commands. As to why 's' isn't an option on the Mac, according to @Mark, it may be due to the difference in BSD (Mac) and GNU (Linux). There are most likely differences between the two.
edited 7 hours ago
answered 8 hours ago
jmhjmh
5,7262 gold badges9 silver badges33 bronze badges
5,7262 gold badges9 silver badges33 bronze badges
First part OK. Second part is incorrect. Mac uses BSD commands. GNU, which is what Linux uses, often adds extra non standard options, BSD tends to stick to the older options, So upto BSD and GNU why options differ, not really Apple's choice
– Mark
7 hours ago
thank you. my bad.
– jmh
7 hours ago
add a comment
|
First part OK. Second part is incorrect. Mac uses BSD commands. GNU, which is what Linux uses, often adds extra non standard options, BSD tends to stick to the older options, So upto BSD and GNU why options differ, not really Apple's choice
– Mark
7 hours ago
thank you. my bad.
– jmh
7 hours ago
First part OK. Second part is incorrect. Mac uses BSD commands. GNU, which is what Linux uses, often adds extra non standard options, BSD tends to stick to the older options, So upto BSD and GNU why options differ, not really Apple's choice
– Mark
7 hours ago
First part OK. Second part is incorrect. Mac uses BSD commands. GNU, which is what Linux uses, often adds extra non standard options, BSD tends to stick to the older options, So upto BSD and GNU why options differ, not really Apple's choice
– Mark
7 hours ago
thank you. my bad.
– jmh
7 hours ago
thank you. my bad.
– jmh
7 hours ago
add a comment
|