Command not found error

I'm trying to run this command in my terminal:
sudo ./cloudera-manager-installer.bin
however, it is saying that such a command is not found... I've tried also inputting the actual path to the object as such:
sudo ./cloudera-manager-installer.bin
and have gotten the same error messsage. Any feedback would be greatly appreciated!

The second command is the same as the first. It will work only if there is an executable named "cloudera-manager-installer.bin" in the current directory. If there isn't, change to the directory or use the full path.

Similar Messages

  • Command not found error while executing shell programs in terminal

    I have written one sample shell program.
    while executing shell program in terminal,it shows COMMAND NOT FOUND error.
    How to slove this.

    Post the "Actual" error.  It says more than command not found.
    Post your script.
    Post the output from:
    echo $PATH
    Post the output from:
    which name_of_command_not_found

  • Terminal troubles. Command not found error in the directory of the command.

    I'm getting a "command not found" error when I am in the directory of the command I want to run. For example try to run 'mysql' in the directory with that executable file and I get the error. BUT, if I put the full path to the mysql command, starting from the root, the command works correctly.
    I know this isn't a PATH issue, since I'm in the location of the file.
    It seems like a possible permissions issue, but I appear to have the proper permissions to the command and all parent directories. Moreover, I would assume that I would see a "permissions denied" error rather than a "command not found" error if this was the case.
    Beyond the two possibilities above, I'm stumped as to what the issue could be. To be clear, this is happening on more than one command, although both commands are within the /usr/local/ directory.
    Any help would be greatly appreciated!!! Thanks in advance!

    By default . is not included in your PATH and the shell does not do this on its own, as that is an easy way for someone to get a user to execute a Trojan.
    For example, in a multi-user system you create a script 'ls' and put it in a directory with a bunch of other stuff. Then go over to a user on the same system and ask them to help you with something in this directory. The first thing they will do is issue the 'ls' command, which if you have . in your PATH, or the shell always looks in the current working directory, means this user would execute the Trojan script instead of the real 'ls' command. That script do do anything using the privileges of the user running that script, including modifying stuff in their home directory that could give the person asking for help future access to that user's files and data.
    That is why . (the current working directory) is NOT part of PATH by default and shells do not look in the current working directory by default.

  • Aerender CC 2014 returns "command not found" error on Mac 10.9.3?

    Well, that about sums it up. I'm trying to run aerender in Terminal and I just get a command not found error.
    Here's the batch script: "aerender -project /Volumes/xxx/After_Effects_Templates/xxx.aep -comp "Final_Web_800x600" -OMtemplate 800x600 H.264-output /Volumes/xxx/Renders/rendertest.mov"
    Anyone know what I'm doing wrong?
    Many thanks in advance.
    Bettsy

    Hi wsrphoto,
    You need to follow these steps.
    1. Launch creative cloud application.
    2. Go to Preferences and go to Account tab.
    3. Sign out from there and then quit creative cloud application.
    4. Launch Creative cloud again and log-in back again
    5. Then download and install the product.
    Please revert if you still face any issue.

  • Command not found error while executing a shell script

    Hello,
    I am a newbie to linux.I am attaching the code which gives me following errors..
    error list:
    1. no such file or directory enviornemnt
    2. command not found
    3. ambiguous redirectline
    Script
    cd $HOME/wkdir
    rm /tmp/*.log
    # source environment
    . ./env
    # Run the install script to setup the database
    # Configure SH account
    sqlplus "/ as sysdba" <<! > /tmp/perflab_install.log 2>&1
    grant connect, resource, dba to SH;
    alter user sh account unlock;
    # create the fetch_n_rows procedure
    sqlplus "$PERFLAB_USER" <<! >> /tmp/perflab_install.log 2>&1
    drop index sales_time_bix;
    drop index sales_time_idx;
    create index sales_time_idx on sales(time_id) compute statistics;
    -- fetch_n_rows: fetches 'n' rows from the specified statement --
    CREATE OR REPLACE PROCEDURE fetch_n_rows(
    stmt VARCHAR,
    name VARCHAR,
    nexec NUMBER := 1,
    nrows NUMBER := 0,
    debug BOOLEAN := FALSE)
    IS
    -- Local variables
    curs INTEGER := null;
    rc INTEGER;
    nexec_it INTEGER := 0;
    nrows_it INTEGER;
    BEGIN
    dbms_application_info.set_module('DEMO', name);
    WHILE (nexec_it < nexec)
    LOOP
    curs := DBMS_SQL.OPEN_CURSOR;
    DBMS_SQL.PARSE(curs, stmt, DBMS_SQL.NATIVE);
    rc := DBMS_SQL.EXECUTE(curs);
    nrows_it := 0;
    LOOP
    IF (dbms_sql.fetch_rows(curs) <= 0 OR (nrows <> 0 AND nrows_it = nrows
    THEN
    EXIT;
    ELSE IF (debug = TRUE)
    THEN
    DBMS_OUTPUT.PUT_LINE(nrows_it);
    END IF;
    END IF;
    nrows_it := nrows_it + 1;
    END LOOP;
    DBMS_SQL.CLOSE_CURSOR(curs);
    nexec_it := nexec_it + 1;
    END LOOP;
    dbms_application_info.set_module(null, null);
    END fetch_n_rows;
    show errors
    # Start the workload
    . ./start_workload.sh > /tmp/setup_perflab.log 2>&1
    # Wait two minutes for workload to get going
    sleep 120
    # Modify snapshot interval
    sqlplus -s /NOLOG <<EOF >> /tmp/setup_perflab.log 2>&1
    connect / as sysdba
    set head on
    set feedback on;
    set pagesize 40
    rem -- event to allow setting very short Flushing interval
    alter session set events '13508 trace name context forever, level 1';
    rem -- change INTERVAL setting to 2 minutes
    rem -- change RETENTION setting to 6 hours (total of 180 snapshots)
    execute dbms_workload_repository.modify_snapshot_settings(interval => 2,-
    retention => 360);
    EOF
    Note : start_workload.sh is also in the same directory..
    Any help would be greatly appreciated.

    Please put your script between "code" format delimiters.
    http://wiki.oracle.com/page/Oracle+Discussion+Forums+FAQ
    You can add the line "set -x" at the beginning of your script to see at which line it fails? I suspect the . ./env line.

  • Shell Commands not found error when running application

    Hello,
    Im using MonoDevelop IDE in my Mac, before it used to work fine but after few days, now when I'm opening the application nothing happens., i checked the Console  for the log and it says this
    May  9 21:29:39 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x52052].com.ximian.monodevelop[1510]: /Applications/MonoDevelop.app/Contents/MacOS/monodevelop: line 17: dirname: command not found 
    May  9 21:29:39 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x52052].com.ximian.monodevelop[1510]: /Applications/MonoDevelop.app/Contents/MacOS/monodevelop: line 31: //mono-version-check: No such file or directory
    May  9 21:29:39 Sri-Vishnu-Totakuras-MacBook-Pro com.apple.launchd.peruser.501[599] ([0x0-0x52052].com.ximian.monodevelop[1510]): Exited with code: 1
    I thought may be some error with the "dirname" command, so i commented it in the code and gave the path of directory myself and then the console shows up like this.
    May  9 21:34:12 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x56056].com.ximian.monodevelop[1532]: /Applications/MonoDevelop.app/Contents/MacOS//mono-version-check: line 19: grep: command not found 
    May  9 21:34:12 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x56056].com.ximian.monodevelop[1532]: /Applications/MonoDevelop.app/Contents/MacOS//mono-version-check: line 19: cut: command not found
    May  9 21:34:12 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x56056].com.ximian.monodevelop[1532]: /Applications/MonoDevelop.app/Contents/MacOS//mono-version-check: line 20: cut: command not found
    May  9 21:34:12 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x56056].com.ximian.monodevelop[1532]: /Applications/MonoDevelop.app/Contents/MacOS//mono-version-check: line 21: cut: command not found
    May  9 21:34:12 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x56056].com.ximian.monodevelop[1532]: /Applications/MonoDevelop.app/Contents/MacOS//mono-version-check: line 22: cut: command not found
    May  9 21:34:12 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x56056].com.ximian.monodevelop[1532]: /Applications/MonoDevelop.app/Contents/MacOS//mono-version-check: line 31: osascript: command not found
    May  9 21:34:12 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x56056].com.ximian.monodevelop[1532]: Cannot launch MonoDevelop
    May  9 21:34:12 Sri-Vishnu-Totakuras-MacBook-Pro [0x0-0x56056].com.ximian.monodevelop[1532]: MonoDevelop requires the Mono Framework version 2.10.4 or later.
    May  9 21:34:12 Sri-Vishnu-Totakuras-MacBook-Pro com.apple.launchd.peruser.501[599] ([0x0-0x56056].com.ximian.monodevelop[1532]): Exited with code: 1
    I opened the contents of the application and run the shell script for opening aplication there it worked very fine and application started working.. But if i open application directly through launchpad or finder it doesnt show up and console
    I tried running those commands in the terminal directly there they work.. But dunno whats wrong in here. and even if try to open the application through the terminal it all opens fine.. what could be the possible problem, is it with my mac..?

    i finally figured out the problem.. it is with the environmental variables.  the path for all those commands like "grep" is not being set for the GUI applications.  that is why i got that error. 
    for those GUI applications which require path, we have to set path in the file /etc/launchd.conf  the environmental variables set in here are used by the gui applications and those which are launched through spotlight.
    that file may bot be present in most of the macs. No problem even if not present,we can create one and use.
    so  type in terminal
              $ sudo vi /etc/launchd.conf     
    and in the editor add these lines
              setenv PATH = /new/path
    and save.  Note: replace /new/path with the path which you need to have for the commands used in the script.
    remeber that you need to restart your mac for applications to use these environmental variables.

  • Command not found error in Linux

    Hi all,
    While login into Linux server using terminal i am getting following error.
    -bash: /usr/bin/id: No such file or directory
    -bash: [: =: unary operator expected
    While execute these commands getting following errors
    # clear
    -bash: clear: command not found
    # du -sh *
    -bash: du: command not found
    Help on these issues.
    Linux 32bit OS.
    Red Hat Enterprise Linux Server release 4.0 (Tikanga)

    Likely a flaky environment.
    What is the contents of .bash_profile in your $HOME?
    Any btw, why RHEL4? It is ancient.

  • HELP! Installer_Script_Springboard__: line 13: s: command not found ERROR

    got this error in the Installer log while using the upgrading option to Leopard. After that the installation just stalled and did not move. I have tried more than a few times. and same results. Can ANYONE PLEASE HELP ? Below is the error message
    Oct 27 05:48:23 localhost runner150: _Installer_Script_Springboard_163: /Volumes/Reddy`s HD/private/tmp/scripts.VaIV/_Installer_Script_Springboard_: line 13: s: command not found
    Oct 27 05:48:23 localhost runner150: _Installer_Script_Springboard_163:
    Oct 27 05:56:19 localhost Unknown67: 2007-10-27 05:56 Mac OS X Installer143 (CarbonCore.framework) FSEventStreamStart: ERROR: FSEvents_connect() => Unknown service name (1102)
    Oct 27 05:56:21 localhost OSInstaller143: installAutoFSMonitor: open failed

    Hi!
    After 6 hours of experimenting, disconnecting devices, formatting my hard drive (joy!) and getting nowhere, I found the problem: apparently, Leopard has trouble dealing with some characters in the volume name (in my case it was '). Rename the volume to something simple, short and with no weird characters and the Leopard will install.
    And, to Apple: I'm very disappointed with the quality of the Leopard install. If a character is valid in OS X, the setup should support it!
    Best regards,
    IYan

  • Spool Command not found error

    Dear friends,
    I am trying to get the list of active and inactive sessions for some users and created a script for this but getting some error message.
    Could you please check why I am getting this error while running from the putty. The same sql command I run from sql developer and get the output with no errors.
    Script:
    set pagesize 0
    set feedback off
    set echo off
    sqlplus '/as sysdba'
    spool kill_session_list.sql;
    select 'ALTER SYSTEM KILL SESSION '''||sid||','||serial#||''';'
    from v$session
    where type!='BACKGROUND'
    and username in('RO_USER','KHALIED','INFAREP','DAC','DMUSER_PROD','LAND_PROD','STAGE_PROD','BIUSER_PROD','OLAPDW','DWRO');
    spool off;
    exit
    Error msg:
    ./kill_session_generate.sql: line 5: spool: command not found
    ./kill_session_generate.sql: line 6: syntax error near unexpected token `||'
    ./kill_session_generate.sql: line 6: `select 'ALTER SYSTEM KILL SESSION '''||sid||','||serial#||''';''
    Thanks.

    877938 wrote:
    Dear friends,
    I am trying to get the list of active and inactive sessions for some users and created a script for this but getting some error message.
    ./kill_session_generate.sql: line 5: spool: command not found
    ./kill_session_generate.sql: line 6: syntax error near unexpected token `||'
    ./kill_session_generate.sql: line 6: `select 'ALTER SYSTEM KILL SESSION '''||sid||','||serial#||''';''Odd.
    Look at the script kill_session_generate.sql very carefully, especially the lines before and after the SPOOL command as well as the spool command itself. Consider deleting and retyping the line with the SPOOL command in case invisible special characters are causing problems
    Good luck!

  • [SOLVED] /bin/bash: endif: command not found ERROR while saving in vim

    My .vimrc file
    set expandtab
    set number
    syntax on
    set autoindent shiftwidth=4
    set smartindent
    set tabstop=4
    set smartcase
    colorscheme elflord
    set incsearch
    set hlsearch
    au BufWritePost * if getline(1) =~ "^#!" | if getline(1) =~ "/bin/" | silent !chmod +x <afile> | endif | endif
    " Tell vim to remember certain things when we exit
    " '10 : marks will be remembered for up to 10 previously edited files
    " "100 : will save up to 100 lines for each register
    " :20 : up to 20 lines of command-line history will be remembered
    " % : saves and restores the buffer list
    " n... : where to save the viminfo files
    set viminfo='10,\"100,:20,%,n~/.viminfo
    function! ResCur()
    if line("'\"") <= line("$")
    normal! g`"
    return 1
    endif
    endfunction
    augroup resCur
    autocmd!
    autocmd BufWinEnter * call ResCur()
    augroup END
    On some files, I get this error http://i.imgur.com/lKFvm.png at the bottom of vim . Please note that I get the error not on all files. Its driving me crazy!
    Last edited by shadyabhi (2011-09-11 02:41:52)

    Replace this:
    au BufWritePost * if getline(1) =~ "^#!" | if getline(1) =~ "/bin/" | silent !chmod +x <afile> | endif | endif
    with this:
    au BufWritePost * if getline(1) =~ "^#!" | if getline(1) =~ "/bin/" | silent execute "!chmod a+x <afile>" | endif | endif
    If the above doesn't work for you (though it should in Vim > 7), try a different way of doing the same thing:
    function ModeChange()
    if getline(1) =~ "^#!"
    if getline(1) =~ "/bin/"
    silent !chmod a+x <afile>
    endif
    endif
    endfunction
    au BufWritePost * call ModeChange()
    Last edited by bohoomil (2011-09-11 02:29:58)

  • MAKEPKG -c error - PKGBUILD: line 32: patch: command not found

    Hello all,
    Well I am getting the above error when running the makepkg -c as user in my local abs tree i am using
    [devnull@myhell chromium]$ makepkg -c
    ==> Making package: chromium 0.9.12-6  (Sun Mar 30 01:43:39 EDT 2008)
    ==> Checking Runtime Dependencies...
    ==> Checking Buildtime Dependencies...
    ==> Retrieving Sources...
      -> Found chromium-src-0.9.12.tar.gz in build dir
      -> Found chromium-data-0.9.12.tar.gz in build dir
      -> Found 0.9.12-gcc3-gentoo.patch in build dir
      -> Found 0.9.12-freealut.patch in build dir
      -> Found 0.9.12-configure.patch in build dir
      -> Found 0.9.12-png.patch in build dir
      -> Found chromium.sh in build dir
      -> Found chromium.png in build dir
      -> Found chromium.desktop in build dir
    ==> Validating source files with md5sums...
        chromium-src-0.9.12.tar.gz ... Passed
        chromium-data-0.9.12.tar.gz ... Passed
        0.9.12-gcc3-gentoo.patch ... Passed
        0.9.12-freealut.patch ... Passed
        0.9.12-configure.patch ... Passed
        0.9.12-png.patch ... Passed
        chromium.sh ... Passed
        chromium.png ... Passed
        chromium.desktop ... Passed
    ==> Extracting Sources...
      -> bsdtar -x -f chromium-src-0.9.12.tar.gz
      -> bsdtar -x -f chromium-data-0.9.12.tar.gz
    ==> Removing existing pkg/ directory...
    ==> Entering fakeroot environment...
    ==> Starting build()...
    PKGBUILD: line 32: patch: command not found
    ==> ERROR: Build Failed.
        Aborting...
    Here is a cut from PKBUILD file line 32:
    build(){
      cd $startdir/src/Chromium-0.9
      patch -p0 -i ../0.9.12-gcc3-gentoo.patch || return 1   <--- This is line 32 from pkbuild file
      patch -p0 -i ../0.9.12-freealut.patch || return 1
      #patch -p0 -i ../0.9.12-configure.patch || return 1
      patch -p0 -i ../0.9.12-png.patch || return 1
    Thanks you in advance for all your help

    Hello,
    /devnull.nsb wrote:
    Hello all,
    *snip*
    PKGBUILD: line 32: patch: command not found
    ==> ERROR: Build Failed.
        Aborting...
    *snip*
    It looks like you might not have patch installed.  What happens when you type
    pacman -Q patch
    If you get an error that the patch package is not found, install base-devel.

  • [SOLVED] Error uninstalling eclipse: "post-install: command not found"

    When I try uninstalling eclipse , I get "error: command failed to execute correctly"
    w0ng@e8500 ~
    % sudo pacman -Rns eclipse
    checking dependencies...
    Targets (8): glib-networking-2.30.2-1 gsettings-desktop-schemas-3.2.0-1 gstreamer0.10-0.10.36-1
    gstreamer0.10-base-0.10.36-1 libproxy-0.4.7-1 libsoup-2.36.1-1 libwebkit-1.6.3-1
    eclipse-3.7.2-2
    Total Removed Size: 243.84 MiB
    Do you want to remove these packages? [Y/n] y
    (1/8) removing eclipse [######################################] 100%
    /tmp/alpm_eY6rVO/.INSTALL: line 10: post-install: command not found
    error: command failed to execute correctly
    (2/8) removing libwebkit [######################################] 100%
    (3/8) removing libsoup [######################################] 100%
    (4/8) removing glib-networking [######################################] 100%
    (5/8) removing libproxy [######################################] 100%
    (6/8) removing gsettings-desktop-schemas [######################################] 100%
    No schema files found: removed existing output file.
    (7/8) removing gstreamer0.10-base [######################################] 100%
    (8/8) removing gstreamer0.10 [######################################] 100%
    w0ng@e8500 ~
    But all files appear to be removed successfully.
    w0ng@e8500 ~
    % sudo updatedb && locate eclipse
    /usr/share/highlight/themes/edit-eclipse.theme
    /usr/share/icons/Faenza/apps/16/eclipse.png
    /usr/share/icons/Faenza/apps/22/eclipse.png
    /usr/share/icons/Faenza/apps/24/eclipse.png
    /usr/share/icons/Faenza/apps/32/eclipse.png
    /usr/share/icons/Faenza/apps/48/eclipse.png
    /usr/share/icons/Faenza/apps/64/eclipse.png
    /usr/share/icons/Faenza/apps/96/eclipse.png
    /usr/share/icons/Faenza/apps/scalable/eclipse.svg
    /var/abs/community/eclipse-cdt
    /var/abs/community/eclipse-cdt/PKGBUILD
    /var/abs/core/licenses/eclipse-1.0.txt
    /var/abs/extra/eclipse
    /var/abs/extra/eclipse-ecj
    /var/abs/extra/eclipse/PKGBUILD
    /var/abs/extra/eclipse/eclipse.desktop
    /var/abs/extra/eclipse/eclipse.install
    /var/abs/extra/eclipse/eclipse.sh
    /var/abs/extra/eclipse/eclipse.svg
    /var/abs/extra/eclipse-ecj/PKGBUILD
    /var/abs/extra/eclipse-ecj/ecj
    w0ng@e8500 ~
    Should I be concerned or is everything fine? Can anyone reproduce this?
    Last edited by w0ng (2012-03-28 19:00:30)

    Check /var/abs/extra/eclipse/eclipse.install. Typo in post_remove: post-install should be post_install. You can run the post_install manually (and maybe report this in the bug tracker), but it just updates the gtk icon cache, so it's nothing to worry about.

  • Patch: command not found

    While trying to build freetype2-lcd with makepkg -c, I keep getting the following error:
    wiltell ~/build/freetype2-lcd  $ makepkg -c
    ==> Making package: freetype2-lcd 2.3.5-3  (Mon Mar 24 17:02:26 CET 2008)
    ==> Checking Runtime Dependencies...
    ==> Checking Buildtime Dependencies...
    ==> Retrieving Sources...
      -> Found freetype-2.3.5.tar.bz2 in build dir
      -> Found bytecode.patch in build dir
      -> Found freetype-2.3.0-enable-spr.patch in build dir
      -> Found freetype-2.2.1-enable-valid.patch in build dir
      -> Found freetype-2.2.1-memcpy-fix.patch in build dir
      -> Found freetype-2.2.1-subpixel-disable-quantization.diff in build dir
    ==> Validating source files with md5sums...
        freetype-2.3.5.tar.bz2 ... Passed
        bytecode.patch ... Passed
        freetype-2.3.0-enable-spr.patch ... Passed
        freetype-2.2.1-enable-valid.patch ... Passed
        freetype-2.2.1-memcpy-fix.patch ... Passed
        freetype-2.2.1-subpixel-disable-quantization.diff ... Passed
    ==> Extracting Sources...
      -> bsdtar -x -f freetype-2.3.5.tar.bz2
    ==> Removing existing pkg/ directory...
    ==> Entering fakeroot environment...
    ==> Starting build()...
    PKGBUILD: line 29: patch: command not found
    ==> ERROR: Build Failed.
        Aborting...

    When building packages, ensure you have the entire base-devel group installed:
    # pacman -S base-devel
    In particular for this specific case, what you want is the 'patch' program: 
    # pacman -S patch
    - but just install all of base-devel to prevent issues like this in the future.

  • Ldconfig: command not found

    I just did a pacman -Syu and something went terribly wrong.
    Whenever i try to install a new program i get something like this:
    $ pacman -S glibc
    warning: glibc-2.10.1-3 is up to date -- reinstalling
    resolving dependencies...
    looking for inter-conflicts...
    Targets (1): glibc-2.10.1-3
    Total Download Size: 0.00 MB
    Total Installed Size: 31.47 MB
    Proceed with installation? [Y/n]
    checking package integrity...
    (1/1) checking for file conflicts [##############################] 100%
    (1/1) upgrading glibc [##############################] 100%
    /tmp/alpm_ZLRuBH/.INSTALL: line 39: ldconfig: command not found
    /tmp/alpm_ZLRuBH/.INSTALL: line 40: init: command not found
    Generating locales...
    en_US.UTF-8... done
    en_US.ISO-8859-1... done
    Generation complete.
    sh: ldconfig: command not found
    error: command failed to execute correctly
    Checking the integrity of the local database in /var/lib/pacman/
    any ideas?

    Have all the users with GNOME started a root's Terminal window???
    I've noticed that using the Gnome's root terminal messes up the $PATH variable (as of today)... when i start archlinux (note: i don't use GDM) my path is:
    /bin:/usr/bin:/sbin:/usr/sbin....
    and many other items... but when a root terminal is started inside gnome, $PATH changes to:
    /usr/ucb:/bin:/usr/bin:/etc
    And ldconfig will fail... (and any other tool in /sbin) this change is restricted to this window only. If you exit the root terminal and go to a normal terminal, the path is what is expected.
    This happens on a clean reformatted machine, installed archlinux, doing a pacman -Syu, installing gnome and all extras (including system administrations tools) (as tested today).
    Maybe some config file is messed or is a bug from the Gnome guys...
    Anyways the only workaround i can think is to start a normal terminal (for the guys that use gnome or use GDM to start their machines) and in the terminal doing a "su -" to got root access (of course will ask for the password) and then update/install/whatever you want with pacman.
    And sorry about my english.
    J.
    Last edited by stargeizer (2009-09-24 14:35:10)

  • Docbook-to-man: command not found

    Good Day.
    I am having a small isse compliling flow-tools 0.68 on Solaris 5.10.
    Here is the error
    ...bunch of unintersting stuff...
    Making all in bin
    Making all in configs
    Making all in docs
    docbook-to-man flow-dscan.sgml > flow-dscan.1
    bash: docbook-to-man: command not found
    *** Error code 127
    make: Fatal error: Command failed for target `flow-dscan.1'
    Current working directory /Desktop/flow-tools-0.68/docs
    *** Error code 1
    The following command caused the error:
    set fnord $MAKEFLAGS; amf=$2; \
    dot_seen=no; \
    target=`echo all-recursive | sed s/-recursive//`; \
    list='lib src bin configs docs'; for subdir in $list; do \
      echo "Making $target in $subdir"; \
      if test "$subdir" = "."; then \
        dot_seen=yes; \
        local_target="$target-am"; \
      else \
        local_target="$target"; \
      fi; \
      (cd $subdir && make  $local_target) \
       || case "$amf" in *=*) exit 1;; *k*) fail=yes;; *) exit 1;; esac; \
    done; \
    if test "$dot_seen" = "no"; then \
      make  "$target-am" || exit 1; \
    fi; test -z "$fail"
    make: Fatal error: Command failed for target `all-recursive'Could I be missing something in my PATH? I am at a loss.

    Have you downloaded/compiled/installed docbook-to-man as it is not part of the Solaris distribution.
    If you have then add it's location to your $PATH.

Maybe you are looking for