12-07-2006
Quote:
Originally Posted by Perderabo
Except for Linux, few versions of unix have a /bin/sh that supports disown.
Good to know. Is it that they don't need it, or do they simply not support leaving processes behind?
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Anyone can help me ?
I try to using crontab with a simple shell script as echo it run okay but now i have more command in script. when I set entry to crontab and whe it run i get mail with error cannot execute binary file.
it urgent so please help me the soutions. Thank so much for your help.... (5 Replies)
Discussion started by: raccsdl
5 Replies
2. Linux
We are getting one error when we execute the binary file below mentioned, and ownership goes to root:nobody, how to resolve this problem.
sh /home/pub/bin/awk: cannot execute binary file
:confused:
Pls help me out . (2 Replies)
Discussion started by: durgaprasadr13
2 Replies
3. Shell Programming and Scripting
HI,
i am trying to execute one .bin file which is a pre-installed (not compiled by me). But I am getting the error "cannot execute binary file".I checked the permissions and everything is ok.
also I checked ldd <bin-filename> andit showed a msg "not a dynamic executable"
Can anyone help in... (4 Replies)
Discussion started by: bhag281
4 Replies
4. Linux
Hi,
I had changed my compiler options earlier so that it would compile and produce output for ARM but now i want to change it back so that i can get the executable for normal linux, I am facing problem, please help me out... it say
-bash: ./a.out: cannot execute binary file
When i had a look... (2 Replies)
Discussion started by: niranjanvg
2 Replies
5. SuSE
When I am trying to execute a script created by Perl2exe in Linux SLES 8.1 running with virtual machine on mainframe s/390 ....I am getting
"cannot execute binary file"....
In the linux server which are not in mainframe the scripts are fine.....
Thanks for help (1 Reply)
Discussion started by: Anu10
1 Replies
6. UNIX for Dummies Questions & Answers
As root, I receive the error message, "cannot execute binary file" when running some commands such as /usr/bin/clear or /usr/sbin/brctl or /usr/sbin/lsof. The system is running RHEL5.5. File permissions are 755. noexec is NOT set on the partitions where these files live.
I've spent a... (6 Replies)
Discussion started by: SmithJ
6 Replies
7. Linux
I'm trying to install JasperReports Server 4.1 on Linux Ubuntu (release 11.04) as root and have following message:
-bash: ./jasperreports-server-cp-4.1.0-linux-x64-installer.run: cannot execute binary file
Is any idea what should I do in order to install Jasper?
Previously, I installed... (6 Replies)
Discussion started by: pots06
6 Replies
8. UNIX for Dummies Questions & Answers
Grettings,
Hi and thanks for taking a look at this. I'm going to attempt to explain this the best I possible can but due to my limited knowledge of linux this may prove difficult. I have attempted to install xcrysden on cygwin following the instruction on xcrysden webpage (I attempted to link the... (2 Replies)
Discussion started by: Zbay
2 Replies
9. Fedora
Hi all,
Probably somewhat of an obvous problem here but i'm no pro.
I just bought a PengPod1000 at pengpod.com
On it I have an image of Fedora 18.
I am trying to run an application I wrote for Fedora 14 32 bit desktop on this tablet. With all permissions setup using chmod but I get... (7 Replies)
Discussion started by: fedora18
7 Replies
10. Red Hat
Hi,
When i was trying to execute binary file i am getting the below " cannot execute binary file " error message."
My Unix Version is : Red Hat Enterprise Linux Server release 5.1 (Tikanga)
Logged in as Sudo user and $PATH Value is below
... (1 Reply)
Discussion started by: Nandy
1 Replies
LEARN ABOUT NETBSD
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (ISC Cron V4.1)
SYNOPSIS
crontab [-u user]
crontab [-elr]
DESCRIPTION
crontab is the program used to install, deinstall, or list the tables used to drive the cron(8) daemon in ISC Cron. Each user can have their
own crontab, and though these are files in /var/cron, they are not intended to be edited directly.
If the /var/cron/allow file exists, then you must be listed therein in order to be allowed to use this command. If the /var/cron/allow file
does not exist but the /var/cron/deny file does exist, then you must not be listed in the /var/cron/deny file in order to use this command.
If neither of these files exists, depending on the compiled in settings, only the super user will be allowed to use this command, or everyone
will be allowed to use this command. On NetBSD everyone is allowed to use this command.
The default maximum size for a crontab is 256 kilobytes, but this may be changed for all users on the system by putting the desired maximum
size (in bytes) in the /var/cron/maxtabsize file.
If the -u option is given, it specifies the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines
``your'' crontab, i.e., the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running
inside of su(1) you should always use the -u option for safety's sake.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename ``-'' is given.
The -l option causes the current crontab to be displayed on standard output.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically.
FILES
/var/cron/allow Optional list of users that are allowed to use crontab.
/var/cron/deny Optional list of users that are disallowed to use crontab.
/var/cron/maxtabsize Maximum size of crontab files. Defaults to 256 kilobytes.
/var/cron/tabs/ Directory containing the individual user crontab files, named after the user.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), cron(8)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2''). This new command syntax differs from previous versions of Vixie Cron, as well
as from the classic Version 3 AT&T UNIX syntax.
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
May 6, 2010 BSD