01-29-2020
Quote:
Originally Posted by
wisecracker
Hi Neo...
.................................
[code]#¡/bin/bash
.................................
Enjoy...
Thanks for sharing nice code wisecracker
Please forgive me if I am wrong here, I believe shebang should be
#!/bin/bash right?
Or please correct me if I missed something here, cheers.
Thanks,
R. Singh
This User Gave Thanks to RavinderSingh13 For This Post:
6 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I am interested in knowing if anyone out there has been using the BSD UNIX that underlies
MacOS X. Is this an "industrial strength" version of UNIX? Can I run X-Windows on such
a machine? How about TeXing, pythoning, PERLing or using other useful UNIX goodies
near and dear to my shrunken... (1 Reply)
Discussion started by: ncmathsadist
1 Replies
2. UNIX for Dummies Questions & Answers
1) How can I stop Vuze from reporting the following error: "Too many open files" ?
2) What directory do I need to be in to effectively utilize this command:
sudo bash -c 'ulimit -n 8192; sudo -u username ./azureus' ?
3) Is this the maximum number of files that I can allot to Vuze on OS X... (1 Reply)
Discussion started by: JFraser1
1 Replies
3. UNIX for Beginners Questions & Answers
Dear all,
I use awk quite a bit for data wrangling ... today I find weird behavior that I cannot wrap my head around.
if I execute the following command (simplified to illustrate the behavior ... nothing to do with the real command)
bash-3.2$ awk... (3 Replies)
Discussion started by: comm|getline
3 Replies
4. UNIX for Beginners Questions & Answers
why,just beacuse that its the bottom layer uses a small amount of bsd code? In my opinion, macos and Unix are completely different. The directories are long directory structures. For example, /application, /system, /user, /volumes, etc. are completely different from the traditional /bin/ /sbin... (5 Replies)
Discussion started by: malaizhichun
5 Replies
5. OS X (Apple)
Interestingly Apple has decided to switch the default shell for new users from bash to zsh in MacOS Catalina (10.15)
Use zsh as the default shell on your Mac - Apple Support
Another interesting fact is that Catalina also comes with /bin/dash (5 Replies)
Discussion started by: Scrutinizer
5 Replies
6. OS X (Apple)
Hi all...
This was the original code I created to expand a terminal on the fly using Python 2.6.x to the now 3.8.0 without modification under OSX 10.7.5.
I had no idea at the time that the MBP terminal could be full screen until here:... (0 Replies)
Discussion started by: wisecracker
0 Replies
LEARN ABOUT REDHAT
system
SYSTEM(3) Linux Programmer's Manual SYSTEM(3)
NAME
system - execute a shell command
SYNOPSIS
#include <stdlib.h>
int system(const char *string);
DESCRIPTION
system() executes a command specified in string by calling /bin/sh -c string, and returns after the command has been completed. During
execution of the command, SIGCHLD will be blocked, and SIGINT and SIGQUIT will be ignored.
RETURN VALUE
The value returned is -1 on error (e.g. fork failed), and the return status of the command otherwise. This latter return status is in the
format specified in wait(2). Thus, the exit code of the command will be WEXITSTATUS(status). In case /bin/sh could not be executed, the
exit status will be that of a command that does exit(127).
If the value of string is NULL, system() returns nonzero if the shell is available, and zero if not.
system() does not affect the wait status of any other children.
CONFORMING TO
ANSI C, POSIX.2, BSD 4.3
NOTES
As mentioned, system() ignores SIGINT and SIGQUIT. This may make programs that call it from a loop uninterruptable, unless they take care
themselves to check the exit status of the child. E.g.
while(something) {
int ret = system("foo");
if (WIFSIGNALED(ret) &&
(WTERMSIG(ret) == SIGINT || WTERMSIG(ret) == SIGQUIT))
break;
}
Do not use system() from a program with suid or sgid privileges, because strange values for some environment variables might be used to
subvert system integrity. Use the exec(3) family of functions instead, but not execlp(3) or execvp(3). system() will not, in fact, work
properly from programs with suid or sgid privileges on systems on which /bin/sh is bash version 2, since bash 2 drops privileges on
startup. (Debian uses a modified bash which does not do this when invoked as sh.)
The check for the availability of /bin/sh is not actually performed; it is always assumed to be available. ISO C specifies the check, but
POSIX.2 specifies that the return shall always be non-zero, since a system without the shell is not conforming, and it is this that is
implemented.
It is possible for the shell command to return 127, so that code is not a sure indication that the execve() call failed.
SEE ALSO
sh(1), signal(2), wait(2), exec(3)
2001-09-23 SYSTEM(3)