02-17-2014
Quote:
Originally Posted by
c3rb3rus
I did notice the dependency hell on perilz which prevented me from getting Samba installed on the AIX OS, I was finding that it needed dependency A which needed dependency B, and so on the chain was huge.
Michael Perzl is probably the most structured worker i ever came across. Yes, that means that "packageA" really contains only A and not a iota of B, which might create a dependency to B, but you will come to appreciate the robustness and dependability his packages offer. Something unexpected practically never happens. This is arguably the best site for third-party AIX software and the packages are way better than the rpm-packages IBM itself offers.
Quote:
Originally Posted by
c3rb3rus
I was also succesful at removing Samba, however I did notice that using..
lssrc -g Samba config. remained behind, showing the samba group (nmbd, winbindd, and smbd services). perhaps the previous admin manually created the service group thus the removal did not take care of it.
hmm....
"lssrc" ist listing
running ("active") and
stopped ("inoperative") subsystems (~=daemons), not files. It is the interface to the "System Resource Controller" (SRC), a sort-of super-daemon. You will find some information here if you search for it.
It might well be that the previous admin created some users/groups himself. There are some easy commands to find out what belongs to where:
"lslpp -l" lists all installed packages in a long list
"lslpp -f <package-name>" lists all the files/directories belonging to the package
"lslpp -w <file>" lists the package a file belongs to (if any)
You can even "take apart" lpp-packages and look into their pre-/post-install-scripts, which would be responsible for creating users, groups and the like.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
Hi all,
I've got a question about an OS upgrade.
I'm planning to do a upgrade from AIX UNIX 4.3.2 to 4.3.3 in a few weeks.
I haven't got that much information.
Could someone give me some general tips or hints, things I should think of before? Things I should know, or general errors.
I know... (9 Replies)
Discussion started by: Erik Rooijmans
9 Replies
2. 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
3. AIX
Please help, I'm wicked... :confused:
I'm trying to get Samba to work on an IBM pseries machine (AIX 5.3) to provide access to the server for a user to retrieve reports from her WinXP desktop. I've made the proper entires in the smb.conf file and tried runing the smbpasswd command to add the user... (4 Replies)
Discussion started by: trandall
4 Replies
4. AIX
Hi All,
We are in the processing of upgrading our AIX server OS from 5.2.0.0 to 6.1. And we have a set of highly critical running C applications in AIX box. I have a question like whether this upgradation of OS will affect any C code compilation and C runtime enviornment...
how does AIX 6.1... (1 Reply)
Discussion started by: karthikc
1 Replies
5. AIX
Hi,
I am having 2 Hard disk one for os and another for data,I would like to know for Upgrading AIX 5.3 to 6.1,wheather I have to varry off datavg while upgrading, or any other files needs to be backup.
Please suggest
Regards,
Manoj (1 Reply)
Discussion started by: manoj.solaris
1 Replies
6. AIX
We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC.
Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers.
My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies
7. AIX
Hey guys,
since AIX 5.3 reaches EOS on april 2012, I really need to update my systems asap.
Any experience on upgrading directly to 7.1, with sap/db2/oracle?
could do fresh installs and import my sap/db vgs, but this would be a lot of work
cheers Funksen (4 Replies)
Discussion started by: funksen
4 Replies
8. AIX
Hi Folks,
Currently we are having the below configuration in one of our AIX 6.1 server.
RAM:- 8 GB
Paging space :- 19 GB
CPU processor:- 1
CPU type: 64 bit
But we would like to upgrade the configuration to below to improve the system performance and resolve some memory issues.
... (11 Replies)
Discussion started by: sumanmca2006
11 Replies
9. AIX
Hi all,
I have this weird notion that upgrading the TL does not cause the machine to wipe, but upgrading a major version (from aix 6 to 7) means it's actually a fresh install and will wipe the date and i have to install the software again (TSM server, for instance). Trying to google it, i came... (3 Replies)
Discussion started by: tde3000
3 Replies
10. AIX
I am running AIX 7.1 and currently we have samba 3.6.25 installed on the server. As it stands some AIX folders are shared that can be accessed by certain Windows users.
The problem is that since Windows 10 the guest feature no longer works so users have to manually type in their Windows login/pwd... (14 Replies)
Discussion started by: linuxsnake
14 Replies
LEARN ABOUT OSX
perlos400
PERLOS400(1) Perl Programmers Reference Guide PERLOS400(1)
NAME
perlos400 - Perl version 5 on OS/400
DESCRIPTION
This document describes various features of IBM's OS/400 operating system that will affect how Perl version 5 (hereafter just Perl) is
compiled and/or runs.
By far the easiest way to build Perl for OS/400 is to use the PASE (Portable Application Solutions Environment), for more information see
<http://www.iseries.ibm.com/developer/factory/pase/index.html> This environment allows one to use AIX APIs while programming, and it
provides a runtime that allows AIX binaries to execute directly on the PowerPC iSeries.
Compiling Perl for OS/400 PASE
The recommended way to build Perl for the OS/400 PASE is to build the Perl 5 source code (release 5.8.1 or later) under AIX.
The trick is to give a special parameter to the Configure shell script when running it on AIX:
sh Configure -DPASE ...
The default installation directory of Perl under PASE is /QOpenSys/perl. This can be modified if needed with Configure parameter
-Dprefix=/some/dir.
Starting from OS/400 V5R2 the IBM Visual Age compiler is supported on OS/400 PASE, so it is possible to build Perl natively on OS/400. The
easier way, however, is to compile in AIX, as just described.
If you don't want to install the compiled Perl in AIX into /QOpenSys (for packaging it before copying it to PASE), you can use a Configure
parameter: -Dinstallprefix=/tmp/QOpenSys/perl. This will cause the "make install" to install everything into that directory, while the
installed files still think they are (will be) in /QOpenSys/perl.
If building natively on PASE, please do the build under the /QOpenSys directory, since Perl is happier when built on a case sensitive
filesystem.
Installing Perl in OS/400 PASE
If you are compiling on AIX, simply do a "make install" on the AIX box. Once the install finishes, tar up the /QOpenSys/perl directory.
Transfer the tarball to the OS/400 using FTP with the following commands:
> binary
> site namefmt 1
> put perl.tar /QOpenSys
Once you have it on, simply bring up a PASE shell and extract the tarball.
If you are compiling in PASE, then "make install" is the only thing you will need to do.
The default path for perl binary is /QOpenSys/perl/bin/perl. You'll want to symlink /QOpenSys/usr/bin/perl to this file so you don't have
to modify your path.
Using Perl in OS/400 PASE
Perl in PASE may be used in the same manner as you would use Perl on AIX.
Scripts starting with #!/usr/bin/perl should work if you have /QOpenSys/usr/bin/perl symlinked to your perl binary. This will not work if
you've done a setuid/setgid or have environment variable PASE_EXEC_QOPENSYS="N". If you have V5R1, you'll need to get the latest PTFs to
have this feature. Scripts starting with #!/QOpenSys/perl/bin/perl should always work.
Known Problems
When compiling in PASE, there is no "oslevel" command. Therefore, you may want to create a script called "oslevel" that echoes the level
of AIX that your version of PASE runtime supports. If you're unsure, consult your documentation or use "4.3.3.0".
If you have test cases that fail, check for the existence of spool files. The test case may be trying to use a syscall that is not
implemented in PASE. To avoid the SIGILL, try setting the PASE_SYSCALL_NOSIGILL environment variable or have a handler for the SIGILL. If
you can compile programs for PASE, run the config script and edit config.sh when it gives you the option. If you want to remove fchdir(),
which isn't implement in V5R1, simply change the line that says:
d_fchdir='define'
to
d_fchdir='undef'
and then compile Perl. The places where fchdir() is used have alternatives for systems that do not have fchdir() available.
Perl on ILE
There exists a port of Perl to the ILE environment. This port, however, is based quite an old release of Perl, Perl 5.00502 (August 1998).
(As of July 2002 the latest release of Perl is 5.8.0, and even 5.6.1 has been out since April 2001.) If you need to run Perl on ILE,
though, you may need this older port: <http://www.cpan.org/ports/#os400> Note that any Perl release later than 5.00502 has not been ported
to ILE.
If you need to use Perl in the ILE environment, you may want to consider using Qp2RunPase() to call the PASE version of Perl.
AUTHORS
Jarkko Hietaniemi <jhi@iki.fi> Bryan Logan <bryanlog@us.ibm.com> David Larson <larson1@us.ibm.com>
perl v5.16.2 2012-10-11 PERLOS400(1)