Stat command not found

kshsolarisstat

I want to execute stat command in my unix shell /usr/bin/ksh:

Input:

/bin/date +%Y%m%d%H%M%S -d "$(/usr/bin/stat -c %x find.txt)"

And the output:

/usr/bin/ksh: stat:  not found

My system:
SunOS 5.10 Generic_150400-23 sun4v sparc sun4v

Best Answer

The stat command is not standard. There's one on Linux, a more restricted one on embedded Linux, one with completely different options on FreeBSD and OSX, and none on most other Unix variants such as Solaris, AIX, and HP-UX. Your syntax looks like it's intended for Linux's stat.

You're apparently running a system without stat. You probably don't have date -d either then.

The only portable way to list a file's access time is with ls.

ls -log -u find.txt

This gives less precise output that what you need, in a cumbersome format.

If you can install GNU coreutils, do so and use its stat and date commands. Many modern Unix variants have an easy way to install GNU utilities.

Alternatively, use Perl, which is very often installed on Unix systems. Call stat to read the file's timestamp and localtime to break the timestamp into date and time parts.

perl -e '@stat = stat($ARGV[0]); @time = localtime($stat[9]); printf "%04d%02d%02d%02d%02d%02d\n", $time[5]+1900, @time[4,3,2,1,0]'

Related Solutions

Shell – Using sed to color the output from a command on solaris

\xNN is an escape sequence in GNU sed, but it is not standard, and in particular it is not available on Solaris.

You can include a literal escape character in your script, but that would make it hard to read and edit.

You can use printf to generate an escape character. It understands octal escapes, not hexadecimal.

esc=$(printf '\033')
echo "test" | sed "s,.*,${esc}[31m&${esc}[0m,"

You can call tput to generate the replacement text in the call to sed. This command looks up escape sequences in the terminfo database. In theory, using tput makes your script more portable, but in practice you're unlikely to encounter a terminal that doesn't use ANSI escape codes.

echo "test" | sed "s,.*,$(tput setaf 1)&$(tput sgr0),"

What are the dangers of setting a high limit to max File Descriptors per process

To see the number of file descriptors in use by a running process, run pfiles on the process id.

There can be performance impact of raising the number of fd’s available to a process, depending on the software and how it is written. Programs may use the maximum number of fd’s to size data structures such as select(3c) bitmask arrays, or perform operations such as close in a loop over all fd’s (though software written for Solaris can use the fdwalk(3c) function to do that only for the open fd’s instead of the maximum possible value).

Best Answer

Related Solutions

Shell – Using sed to color the output from a command on solaris

What are the dangers of setting a high limit to max File Descriptors per process

Related Question