similar to: MacOSX & ssh-agent -l

Hi Guys, I'm a newbie, running my first windows app on a Macbook. OS X 10.6.8 2.2 GHz Intel Core 2 Duo 2 GB 667 MHz DDR2 SDRAM When I tried to install X11, both the original X11 app and the update told me it is already installed on my Mac. Here's the error messages from Term: $ wine setup.exe wine: created the configuration directory '/Users/horacemann/.wine' Application tried

On Jun 11, 2017, at 7:15 AM, Robbie van der Walle <rvanderwalle at gmail.com> wrote: > > I see only a reboot. Not a shutdown. But is this normal because shutdown -u -h +0 is used? > To be honest, I haven't experimented much with this, but I saw a normal shutdown/reboot when I just tried this from the command line (10.12): reboot ~ Mon Jun 12 08:36

On Jun 28, 2015, at 10:49 AM, Sundeep Mediratta <smedius at gmail.com> wrote: > I think the high CPU usage was caused by the native OS X driver crashing and not working properly. The native driver was not sensing the UPS going on battery or any change in battery percentage. As you can imagine, if the native driver does not see a change, the macosx-ups driver will not, either.

https://bugzilla.mindrot.org/show_bug.cgi?id=2234 Bug ID: 2234 Summary: ssh-add -l output aborts on unrecognized key, skips flush when stdout not tty Product: Portable OpenSSH Version: 6.6p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component:

I am on my Mac, in Snow leopard, 10.6.8. Whenever I try to use wine to open a program or and application this message comes up in terminal: Dynamic session lookup supported but failed: launchd did not provide a socket path, verify that org.freedesktop.dbus-session.plist is loaded! err:process:__wine_kernel_init boot event wait timed out I have no idea what this means and I cannot find anything

On 30/05/15 08.34, Nico Kadel-Garcia wrote: > On Sat, May 30, 2015 at 8:00 AM, Kasper Dupont > <kasperd at kdxdx.23.may.2015.kasperd.net> wrote: > > As far as I can tell when the ssh command uses an agent to > > authenticate to a server and then forwards an agent to that > > server, it will always use the same agent for both purposes. > > > > Has there

https://bugzilla.mindrot.org/show_bug.cgi?id=1413 Summary: Add support for launching ssh-agent from Mac OS X's launchd. Classification: Unclassified Product: Portable OpenSSH Version: 4.7p1 Platform: Other OS/Version: Mac OS X Status: NEW Severity: normal Priority: P2 Component:

I've figured this one out... Just wanted to get it into the dovecot mailing list archive so that somebody in the future might find it if they need it. Running Dovecot on Mac OS X 10.4.11 and using LaunchDaemon to start. Following a system crash, dovecot failed to restart with this in the system log... Feb 4 10:04:29 G520X2 launchd: org.dovecot: exited with exit code: 89 Feb 4

I was going to experiment with ACLs when I faced a small problem. It is just sufficient to enable the acl plugin for getting the behavior described hereafter. When launching dovecot from the command line, one gets: sh-3.2# /usr/local/dovecot/sbin/dovecot -F ILoading modules from directory: /usr/local/dovecot-1.2.rc6/lib/ dovecot/imap IModule loaded:

Hi , just starting off with Puppet on Macs. initially we are planning for a small group of machines. If successfull we plan to span it to entire environment in a phased manner. I have a couple of newbie questions. Do i have to use custom script to create and maintain user/group accounts as far as i have read i can manage passwords ? Can i use puppet fileserver also as sourcedir for pushing

Hello, I used Lingon for Leopard Server to create a launchd job that would execute the following rsync (v3.0.4) command when logged in as admin at 12:01 AM each day. sudo rsync -aAHvWX /Volumes/File_Storage/docs/ /Volumes/File_Storage_Mirror/docs When launchd executed this command, it did not work. The system.log file reads "Exited with exit code: 1". It called it at 12:01 AM,

https://bugzilla.mindrot.org/show_bug.cgi?id=2598 Bug ID: 2598 Summary: ssh-agent very occasionally won't remove keys or certs despite now() >= lifetime Product: Portable OpenSSH Version: 6.9p1 Hardware: amd64 OS: Mac OS X Status: NEW Severity: minor Priority: P5

https://bugzilla.mindrot.org/show_bug.cgi?id=1700 Summary: ssh-agent dies under high load Product: Portable OpenSSH Version: 5.1p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: ssh-agent AssignedTo: unassigned-bugs at mindrot.org ReportedBy: kernel at

On Sat, May 30, 2015 at 10:38 AM, Phil Pennock <phil.pennock at globnix.org> wrote: > On 2015-05-30 at 15:00 +0200, Kasper Dupont wrote: >> On my laptop I have key1 and key2. I can use key1 to log in >> on server1, and I can use key2 to log in on server2. I want >> neither key to leave the laptop, and only key2 is allowed >> to be forwarded to other hosts. >

I have some Rails apps I use on my Mac to do brutally stupid stuff like track time and activities. They''re always running, but each time I restart, I (duh) have to restart the Mongrels. Well, I know better than that, right? So I dug around in Google to find out how people are getting Mongrels started using Launchd. There are some detailed posts, but none of them seemed to work. My

Hi all, i'm trying to figure out if i'm being silly or if there is a genuine problem. Running on the notorious Redhat 7, 2.2.16-22 #1, X86. [user at host]$ ssh-agent -s SSH_AUTH_SOCK=/tmp/ssh-XXYFcFR6/agent.2101; export SSH_AUTH_SOCK; SSH_AGENT_PID=2102; export SSH_AGENT_PID; echo Agent pid 2102; [user at host]$ echo $SSH_AUTH_SOCK [user at host]$ echo $SSH_AGENT_PID [user at host]$

On Wed, 5 Feb 2020, Phil Pennock wrote: > On 2020-02-06 at 10:29 +1100, Damien Miller wrote: > > * sshd(8): allow the UpdateHostKeys feature to function when > > multiple known_hosts files are in use. When updating host keys, > > ssh will now search subsequent known_hosts files, but will add > > updated host keys to the first specified file only. bz2738 >

http://bugzilla.mindrot.org/show_bug.cgi?id=500 ------- Additional Comments From djm at mindrot.org 2003-02-24 12:43 ------- I think that: [ -z "$SSH_AUTH_SOCK" ] && eval `ssh-agent -s` [ -z "$SSH_AGENT_PID" ] || ssh-add -l >/dev/null 2>&1 || ssh-add Is as effective and a lot more concise. On the other hand, fragile heuristics like: > export

I've just written this patch, it's undergone minimal testing and "works for me" and I'm after feedback as to acceptability of approach, anything I should be doing differently for the feature to be acceptable upstream and what I should be doing about automated testing. Use-case: you have the host's SSH fingerprints via an out-of-band mechanism which you trust and want to

On Fri, Sep 18, 2015 at 7:07 PM, Peter Stuge <peter at stuge.se> wrote: > Fabiano Fid?ncio wrote: >> A few possible solutions for this would involve a way to support more >> than one agent, talking to both (the local one and the spice one), >> merging then their responses and returning it to any application who >> sent the request. Note that would be really nice if