Sponsored Content
Full Discussion: POSIX compliance...
Operating Systems OS X (Apple) POSIX compliance... Post 302976763 by Scrutinizer on Tuesday 5th of July 2016 11:16:14 PM
Old 07-06-2016
Hi Barry,

That looks quite neat and Posixy!

Some comments and ideas:
  • The sleep command is not used in a POSIX compliant ways, since it gets fed a float here, and in POSIX it can only handle integers. An alternative is maybe to fill the hourglass more or less from the start, depending on the number of minutes / seconds, and compensate the rest with the first sleep command.
  • Instead of using awk to cut the first 6 characters you could use "${platform%"${platform#??????}"}" or better yet, replace the if statements with one case statement and use it pattern matching capability CYGWIN*), so you do not need to cut the platform string.
  • The awk command substitutions in the 2nd for loop take time and will skew the time slightly. An alternative is to use parameter expansions or predefine the strings so that it does not add as much to the time used by the sleep commands..
  • Perhaps you could have a seconds countdown instead of the static number.
  • If more time is entered than what the hourglass can handle, graphically turn the hourglass (nice scripting challenge?)
This User Gave Thanks to Scrutinizer For This Post:
 

5 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

sudo & Sox compliance

Hello, I am trying to convince my boss to stop allowing our users to login as root (superuser). Currently our users login to our unix server with their own account, then as needed, they will do an su and put in the root password. This scares me, for a bunch of reasons. Mainly, one is that we... (1 Reply)
Discussion started by: rwallaceisg
1 Replies

2. UNIX for Dummies Questions & Answers

man synopsis standard compliance

In different online sources, I found bits and pieces of information about those square and angular brackets and pipes. From what I have read, I can conclude it looks like this: 1. Options outside any brackets are mandatory 2. Options inside these < .. > are mandatory too 3. Options inside ... (4 Replies)
Discussion started by: vkleban
4 Replies

3. Cybersecurity

PCI DSS Compliance : Insecure Communication Has Been Detected

From the nessus scanner tool report i got below vulnerability PCI DSS Compliance : Insecure Communication Has Been Detected http://www.tenable.com/plugins/index.php?view=single&id=56208 As per the description given in above link - I am not able to understand How to find insecure port... (2 Replies)
Discussion started by: saurabh84g
2 Replies

4. Red Hat

Looking for PCI Compliance tool for Redhat Lix.

Hi i am in new to Linux world . I have been assigned to a project to find out a tool that will fulfill the PCI compliance for Linux servers for Audit process. anyone have any recommendation on that. Do Rad hat have any native application or plug-ins which we can use for that. (1 Reply)
Discussion started by: sahasuman
1 Replies

5. HP-UX

Password compliance setting

I need to set password compliance for some servers in my company. However, the requirements are that we need to set different password policies for 3 different user groups within the company. These are : System Users: i.e root, etc Batch/Application Users: oracle, bscs, etc Standard User:... (0 Replies)
Discussion started by: anaigini45
0 Replies
ECJ(1)							      General Commands Manual							    ECJ(1)

NAME
ecj - manual page for eclipse JDT Compiler SYNOPSIS
ecj <options> <source files> DESCRIPTION
The JDT Compiler (jdtc) is a command version of Java compiler for eclipse. ecj has basic java compiler options like SUN's javac. Note: this manual page is out of date; please call the compiler with -help for the current documentation. OPTIONS
-help display a help message -version compiler version number -classpath <dir 1>;<dir 2>;...;<dir P> -d <dir> destination directory (if omitted no package directory structure is created) -d none no classfile is generated -1.3 set compliance level to 1.3 -1.4 set compliance level to 1.4 (default) -1.5 set compliance level to 1.5 -1.6 set compliance level to 1.6 -1.7 set compliance level to 1.7 -source <ver> assertions toggle (1.3 or 1.4, default is 1.3 in -1.3 mode and 1.4 in -1.4 mode) -target <ver> classfile target setting -nowarn no warning (equivalent to '-warn:none') -warn: <level> set warning level (e.g. '-warn:unusedLocals,deprecation') constructorName warn method with constructor name packageDefaultMethod warn attempt to override package-default method deprecation warn usage of deprecated type or member maskedCatchBlocks warn hidden catch block unusedLocals warn on unused local variable (never read) unusedArguments warn on unused method argument (never read) unusedImports warn on unused imports syntheticAccess warn when performing synthetic access for innerclass assertIdentifier warn occurrence of 'assert' used as identifier -deprecation equivalent to -warn:deprecation. -g[:<level>] debug attributes level -g all debug info ('-g:lines,vars,source') -g:none no debug info -g:[lines,vars,source] selective debug info -preserveAllLocals code gen preserve all local variables (for debug purpose) -noImportError no errors for unresolved imports -encoding specify default source encoding format (custom encoding can also be specifed on a per file basis by suffixing each input source file/folder name with '[encoding]') -log <filename> specify a log file -proceedOnError keep compiling when error, dumping class files with problem methods -verbose print accessedprocessed compilation units -referenceInfo compute reference info -progress show progress (only in -log mode) -time display speed information -noExit do not call System.exit(n) at end of compilation (n=0 if no error) -repeat <n> repeat compilation process <n> times (perf analysis) AUTHOR
This manual page was written by Takshi Okamoto and Jan Schulz <debian@katzien.de>. October 2002 ECJ(1)
All times are GMT -4. The time now is 04:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy