Sponsored Content
Top Forums Shell Programming and Scripting AIX subsystem stops partially Post 303044601 by sea on Thursday 27th of February 2020 12:57:27 PM
Old 02-27-2020
One could assign the logfile to the user as well....

Code:
touch "$LOGFILE"
chown 206 "$LOGFILE"

Since root can write anyway, this would help to ensure that this specific user can write to the logfile as well.

Written on mobile phone in train.

Just an idea.
Hth
 

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
cback-span(1)						       Kenneth J. Pronovici						     cback-span(1)

NAME
cback-span - Span staged data among multiple discs SYNOPSIS
cback-span [switches] DESCRIPTION
This is the Cedar Backup span tool. It is intended for use by people who back up more data than can fit on a single disc. It allows a user to split (span) staged data between more than one disc. It can't be a Cedar Backup extension in the usual sense because it requires user input when switching media. Generally, one can run the cback-span command with no arguments. This will start it using the default configuration file, the default log file, etc. You only need to use the switches if you need to change the default behavior. This command takes most of its configuration from the Cedar Backup configuration file, specifically the store section. Then, more informa- tion is gathered from the user interactively while the command is running. SWITCHES
-h, --help Display usage/help listing. -V, --version Display version information. -b, --verbose Print verbose output to the screen as well writing to the logfile. When this option is enabled, most information that would normally be written to the logfile will also be written to the screen. -c, --config Specify the path to an alternate configuration file. The default configuration file is /etc/cback.conf. -l, --logfile Specify the path to an alternate logfile. The default logfile file is /var/log/cback.log. -o, --owner Specify the ownership of the logfile, in the form user:group. The default ownership is root:adm, to match the Debian standard for most logfiles. This value will only be used when creating a new logfile. If the logfile already exists when the cback script is executed, it will retain its existing ownership and mode. Only user and group names may be used, not numeric uid and gid values. -m, --mode Specify the permissions for the logfile, using the numeric mode as in chmod(1). The default mode is 640 (-rw-r-----). This value will only be used when creating a new logfile. If the logfile already exists when the cback script is executed, it will retain its existing ownership and mode. -O, --output Record some sub-command output to the logfile. When this option is enabled, all output from system commands will be logged. This might be useful for debugging or just for reference. Cedar Backup uses system commands mostly for dealing with the CD recorder and its media. -d, --debug Write debugging information to the logfile. This option produces a high volume of output, and would generally only be needed when debugging a problem. This option implies the --output option, as well. -s, --stack Dump a Python stack trace instead of swallowing exceptions. This forces Cedar Backup to dump the entire Python stack trace associ- ated with an error, rather than just progating last message it received back up to the user interface. Under some circumstances, this is useful information to include along with a bug report. RETURN VALUES
This command returns 0 (zero) upon normal completion, and six other error codes related to particular errors. 1 The Python interpreter version is < 2.5. 2 Error processing command-line arguments. 3 Error configuring logging. 4 Error parsing indicated configuration file. 5 Backup was interrupted with a CTRL-C or similar. 6 Other error during processing. NOTES
Cedar Backup itself is designed to run as root, since otherwise it's difficult to back up system directories or write the CD or DVD device. However, this command can be run safely as any user that has read access to the Cedar Backup staging directories and write access to the CD or DVD device. SEE ALSO
cback(1) FILES
/etc/cback.conf - Default configuration file /var/log/cback.log - Default log file BUGS
Report bugs to <support@cedar-solutions.com>. AUTHOR
Written by Kenneth J. Pronovici <pronovic@ieee.org>. COPYRIGHT
Copyright (c) 2007,2010 Kenneth J. Pronovici. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. Cedar Backup July 2010 cback-span(1)
All times are GMT -4. The time now is 07:22 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy