02-15-2012
Installing SAMBA problems
I have created an LPAR and the next step is to get SAMBA installed, I have mounted our NIM server up and copied over the SAMBA binaries .bff files. How do i install these? i tried doing this through SMIT but had no luck..? Any help would be greatly appreciated. AIX OS 6.1
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
i am run SUSE 6.4 with apache that i built and maintain to serve my dads website, (www.farragutmarine.com for anyone who cares) anyway i am running samba and i have a huge problem, throughout the day, everything goes fine, but then my server will come to a grinding halt, if i try to telnet in or... (4 Replies)
Discussion started by: norsk hedensk
4 Replies
2. UNIX for Dummies Questions & Answers
Hi all,
I am under Sun Solaris 10, and I wan't to use printers which are on my local area network (on Windows XP workstation), I have got samba installed, and cups.
I wan't to have an easy way for printing document (with StarOffice, Gimp etc...), for exemple by just launching a command.
... (0 Replies)
Discussion started by: willits
0 Replies
3. Solaris
Hello all
I am trying to install sara-sans(http://www.cisecurity.org/top20.htm) on a Solaris 9 server. The process highly recommends the installation of samba-tng suite. In the process of installaing samba-tng, "./configure" went smooth. After that while trying to 'make', it is stopped with the... (0 Replies)
Discussion started by: chrs0302
0 Replies
4. AIX
Hello, I need assistance installing Samba on AIX 5.3 TL06. Smitty Install produces the following error message:
Command: failed stdout: yes stderr: no
Before command completion, additional instructions may appear below.
geninstall -I "a -cgNQqwXY -J" -Z -d... (5 Replies)
Discussion started by: tgray71
5 Replies
5. Solaris
i am a rookie so please give every detail... i need help installing samba on my solaris 8 (intel) box so i can share with WXP box. i can get online, but can only see websites as outline\text form but managed to download "samba-latest.tar.z" is this correct? and what is next step to get it up and... (1 Reply)
Discussion started by: flir11
1 Replies
6. UNIX for Advanced & Expert Users
Hi I have an issue with a client. He was able to use his mounted Samba share for a long time. However, a couple of days ago, he wasn't able to access all of his files all of a sudden. He still see's the share and majority of the files, but not some that he needs.
I checked with Secure CRT on... (1 Reply)
Discussion started by: zixzix01
1 Replies
7. Red Hat
Hi,
I have installed RHEL 5.2 for a specific reason.
Anyway I would really like to use SWAT to administer Samba. Samba is currently installed and working almost successfully however SWAT would make life a bit easier.
I have tried rpm -ivh samba-swat but it can't find the file. ... (1 Reply)
Discussion started by: drag0n
1 Replies
8. Solaris
Hi all, I'm trying to update my samba 3.5.10 to 3.6.5 due to security CVE issued with 3.5.
I downloaded and unzipped, did the make and make install and the ./configure.
I didn't use any changes to it and it said it installed correctly added it to my path and it looks like it's operating... (6 Replies)
Discussion started by: mattymatt79
6 Replies
9. UNIX for Dummies Questions & Answers
I have made a complete botch of trying to install both ssh and samba, having followed numerous tutorials - all claiming to be easy to follow and stating that it is easy.
The last attempt @ ssh was going really well until the copy id stage
roy@roy-1011PX:~$ ssh-copy-id -i /home/roy/.ssh/id_dsa.pub... (8 Replies)
Discussion started by: Royalist
8 Replies
LEARN ABOUT OPENDARWIN
install
INSTALL(1) BSD General Commands Manual INSTALL(1)
NAME
install -- install binaries
SYNOPSIS
install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 file2
install [-bCcMpSsv] [-B suffix] [-f flags] [-g group] [-m mode] [-o owner] file1 ... fileN directory
install -d [-v] [-g group] [-m mode] [-o owner] directory ...
DESCRIPTION
The file(s) are copied to the target file or directory. If the destination is a directory, then the file is copied into directory with its
original filename. If the target file already exists, it is either renamed to file.old if the -b option is given or overwritten if permis-
sions allow. An alternate backup suffix may be specified via the -B option's argument.
The options are as follows:
-b Back up any existing files before overwriting them by renaming them to file.old. See -B for specifying a different backup suffix.
-B suffix
Use suffix as the backup suffix if -b is given.
-C Copy the file. If the target file already exists and the files are the same, then don't change the modification time of the target.
If the target's file flags and mode need not to be changed, the target's inode change time is also unchanged.
-c Copy the file. This is actually the default. The -c option is only included for backwards compatibility.
-d Create directories. Missing parent directories are created as required.
-f Specify the target's file flags; see chflags(1) for a list of possible flags and their meanings.
-g Specify a group. A numeric GID is allowed.
-M Disable all use of mmap(2).
-m Specify an alternate mode. The default mode is set to rwxr-xr-x (0755). The specified mode may be either an octal or symbolic
value; see chmod(1) for a description of possible mode values.
-o Specify an owner. A numeric UID is allowed.
-p Preserve the access and modification times. Copy the file, as if the -C (compare and copy) option is specified, except if the target
file doesn't already exist or is different, then preserve the access and modification times of the source file.
-S Safe copy. Normally, install unlinks an existing target before installing the new file. With the -S flag a temporary file is used
and then renamed to be the target. The reason this is safer is that if the copy or rename fails, the existing target is left
untouched.
-s install exec's the command strip(1) to strip binaries so that install can be portable over a large number of systems and binary
types.
-v Cause install to be verbose, showing files as they are installed or backed up.
By default, install preserves all file flags, with the exception of the ``nodump'' flag.
The install utility attempts to prevent moving a file onto itself.
Installing /dev/null creates an empty file.
DIAGNOSTICS
The install utility exits 0 on success, and >0 if an error occurs.
FILES
INS@XXXX If either -S option is specified, or the -C or -p option is used in conjuction with the -s option, temporary files named INS@XXXX,
where XXXX is decided by mkstemp(3), are created in the target directory.
COMPATIBILITY
Historically install moved files by default. The default was changed to copy in FreeBSD 4.4.
SEE ALSO
chflags(1), chgrp(1), chmod(1), cp(1), mv(1), strip(1), mmap(2), chown(8)
HISTORY
The install utility appeared in 4.2BSD.
BUGS
Temporary files may be left in the target directory if install exits abnormally.
File flags cannot be set by fchflags(2) over a NFS file system. Other file systems do not have a concept of flags. The install utility will
only warn when flags could not be set on a file system that does not support them.
The install utility with -v falsely says a file is copied when -C snaps hard links.
BSD
May 7, 2001 BSD