Sponsored Content
Top Forums Shell Programming and Scripting AIX subsystem stops partially Post 303044578 by Neo on Thursday 27th of February 2020 01:11:49 AM
Old 02-27-2020
Normally when people experience a problem between running a script successfully as one user, and then having issues with the same script under another user, the issues are generally resolved by:
  • Make your you use full path names in all scripts and commands in your scripts.
  • Make sure any environmental variable you use in your scripts are the same for both users.
  • Make sure all users have appropriate read/write/execute file permissions.

This "different users" problems we see generally are easy to resolve if when folks start with the three bullet points above.

The most command mistakes in similar situations across all OS over the years is caused by not using full paths for files and commands.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

NFS client subsystem hang up on boot

Hi, I have a Unix box running HP-UX 10.20 and it suddenly won't boot. Every time it goes down the boot checklist, it hangs on "NFS client subsystem" and just continues to say busy/wait. I have read something about the /etc/auto_master but don't quite understand what has to happen to fix it. ... (4 Replies)
Discussion started by: Asheley Ryan
4 Replies

2. UNIX for Advanced & Expert Users

subsystem failure

aix 4.3 I get the following error from the errpt log BD797922 0306170008 P H enclosure0 SUBSYSTEM FAILURE I'm not clear on this kind of error. It never happened to me. What do this errors mean, and how do I clear or solve them? Any help is appreciated. (2 Replies)
Discussion started by: andwhat
2 Replies

3. AIX

Subsystem Component Failure

Hello All, Does some one have any idea about the subsystem component failure. Errpt command throws below errors for my server :- # errpt IDENTIFIER TIMESTAMP T C RESOURCE_NAME DESCRIPTION B9735AF4 0304222408 P H hdisk5 SUBSYSTEM COMPONENT FAILURE B9735AF4 0304222408 P H... (1 Reply)
Discussion started by: Shrek
1 Replies

4. AIX

Generating a Subsystem

Hello, I'm trying to generate a subsystem which supports startsrc, stopsrc and refresh I want to specify special arguments in case of stopsrc and refresh for example: startsrc: /bin/testscript start stopsrc: /bin/testscript stop refresh: /bin/testscript restart which should be... (0 Replies)
Discussion started by: funksen
0 Replies

5. AIX

AIX 5.3 ML10 new install, rsh only partially working

Two boxes we just reloaded to use as a two node HACMP cluster to insure our software is compatible. Install disks we received at our library on 5/2009 AIX 5.3-ML10 For sake of argument names ibmaix1 and ibmaix2 On both: ibmaix1# oslevel -r 5300-10 .rhosts files with 600 permissions... (0 Replies)
Discussion started by: DrKillPatient
0 Replies

6. Ubuntu

Getting Subsystem ID/Vendor

Hey Guys ... How I can look up Subsystem ID of the WIFI card under Ubuntu... I did try lspci but its outputting only Vendor and Dev no subsys ... I need same data as below ( Windows ) PCI\VEN_168C&DEV_001C&SUBSYS_04281468&REV_01\4&1BF192B7&0&0020 thank you happy new year ! (2 Replies)
Discussion started by: NDxiak
2 Replies

7. UNIX for Dummies Questions & Answers

SFTP subsystem requests

Hi there, what is the meaning of this line: SFTP subsystem requests: 5 Time(s) in: /var/mail/root??? Tks in advance, GB (0 Replies)
Discussion started by: Giordano Bruno
0 Replies

8. AIX

sftp : have to specify subsystem from client side

I have several ssh servers *running aix 5.3 and they respond to sftp requests just fine, but I have one that requires clients to specify the path to the sftp server using the -s flag which is*/usr/sbin/sftp-server I check the sshd_config across all servers and they are the same. *The other... (1 Reply)
Discussion started by: massdesign
1 Replies

9. HP-UX

[HP UNIX B.10.20] NFS Client SubSystem fail

Recently moved a HP Unix B.10.20 system from US to Thailand, and everything is work well in US but after we changed: 1. set_parms ip_address (change the IP to TH range) 2. set_parms addl_netwrk (change the Subnet, Gateway, Domain name, DNS Svr Name, and DNS IP) 3. vi /etc/hosts (to commented... (4 Replies)
Discussion started by: beta911
4 Replies

10. AIX

AIX 7.1 booting stops at C1922000 C19220FF

Hi, we have the p6 server running AIX 7.1 it suddenly stops working. I tried to re-cycle power but it keeps stopping at C19220FF. Activate the service processor pinhole reset switch but still stops at the same code. Error logs: 1. 501A1181 2016-06-08 22:06:20 'Service Process'... (1 Reply)
Discussion started by: lilyn
1 Replies
DH_INSTALLINIT(1)						     Debhelper							 DH_INSTALLINIT(1)

NAME
dh_installinit - install init scripts and/or upstart jobs into package build directories SYNOPSIS
dh_installinit [debhelperoptions] [--name=name] [-n] [-R] [-r] [-d] [--params] DESCRIPTION
dh_installinit is a debhelper program that is responsible for installing init scripts with associated defaults files, as well as upstart job files into package build directories. It also automatically generates the postinst and postrm and prerm commands needed to set up the symlinks in /etc/rc*.d/ to start and stop the init scripts. FILES
debian/package.init If this exists, it is installed into etc/init.d/package in the package build directory. debian/package.default If this exists, it is installed into etc/default/package in the package build directory. debian/package.upstart If this exists, it is installed into etc/init/package.conf in the package build directory. OPTIONS
-n, --noscripts Do not modify postinst/postrm/prerm scripts. -o, --onlyscripts Only modify postinst/postrm/prerm scripts, do not actually install any init script, default files, or upstart job. May be useful if the init script or upstart job is shipped and/or installed by upstream in a way that doesn't make it easy to let dh_installinit find it. -R, --restart-after-upgrade Do not stop the init script until after the package upgrade has been completed. This is different than the default behavior, which stops the script in the prerm, and starts it again in the postinst. This can be useful for daemons that should not have a possibly long downtime during upgrade. But you should make sure that the daemon will not get confused by the package being upgraded while it's running before using this option. -r, --no-restart-on-upgrade Do not stop init script on upgrade. --no-start Do not start the init script on install or upgrade, or stop it on removal. Only call update-rc.d. Useful for rcS scripts. -d, --remove-d Remove trailing d from the name of the package, and use the result for the filename the upstart job file is installed as in etc/init/ , and for the filename the init script is installed as in etc/init.d and the default file is installed as in etc/default/ . This may be useful for daemons with names ending in d. (Note: this takes precedence over the --init-script parameter described below.) -uparams --update-rcd-params=params -- params Pass params to update-rc.d(8). If not specified, defaults will be passed to update-rc.d(8). --name=name Install the init script (and default file) as well as upstart job file using the filename name instead of the default filename, which is the package name. When this parameter is used, dh_installinit looks for and installs files named debian/package.name.init, debian/package.name.default and debian/package.name.upstart instead of the usual debian/package.init, debian/package.default and debian/package.upstart. --init-script=scriptname Use scriptname as the filename the init script is installed as in etc/init.d/ (and also use it as the filename for the defaults file, if it is installed). If you use this parameter, dh_installinit will look to see if a file in the debian/ directory exists that looks like package.scriptname and if so will install it as the init script in preference to the files it normally installs. This parameter is deprecated, use the --name parameter instead. This parameter is incompatible with the use of upstart jobs. --error-handler=function Call the named shell function if running the init script fails. The function should be provided in the prerm and postinst scripts, before the #DEBHELPER# token. NOTES
Note that this command is not idempotent. dh_prep(1) should be called between invocations of this command. Otherwise, it may cause multiple instances of the same text to be added to maintainer scripts. SEE ALSO
debhelper(7) This program is a part of debhelper. AUTHORS
Joey Hess <joeyh@debian.org> Steve Langasek <steve.langasek@canonical.com> 9.20120909 2012-04-10 DH_INSTALLINIT(1)
All times are GMT -4. The time now is 07:10 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy