similar to: buildpkg.sh enhancements

Here is a small patch for OpenSSH 3.2.3p1.. When the package postinstall script runs, it presumes that the package will be installed relative to the current / directory.. If this package is installed as part of a Solaris Jumpstart installation, this will not be the case. Consequentially, the /etc/ssh/sshd_config.default will never get copied to /etc/ssh/sshd_config on the new operating system.

Can someone else from the Solaris realm that uses our package system verify that this should be done? It looks right, but I want another opinion before commiting. - Ben > On Wed, 27 Feb 2002, Antonio Navarro wrote: > >> Hi Ben, >> >> I have made some modifications to the buildpkg.sh script that is >> distributed with openssh. >> >> I am sending it to

Greetings all, See below for postinstall and remove scripts for the above release for those who may have wondered why they didn't work. Minor changes, but those below work. Find these scripts in ../samba-1.9.18p10/packaging/Solaris/pkg-specs. Regards Anthnoy :::::::::::::: postinstall :::::::::::::: #!/bin/sh # install samba nawk '/^netbios-[ns]*[ ]/ {next} {print} END { print

I've attached a patch for contrib/solaris package builder to bring it up to date with OpenSSH 2.9p1. The changes are: build-pkg - add libexec/ directory creation (to house sftp-server) cp sftp-server to libexec/ cp sftp.1 to man/man1 cp sftp to bin/ postinstall.in - add RSA key generation and installation/update prototype - add sftp, sftp.1 and sftp-server Btw, 2.9p1 is

Hi. Solaris packages created by buildpkg.sh don't create privsep user or group and sshd won't start until they are created (or privsep is disabled): ## Executing postinstall script. starting /usr/local/sbin/sshd... Privilege separation user sshd does not exist /etc/init.d/opensshd: Error 255 starting /usr/local/sbin/sshd... bailing. The attached patch (against -cvs) ports the relevant

SecureComputing's PAM library doesn't pass back the correct context to the pam_conversation function, i.e. it passes back NULL. So this patch works around this fact. likely you'll only want this hack if you expect to use pam_safeword.so in your authentication check, and only if you run sshd in privilege separation (separate process) mode so that the PAM conversation is single

Hello everybody, I have written a shell script that makes the building of a Solaris package of rsync easier. Because I think it is useful for other Solaris user, I wold be very happy, if somebody would include it to the source tree. There is one little things to do: - include it in the auto-configuration process, so that the version number will be set correctly. So far, Jens ----- Script

(Shame on me: wrong filename in last posting, now here are correct diffs) in contrib/solaris/ (openssh-SNAP-20011017.tar.gz) 1) buildpkg.sh makes wrong link for /etc/init.d/opensshd 2) /etc/init.d/opensshd has not-working killproc here my version tested on Solaris 2.4 and 8 (no pgrep with solaris 2.4, XARGS was undefined, simpler syntax) J?rg --- contrib/solaris/buildpkg.sh Fri Oct 12

Hi, thanks for this great work. Just a minor point - maybe you should mention the rm -rf $FAKE_ROOT command within your README file: It caught me unexpected and I was looking a couple of minutes for the package artifact before I actually read the last line. Regards, Burkhard Kohl Lead Engineer Content Management burkhard.kohl at intershop.de INTERSHOP? http://www.intershop.de INTERSHOP

I've just commited the patch below to buildpkg.sh.in to HEAD Just in case anyone is using "make package" to build a SVR4 style package, I thought I'd give a heads the default name for $POST_MAKE_INSTALL_FIXES has changed. --- buildpkg.sh.in.old 2005-12-28 14:24:55.856729016 -0800 +++ buildpkg.sh.in 2006-02-12 10:04:06.383475017 -0800 @@ -35,7 +35,7 @@ SYSVINITSTART=S98

Hi *, I have set up a very simple asterisk configuration where I intend to be redirected to the voicemail whenever I dial 100 with my kphone SIP client. The problem is that asterisk can not find the stream 'vm-theperson'. I have made a non-standard installation (since I am just testing), and that file is located in /mnt/tr2/fake_root/installed/usr/local/var/lib/asterisk/sounds. 1. How

Hello All, Attached is a patch makes the following changes to contrib/aix relative to 3.1p1: * Gets version number from ssh -V as suggested by Tim Rice. * Does a better job of generating valid AIX package version numbers (fixes inutoc "format of the toc file is invalid" and "invalid level" errors reported by Mandar Mirashi). * Tests for "make install" failure and

Hello All, This is a resend of a patch I posted nearly two weeks ago. As of a few minutes ago, it hasn't been committed and thus the AIX package builds from CVS fail. (I know because I now have a cron job that tells me :-) Could someone please review and commit the attached patch and chmod a+x contrib/aix/*.sh, or let me know what needs to be changed? It makes the following changes

Not that I''m much of a Solaris guy, and definitely not a Solaris 10 guy, but since nobody else had posted anything yet: http://reductivelabs.com/trac/puppet/wiki/PuppetSolaris#Solaris10 The good news is that it appears to be a completely hands-off puppetd installation. Just sign the client key afterwards on the puppetmaster and you''re set. The bad news is that it''s

apt-get install svn-buildpackage cat <<_eof >> ~/.svn-buildpackage.conf svn-lintian svn-linda svn-move _eof mkdir logcheck; cd logcheck svn co svn+ssh://svn.debian.org/svn/logcheck/logcheck/trunk cd trunk svn-buildpackage -k<your key ID> -rfakeroot man svn-buildpackage for more. Nice, huh? -- .''`. martin f. krafft <madduck at debian.org> : :' :

Dave St John wrote: > Before the official release of icecast2 1.0 (non beta) i would like to see > pid file management, > ive discussed this before on how to capture the pid, but ended up with alot > of bash rigamaroo that mounted to even more > headaches. If I understand you correctly, all you want is the PID of the Icecast process and not of its children (probably to be able to

dont worry Dave, it'll be committed soon and will be in the next beta...definately in 2.0 oddsock At 03:43 PM 12/1/2003 -0700, you wrote: >Thanks for the snippet, albeit id still like to see it added :) > > > PID files are quite useless junk on the harddisk in most cases... IMO > > they make only sense if you have to run a program in the foreground and > > send

Thanks for the snippet, albeit id still like to see it added :) > PID files are quite useless junk on the harddisk in most cases... IMO > they make only sense if you have to run a program in the foreground and > send signals like SIGUSR1 to it (those that don't have hotkeys like > CTRL+C). Besides, they come with their own set of potential problems. > Anyways - Icecast2 is very

Hi, I need help because I can't install Nut in RedHat EL 6.6 The version of Nut in repository ot RHEL is 2.6.5-2, but doesn't suppor my UPS, Liebert GXT3-200RT. I read that it is supported using Nut version 2.7.2, but I looking all around the web how to install it in my RedHat but I didn't find answers. Follow the guide, I can downlad lasted version stable on web: 2.7.2 Here the

https://bugzilla.mindrot.org/show_bug.cgi?id=1629 Summary: allow --port=#### option at configuration time? Product: Portable OpenSSH Version: 5.2p1 Platform: Other OS/Version: Other Status: NEW Severity: enhancement Priority: P2 Component: Build system AssignedTo: unassigned-bugs at mindrot.org