Sponsored Content
Top Forums UNIX for Dummies Questions & Answers What are the executable file formats in Solaris and Linux? Post 302785379 by Yoda on Monday 25th of March 2013 01:29:11 PM
Old 03-25-2013
In Linux, file types are not recognized by file extensions. It is actually determined by the data in a file. The file extension doesn't even matter.

If you run file command on any file, three sets of tests, performed in this order: filesystem tests, magic number tests and language tests to determine the file type.

Go over the file command manual for more information:
Code:
man file

 

8 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Linux Script to move executable to quarantine

Please help! I am preparing a Linux Script to move windows executable files from samba directory to quarantine directory. For safety, will use "file" command to determine if its executable. Anyone can help? Below is my trial script, but it just move everything, including non-executable.. any wrong... (2 Replies)
Discussion started by: gavintam
2 Replies

2. Solaris

Executable compiled on solaris 10 not working on solaris 9

Hi I compiled an executable on Solaris 10 which creates semaphore ( semget) but it didn't work on solaris 9 , while it is executing sucessfully on solaris 10. It is throwing the system error that Invalid arguments ( system error 22) on solaris 9. the ldd for the executable on two servers is as... (4 Replies)
Discussion started by: ash_bit2k2
4 Replies

3. Solaris

Executable file on Solaris

Hi! What are executable file formats in Solaris? Can someone please share it? Thanks! (3 Replies)
Discussion started by: Klyde
3 Replies

4. Shell Programming and Scripting

Removing formats (bold) from UNIX file

Hi , Could you please guide me how to remove formatting (bold text) in a unix file? vi editor showing like this... ^ Cat command showing like this... tl21ss01 tl21ss02 tl21ss03 (6 Replies)
Discussion started by: suresh3566
6 Replies

5. Shell Programming and Scripting

Get the File name of perl executable in Linux

Hi All, I just want to know how to get the executable name of the perl script as i know "$0" will give me the script name but i want to know the executable name which i got it from the script using pp command. Regards Raj (1 Reply)
Discussion started by: kar_333
1 Replies

6. Shell Programming and Scripting

Need to check the file formats

Hi, I want to check the incoming files whether the file is Mac file or dos/windows file in unix shell script. Sometimes client is posting Mac file and sometimes it is dos file. Could you please help me how to determine/check whether the file is Mac or dos. Help in advance Thanks (4 Replies)
Discussion started by: lkeswar
4 Replies

7. Shell Programming and Scripting

Shell script to encrypt the xls file using executable jar in Linux SUSE 11.4

Dear Experts, I am an ERP consultant and would like to learn shell script. We are working on Linux SUSE 11.4 and I am very new to shell scripting. We can manually encrypt an excel file using "executable jar" through command prompt by placing the jar file & the file to be encrypted on a physical... (1 Reply)
Discussion started by: nithin226
1 Replies

8. UNIX for Beginners Questions & Answers

How to make a .exe file executable in Linux?

Dear all, I download a .exe file in my current folder called: ukbmd5.exe. I was told to run the command below: ukbmd5 ukb25278.enc to verify the integrity of the files that you have downloaded and the program ukbmd5 has been made available to assist with decrpying ukb25278.enc. while when I run... (1 Reply)
Discussion started by: forevertl
1 Replies
Apache::Test(3) 					User Contributed Perl Documentation					   Apache::Test(3)

NAME
Apache::Test - Test.pm wrapper with helpers for testing Apache SYNOPSIS
use Apache::Test; DESCRIPTION
Apache::Test is a wrapper around the standard "Test.pm" with helpers for testing an Apache server. FUNCTIONS
plan This function is a wrapper around "Test::plan": plan tests => 3; just like using Test.pm, plan 3 tests. If the first argument is an object, such as an "Apache::RequestRec" object, "STDOUT" will be tied to it. The "Test.pm" global state will also be refreshed by calling "Apache::Test::test_pm_refresh". For example: plan $r, tests => 7; ties STDOUT to the request object $r. If there is a last argument that doesn't belong to "Test::plan" (which expects a balanced hash), it's used to decide whether to con- tinue with the test or to skip it all-together. This last argument can be: o a "SCALAR" the test is skipped if the scalar has a false value. For example: plan tests => 5, 0; But this won't hint the reason for skipping therefore it's better to use have(): plan tests => 5, have 'LWP', { "perl >= 5.7.3 is required" => sub { $] >= 5.007003 } }; see have() for more info. o an "ARRAY" reference have_module() is called for each value in this array. The test is skipped if have_module() returns false (which happens when at least one C or Perl module from the list cannot be found). o a "CODE" reference the tests will be skipped if the function returns a false value. For example: plan tests => 5, &have_lwp; the test will be skipped if LWP is not available All other arguments are passed through to Test::plan as is. ok Same as Test::ok, see Test.pm documentation. sok Allows to skip a sub-test, controlled from the command line. The argument to sok() is a CODE reference or a BLOCK whose return value will be passed to ok(). By default behaves like ok(). If all sub-tests of the same test are written using sok(), and a test is executed as: % ./t/TEST -v skip_subtest 1 3 only sub-tests 1 and 3 will be run, the rest will be skipped. skip Same as Test::skip, see Test.pm documentation. test_pm_refresh Normally called by Apache::Test::plan, this function will refresh the global state maintained by Test.pm, allowing "plan" and friends to be called more than once per-process. This function is not exported. Functions that can be used as a last argument to the extended plan(): plan tests => 5, &have_http11; Require HTTP/1.1 support. have_ssl plan tests => 5, &have_ssl; Require SSL support. Not exported by default. have_lwp plan tests => 5, &have_lwp; Require LWP support. have_cgi plan tests => 5, &have_cgi; Requires mod_cgi or mod_cgid to be installed. have_apache plan tests => 5, have_apache 2; Requires httpd-2.x (apache-2.x). plan tests => 5, have_apache 1; Requires apache-1.3.x. have_perl plan tests => 5, have_perl 'iolayers'; plan tests => 5, have_perl 'ithreads'; Requires a perl extension to be present, or perl compiled with certain capabilities. The first example tests whether "PerlIO" is available, the second whether: $Config{useithread} eq 'define'; have_module plan tests => 5, have_module 'CGI'; plan tests => 5, have_module qw(CGI Find::File); plan tests => 5, have_module ['CGI', 'Find::File', 'cgid']; Requires Apache C and Perl modules. The function accept a list of arguments or a reference to a list. In case of C modules, depending on how the module name was passed it may pass through the following completions: 1 have_module 'proxy_http.c' If there is the .c extension, the module name will be looked up as is, i.e. 'proxy_http.c'. 2 have_module 'mod_cgi' The .c extension will be appended before the lookup, turning it into 'mod_cgi.c'. 3 have_module 'cgi' The .c extension and mod_ prefix will be added before the lookup, turning it into 'mod_cgi.c'. have plan tests => 5, have 'LWP', { "perl >= 5.7.3 is required" => sub { $] >= 5.007003 } }, { "not Win32" => sub { $^O eq 'MSWin32' } }, 'cgid'; have() is more generic function which can impose multiple requirements at once. All requirements must be satisfied. have()'s argument is a list of things to test. The list can include scalars, which are passed to have_module(), and hash references. The hash references have a condition code reference as a value and a reason for failure as a key. The condition code is run and if it fails the provided reason is used to tell user why the test was skipped. In the presented example, we require the presense of the "LWP" Perl module, "mod_cgid", that we run under perl >= 5.7.3 on Win32. It's possible to put more than one requirement into a single hash reference, but be careful that the keys will be different: have 'LWP', { "perl >= 5.7.3 is required" => sub { $] >= 5.007003 }, "not Win32" => sub { $^O eq 'MSWin32' }, }, 'cgid'; Also see plan(). Apache::TestToString Class The Apache::TestToString class is used to capture Test.pm output into a string. Example: Apache::TestToString->start; plan tests => 4; ok $data eq 'foo'; ... # $tests will contain the Test.pm output: 1..4 ok 1 ... my $tests = Apache::TestToString->finish; perl v5.8.0 2002-09-10 Apache::Test(3)
All times are GMT -4. The time now is 07:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy