Sponsored Content
Full Discussion: sshd not able to restart
Operating Systems Solaris sshd not able to restart Post 302540961 by beginningDBA on Friday 22nd of July 2011 04:47:38 AM
Old 07-22-2011
Hi, i get

Code:
# pkgadd -d /mnt/Product SUNWsshdr

Processing package instance <SUNWsshdr> from </mnt/Product>

SSH Server, (Root)
(sparc) 11.10.0,REV=2005.01.21.15.53
# ident "@(#)copyright  1.4     04/06/22 SMI"
Portions of code copyright by the following authors:

Copyright (c) 1992 Tatu Ylonen, Espoo, Finland
Copyright (c) 1995 Tatu Ylonen <ylo@cs.hut.fi>, Espoo, Finland
Copyright (c) 1998 CORE SDI S.A., Buenos Aires, Argentina.
Copyright (c) 1998 Free Software Foundation, Inc.                        *
Copyright (c) 1999-2004 Markus Friedl.  All rights reserved.
Copyright (c) 1999-2004 Damien Miller.  All rights reserved.
Copyright (c) 2000 Andre Lucas.  All rights reserved.
Copyright (c) 2000 Corinna Vinschen <vinschen@cygnus.com>, Duisburg, Germany
Copyright (c) 2000-2004 Niels Provos.  All rights reserved.

Copyright 2004 Sun Microsystems, Inc.  All rights reserved.
Use is subject to license terms.
Using </> as the package base directory.
## Processing package information.
## Processing system information.
WARNING: /lib <no longer a symbolic link>
   2 package pathnames are already properly installed.
## Verifying package dependencies.
WARNING:
    The <SUNWcakr> package "Core Solaris Kernel
    Architecture (Root)" is a prerequisite package and
    should be installed.
WARNING:
    The <SUNWckr> package "Core Solaris Kernel (Root)" is a
    prerequisite package and should be installed.
WARNING:
    The <SUNWcnetr> package "Core Solaris Network
    Infrastructure (Root)" is a prerequisite package and
    should be installed.

Do you want to continue with the installation of <SUNWsshdr> [y,n,?]

Code:
pkgadd -d /mnt/Product SUNWcakr
pkgadd: ERROR: no package associated with <SUNWcakr>

Do i install anyway? Or i have to try to find all the prerequisite package?
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sshd

i just downloaded and installed succesfully openssh server, and am running it on netbsd 1.5, i can not login with anyuser, i enabled root login just to see what happens and i can login as root, but no other user, i checked my config and most things are default, whats going on? has any one else had... (2 Replies)
Discussion started by: norsk hedensk
2 Replies

2. AIX

sshd restart

need some clarification: if i ssh to the server & i restart the sshd process, did my connection gone? one more thing, there are a few sshd processes in aix, how do i restart it all to read new config? using HUP? thanks in advance! (2 Replies)
Discussion started by: ashterix
2 Replies

3. AIX

It helps in the sshd on sshd.log

Friends, I made the installation of the ssh in the it conspires, I configured in the ssh_config the following parameters.. SyslogFacility AUTH LogLevel INFO that should generate sshd.log in the /var/log.... more no this generating. Somebody could help myself in... (0 Replies)
Discussion started by: sandba
0 Replies

4. UNIX for Dummies Questions & Answers

sshd question

Can someone tell me the difference between the (2) listed below: oracle pts/1 ip1 May1 7:11 9:11 oracle sshd ip1 May1 7:11 8:22 How do I read the above information, the fact that the row for pts/1 has a longer time duration than the row for sshd. Why is the... (2 Replies)
Discussion started by: banyan
2 Replies

5. AIX

SSHD does not start

I installed OpenSSH on AIX 5.1 but when I try to start it, it says: bash-2.05a# /usr/sbin/sshd bash-2.05a# bash-2.05a# tail /var/adm/syslog.out Jan 8 11:52:22 xyz sshd: fatal: Cannot bind any address. :confused: (31 Replies)
Discussion started by: untamed
31 Replies

6. Solaris

no sshd log

My ssh log appear to the screen which i want it to be log to /var/log/sshd.log how to log the sshd to /var/log? (5 Replies)
Discussion started by: hezry79
5 Replies

7. Solaris

sshd and AcceptEnv setting

Hello, On Linux the /etc/ssh/sshd_config has the "AcceptEnv" parameter which allows to "push" environment setting to a ssh session. For example, when I set in sshd_conf AcceptEnv BLAHI can then ssh to the server using: user@client~$ export BLAH=hello user@client~$ ssh server -o SendEnv=BLAH ... (2 Replies)
Discussion started by: RobertFord
2 Replies

8. Solaris

Doubt, sshd restart kills the session on Solaris 8,9,10

Hi Everyone, I am just curious, if sshd service is restarted on these OS Solaris 8,9,10 remotely will the session expires?? . I knew we can restart sshd in solaris 10 that will no effect any current session please suggest for 8,9 Thanks, (2 Replies)
Discussion started by: bobby320
2 Replies

9. Solaris

sshd and loginlog

I have shamelessly tried all the possible ways to see if my /var/adm/loginlog logs user access entries for ssh but nothing has worked for me so far..:confused: for telnet login its working fine. Adding auth.info in syslog.conf works but i dont want that output. Is there any way to edit... (2 Replies)
Discussion started by: ningy
2 Replies

10. Red Hat

Sshd - error

Hi, Do you know what cause the error message ? Nov 19 13:42:19 cfsasnd02 sshd: pam_env(sshd:setcred): non-alphanumeric key '-- /etc/environment' in /etc/environment', ignoring Nov 19 13:42:20 cfsasnd02 sshd: pam_env(sshd:setcred): non-alphanumeric key '-- /etc/environment' in... (0 Replies)
Discussion started by: xitrum
0 Replies
packagetoc(4)							   File Formats 						     packagetoc(4)

NAME
packagetoc - package table of contents description file DESCRIPTION
The package table of contents file, .packagetoc, is an ASCII file containing all of the information necessary for installing a product release distributed in package form. It centralizes and summarizes all of the relevant information about each package in the product. This allows the install software to quickly read one file to obtain all of the relevant information about each package instead of having to examine each package at run time to obtain this information. The .packagetoc file resides in the top-level directory containing the prod- uct. If a .packagetoc file exists for a product, there must also be a .order file. Each entry in the .packagetoc file is a line that establishes the value of a parameter in the following form: PARAM=value A line starting with a pound-sign, ``#'', is considered a comment and is ignored. Parameters are grouped by package. The start of a package description is defined by a line of the form: PKG=value There is no order implied or assumed for specifying the parameters for a package with the exception of the PKG parameter, which must appear first. Only one occurrence of a parameter is permitted per package. The parameters recognized are described below. Those marked with an asterisk are mandatory. PKG* The package identifier, for example, SUNWaccu. The maximum length of the identifier is nine characters. All the characters must be alphanumeric. The first character must be alphabetic. install, new, and all are reserved iden- tifiers. PKGDIR* The name of the directory containing the package. This directory is relative to the directory containing the prod- uct. NAME* The full name of the package. VENDOR The name of the package's vendor. VERSION The version of the package. PRODNAME The name of the product to which this package belongs. PRODVERS The version of the product to which this package belongs. SUNW_PKGTYPE The package type. Valid values are: root indicates that the package will be installed in the / file system. The root packages are the only packages installed during dataless client installations. The root packages are spooled during a server installa- tion to allow the later installation of diskless clients. usr indicates that the package will be installed in the /usr file system. kvm indicates that the package will be installed in the /usr/platform file system. ow indicates a package that is part of the bundled OpenWindows product release. If no SUNW_PKGTYPE macro is present, the package is assumed to be of type usr. ARCH* The architecture(s) supported by the package. This macro is taken from the package's pkginfo(4) file and is sub- ject to the same length and formatting constraints. The install program currently assumes that exactly one architecture token is specified for a package. For example, ARCH=sparc.sun4u is acceptable, but ARCH=sparc.sun4u, sparc.sun4m is not. DESC A detailed textual description of the package. BASEDIR* The default installation base directory of the package. SUNW_PDEPEND A dependency specification for a prerequisite package. Each prerequisite dependency must appear as a separate macro. See depend(4) for more information on dependencies and instance specifications. SUNW_IDEPEND A dependency specification for an incompatible package. Each incompatible dependency should appear as a separate macro. See depend(4) for more information on dependencies and instance specifications. SUNW_RDEPEND A dependency specification for a reversed package dependency. Each reverse dependency should appear as a separate macro. See depend(4) for more information on dependencies and instance specifications. CATEGORY The category of the package. SUNW_LOC Indicates that this package contains localizations for other packages. Such localization packages are treated as special case packages. Each package which has a SUNW_LOC macro must have a corresponding SUNW_PKGLIST macro. The value specified by this macro should be a valid locale. SUNW_PKGLIST A comma separated list of package identifiers. Currently this macro is used to indicate which packages are local- ized by a localization package. ROOTSIZE* The space used by the package in the / file system. USRSIZE* The space used by the package in the /usr subtree of the file system. VARSIZE* The space used by the package in the /var subtree of the file system. OPTSIZE* The space used by the package in the /opt subtree of the file system. EXPORTSIZE* The space used by the package in the /export subtree of the file system. USROWNSIZE* The space used by the package in the /usr/openwin subtree of the file system. SPOOLEDSIZE* The space used by the spooled version of this package. This is used during the setup of a server by the initial system installation programs. All sizes are specified in bytes. Default disk partitions and file system sizes are derived from the values provided: accuracy is impor- tant. EXAMPLES
Example 1: A Sample .packagetoc File The following is an example package entry in a .packagetoc file. #ident "@(#)packagetoc.4 1.2 92/04/28" PKG=SUNWaccr PKGDIR=SUNWaccr NAME=System Accounting, (Root) VENDOR=Sun Microsystems, Inc. VERSION=8.1 PRODNAME=SunOS PRODVERS=5.0beta2 SUNW_PKGTYPE=root ARCH=sparc DESC=System Accounting, (Root) BASEDIR=/ CATEGORY=system ROOTSIZE=11264 VARSIZE= 15360 OPTSIZE=0 EXPORTSIZE=0 USRSIZE=0 USROWNSIZE=0 SEE ALSO
cdtoc(4), clustertoc(4), depend(4), order(4), pkginfo(4), pkgmap(4) NOTES
The parameters NAME, VENDOR, VERSION, PRODNAME, PRODVERS, SUNW_PKGTYPE, SUNW_LOC, SUNW_PKGLIST, ARCH, DESC, BASEDIR, and CATEGORY are assumed to have been taken directly from the package's pkginfo(4) file. The length and formatting restrictions placed on the values for these parameters are identical to those for the corresponding entries in the pkginfo(4) file. The value specified for the parameter PKGDIR should not exceed 255 characters. The value specified for the parameters ROOTSIZE, VARSIZE, OPTSIZE, EXPORTSIZE, USRSIZE and USROWNSIZE must be a single integer value. The values can be derived from the package's pkgmap file by counting all space consumed by any files installed in the applicable file system. The space includes that used for directory entries and any UFS overhead that exists because of the way the files are represented (directory allocation scheme; direct, indirect, double indirect blocks; fragments; etc.) The following kinds of entries in the pkgmap(4) file should be included in the space derivation: f regular file c character special file b block special file p pipe l hard link s symbolic link x, d directory i packaging installation script or information file (copyright, depend, postinstall, postremove) SunOS 5.10 19 Nov 2002 packagetoc(4)
All times are GMT -4. The time now is 12:38 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy