similar to: scp doesn't work with sshd 2.5.1p1 on Solaris 2.6

Hi there, I have a problem when I try to create a new user with swat. I use binaries of Samba 2.2.2 coming from www.samba.org, or from www.sunfreeware.com on Solaris 2.6 and on 8. I compiled the sources and the result is the same. When I click on "Add New User" (Server Password Management), I receive a nearly blank page: I can only see the samba gif on top and the user is not

I built OpenSSH as a 64-bit binary on Solaris 9, using gcc 3.3.2, OpenSSL 0.9.7c and zlib 1.2.1. sshd starts up normally, and will begin the login session, however, some time after it reads /etc/default/login, it faults and kills the connection. There are no error messages logged to syslog (with LogLevel set to DEBUG) or with the -ddd option. Here's a truss of the failure: 8132:

Is the following a known problem: =============================================================== [2000/01/26 09:41:03, 0] lib/fault.c:fault_report(41) INTERNAL ERROR: Signal 11 in pid 22273 (2.0.6) Please read the file BUGS.txt in the distribution [2000/01/26 09:41:03, 0] lib/fault.c:fault_report(43) =============================================================== This is using the same

HP-UX 11 is looping on SIGCHLD/sigchld_handler2() when exiting a protocol 2 session apparently because we don't call wait before reinstalling the handler. Any thoughts on this issue or how to address it? serverloop.c from latest snapshots: void sigchld_handler2(int sig) { int save_errno = errno; debug("Received SIGCHLD."); child_terminated = 1; signal(SIGCHLD,

I've got an rsync job which is consistently failing, but I've been unable to diagnose the problem. FAQ/Google/docs/etc. checked and no luck. Basically, it looks like the rsync process invoked on the far end is exiting, and then the local process waits until the timeout and exits. Both systems are Sun boxes, Ultra 10 or better with 256+ MB of memory. Rsync version is 2.5.0 on the local

Hello, I have compiled rsync 2.5.0 cleanly on a Solaris 2.6 box, and can use the resultant binary as a client with no problem. However, when I try and start a daemon, it exits with exit code 0, and no daemon running. I have previously run 2.4.6 and other versions with the same rsyncd.conf file, but can't seem to get the daemon up with 2.5.0. A truss shows the following: # truss -f

using openssh-3.8.1p1 from sunfreeware.com on a SunOS XXX 5.8 Generic_117000-03 sun4u sparc SUNW,Sun-Fire-V240. sshd seems to ignore or miss SIGCLD. this is a rare behaviour we observe about once per week in a ssh intensive environment. the process hangs here: truss: 24453: poll(0xFFBEEF28, 2, -1) (sleeping...) gcore, mdb: libc.so.1`_poll+4(b, 0, 0, ffbeef38, 6fc40,

openssh 3.7p1 sshd on Solaris 8 / sparcv9: sshd runs fine, and starts to allow the login. However, when reading from /etc/default/login, I get a bus error. I am able to get sshd to work by commenting out these lines in session.c: 1015,1018c1015 < # ifdef HAVE_ETC_DEFAULT_LOGIN < read_etc_default_login(&env, &envsize, pw->pw_uid); < path =

I am having problems setting up the smbpasswd command to sync the /etc/passwd and $SAMBAHOME/private/smbasswd files. My passwd program (/usr/bin/passwd %u) doesn't seem to want to wait around for smbpasswd to send it a second password for confirmation. I am running Solaris 2.5.1 (103640-23) on an Ultra 2300 and using Samba 1.9.18p10 compiled with gcc 2.8.1. I thought that I had this running

Hi guys, I've a problem with telnet sessions under Solaris 8 with samba 3.0.23d winbind. If I have the winbind authorization active for telnet in my pam.conf I got a kick out of the system after exactly 300 sec, no mather if I do or do not activity on the telnet session. The same behavior is for AD and for local users. I've trussed a telnet session a the only thing I see is that my

Hi, We upgraded from 3.7.1p2 to 3.9p1. The behaviour of the X11 forwarding changed significantly, it is much slower. See below the truss output (server side which runs 3.7.1p2) an check for the timestamp (6 seconds delay). Do you have any idea what may causes this behaviour? Platform is Solaris 5.9 Generic_117171-05. Thanks in advance, Andy Kocher 19279: 9.5463 sigaction(SIGCLD,

This patch fixes my botched attempted to patch deattack.c. I created a bsd-cray.h file and cleaned up a few error cases in bsd-cray.c. Fixed cray_setup call to pass uid and login name in session.c and moved its call so that its called with root privs. Its been tested on a irix, sun, aix, unicos(SV1) and unicosmk(T3E) systems. If you are building this on a T3E you may have to edit the Makefile

Hello, We discovered a slight problem with rsync 2.6.8 on HP-UX 11.23 on Itanium2. When trying to get a directory listing via: # oracle@DEV1[]:/~ > rsync dev1::deploy drwxr-xr-x 96 2006/09/06 12:57:36 . drwxrwxrwx 96 2006/09/11 15:35:33 test # ... it works flawlessly, but when trying to get a subdirectory we get the following error: # DEV1:/etc# rsync dev1::deploy/test #

Commit-ID: 93ae53d4cde3d461f987804e9bb3f2291c59c30f Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=93ae53d4cde3d461f987804e9bb3f2291c59c30f Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Sat, 19 May 2018 02:39:41 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:55 +0000 [klibc] dash: jobs: Only

hi guys We use rsync extensively in keeping the site resources in synch across redundant infrastructure. While attempting rsync for one of the boxes we find that the rsync process simply sleeps. The situation remains the same even if we have sync very small contents of the order of 4 KB. The same run with the -an flag runs without any issues. We run rsync over ssh on solaris boxes. To debug the

samba-2.0.0beta5 built on Solaris 2.5 with gcc-2.7.2 running on Solaris 2.5.1 I'm trying to track down a problem I'm having using unix password sync in samba-2.0.0beta5. I've noticed some funkiness with the SIGCLD handling in smbd/chgpasswd.c. It seems that after an smbpasswd is run and unix password sync is being used, an smbd is left behind, rapidly spinning it wheels. A truss of

hello applied the patch described below - unfortunately we still experience rare hangs of the remote sshd. not surprising as the patch only changes a few lines in server_loop() - but not in server_loop2() which i used for non-interactive sessions. process id of hanging sshd: 26110 process is sleeping forever in poll (why does server_loop2() sleep forever?): root at XXX:~# truss -fp 26110 26110:

Hi all, I've just set up password encryption using 1.9.18p4. I compiled with NO ALLOW_CHANGE_PASSWORD option because compilation didn't work (I'm using HP-UX 10.20). Everything seems to be working correctly instead of a 'normal' user trying to change his (samba-) password using smbpasswd (root can change any password). The messages I receive are as follows: Old SMB password:

Platform is Solaris 8 on a 280R. I'm setting up a new installation of Dovecot, and I ran into some troubles that I've partly tracked down. I setup auth/user dbs with LDAP initially, and things worked well. Passwords are stored as "{crypt}zxcv..." in LDAP. I setup SQL, and began getting this: dovecot: Jan 23 16:37:47 Error: child 8718 (auth-worker) killed with signal 11

http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz http://dovecot.org/releases/dovecot-1.0.rc23.tar.gz.sig Documentation is probably the only important thing left before v1.0. * deliver doesn't ever exit with Dovecot's internal exit codes anymore. All its internal exit codes are changed to EX_TEMPFAIL. * mbox: X-Delivery-ID header is now dropped when saving mails. * mbox: If