SliTaz Forum
You are not logged in.
Pages: 1
Hi all
I installed Bash to my system and have the man pages installed, and I ran into an issue with the 'w' command; I can find it in the man pages, but in scripts and in the console, I get 'sh: w: command not found'. Any thoughts?
Offline
w command?
Offline
w in BASH tells you how many users are logged in, their uids, the processes they are running at a time etc.
Offline
w sounds like an alias for who
Offline
oh, yeah that works although it doesn't generate the "what" info. hmm... maybe its a bash version difference? I read about it
http://tldp.org/LDP/Bash-Beginners-Guide/html/sect_02_01.html
Curiously, though, the command "w" is still listed in the man pages on my machine.
Offline
My guess is that it may be a standard alias that isn't set in SliTaz by default.
Offline
could be; I still wonder why its the man pages even though its not recognized by the shell
[c]
SYNOPSIS
w [-husfVo] [user]
DESCRIPTION
w displays information about the users currently on the machine, and
their processes. The header shows, in this order, the current time,
how long the system has been running, how many users are currently
logged on, and the system load averages for the past 1, 5, and 15 min-
utes.
The following entries are displayed for each user: login name, the tty
name, the remote host, login time, idle time, JCPU, PCPU, and the com-
mand line of their current process.
The JCPU time is the time used by all processes attached to the tty.
It does not include past background jobs, but does include currently
running background jobs.
The PCPU time is the time used by the current process, named in the
"what" field.
COMMAND-LINE OPTIONS
-h Don't print the header.
-u Ignores the username while figuring out the current process and
cpu times. To demonstrate this, do a "su" and do a "w" and a "w
-u".
-s Use the short format. Don't print the login time, JCPU or PCPU
times.
-f Toggle printing the from (remote hostname) field. The default as
released is for the from field to not be printed, although your
system administrator or distribution maintainer may have compiled
a version in which the from field is shown by default.
-V Display version information.
-o Old style output. Prints blank space for idle times less than one
minute.
user Show information about the specified user only.
FILES
/var/run/utmp
information about who is currently logged on
/proc process information
NOTES
The output for Idle, JCPU and PCPU times vaires depending on if you use
SEE ALSO
free(1), ps(1), top(1), uptime(1), utmp(5), who(1)
AUTHORS
w was re-written almost entirely by Charles Blake, based on the version
by Larry Greenfield <greenfie@gauss.rutgers.edu> and Michael K. Johnson
<johnsonm@redhat.com>.
Please send bug reports to <albert@users.sf.net>
8 Dec 1993 W(1)[/c]
Offline
Well, I did find something... Output of <printenv> indicates the default Shell is /bin/sh
Offline
Hi
There's a version of /usr/bin/w in the procps package:
# tazpkg get-install procps
Offline
Two things. First, /bin/sh is the standard shell executable. Ash (which is provided by Busybox) initially uses it and when you install Bash, bash replaces /bin/sh with a link to itself.
Secondly, like Paul pointed out, w is provided by procps and not Bash. The majority of SliTaz's standard unix commands are provide by Busybox rather than the standard GNU Coreutils and procps. This is mainly to save space and Busybox does pretty well function wise. The two main issues with using Busybox over the real commands is that the busybox command might not have all the features or flags as the real one. The other issue is that some commands just aren't there. For an average linux user, this is minor, but to somebody following a tutorial designed for larger distro, this can be a huge pain.
Basically, this isn't an issue with Bash at all but something that wasn't implemented into Busybox.
Offline
Thank you to Paul and Trixar_za for the replies and the info; I did learn something new and that's why I am here. Awesome!
Offline
Pages: 1
[ Generated in 0.021 seconds, 7 queries executed - Memory usage: 1.55 MiB (Peak: 1.77 MiB) ]