01-31-2012
Typically, /usr/sbin/ will not be included in the PATH of the most basic shell environments. Try modifying the startup script for sshd and adding that directory to the PATH before starting the sshd daemon and see if that fixes your issue.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
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. AIX
Hi,
While I am trying SFTP my machine to another unix machine ,
it was working fine till 10 min back.
But now i am getting the below error
"Request for subsystem 'sftp' failed on channel 0"
Could you please someone help me to solve or analyise the root cause...
Cheers:b:,
Mahiban (0 Replies)
Discussion started by: mahiban
0 Replies
3. UNIX for Advanced & Expert Users
All,
I enabled PAM and aged a password, but when I login it asks me for the current password then says password unchanged after entering the current password. Is this a bug? My security dept is going to want me to enable password aging and I'm stuck!
Any help on what the issu is?
... (6 Replies)
Discussion started by: markdjones82
6 Replies
4. UNIX for Dummies Questions & Answers
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
5. UNIX for Dummies Questions & Answers
I have identical scripts on two machines: one a laptop running Ubuntu 9.04, and the other a Windows XP desktop running Cygwin. The files I'd like to process are on the Windows machine. Running the script in Cygwin engages eight calls to an external executable and spins off who knows how many forks... (1 Reply)
Discussion started by: SilversleevesX
1 Replies
6. UNIX for Advanced & Expert Users
Folks,
I am trying to solve the following problem. I have a process on machine A running as root that needs to mount and access an NFS partition being exported from machine B.
However, I cannot have 'no_root_squash' option given on B, hence I see NFS requests from machine A end up as 'nobody'... (1 Reply)
Discussion started by: helpmelearn
1 Replies
7. HP-UX
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
LEARN ABOUT DEBIAN
btraceback
BTRACEBACK(1) Network backup, recovery and verification BTRACEBACK(1)
NAME
btraceback - wrapper script around gdb and bsmtp
SYNOPSIS
btraceback /path/to/binary pid
DESCRIPTION
btraceback is a wrapper shell script around the gdb debugger (or dbx on Solaris systems) and bsmtp, provided for debugging purposes.
USAGE
btraceback is called by the exception handlers of the Bacula daemons during a crash. It can also be called interactively to view the cur-
rent state of the threads belonging to a process, but this is not recommended unless you are trying to debug a problem (see below).
NOTES
In order to work properly, debugging symbols must be available to the debugger on the system, and gdb, or dbx (on Solaris systems) must be
available in the $PATH.
If the Director or Storage daemon runs under a non-root uid, you will probably need to be modify the btraceback script to elevate privi-
leges for the call to gdb/dbx, to ensure it has the proper permissions to debug when called by the daemon.
Although Bacula's use of btraceback within its exception handlers is always safe, manual or interactive use of btraceback is subject to the
same risks than live debugging of any program, which means it could cause Bacula to crash under rare and abnormal circumstances. Conse-
quently we do not recommend manual use of btraceback in production environments unless it is required for debugging a problem.
ENVIRONMENT
btracback relies on $PATH to find the debugger.
FILES
/usr/lib/bacula/btraceback
The script itself.
/usr/sbin/btraceback
symbolic link to /usr/lib/bacula/btraceback
/etc/bacula/scripts/btraceback.gdb
the GDB command batch used to output a stack trace
AUTHOR
This manual page was written by Lucas B. Cohen <lbc@members.fsf.org>
SEE ALSO
bsmtp(1)
Kern Sibbald 6 December 2009 BTRACEBACK(1)