Hello,
On 2014-01-15 00:17:22 -0600, David C. Rankin wrote:
> I apologize if you get two of these reports, but my server responded that
> the
> mail did not go through when I exited vi. Here is the contents generated by
> bashbug about the line wrap issue when including \t, \T or \A at beginnin
Hello,
On 2014-01-15 00:17:22 -0600, David C. Rankin wrote:
> I apologize if you get two of these reports, but my server responded that
> the
> mail did not go through when I exited vi. Here is the contents generated by
> bashbug about the line wrap issue when including \t, \T or \A at beginnin
Dear Bash gurus,
I apologize if you get two of these reports, but my server responded that the
mail did not go through when I exited vi. Here is the contents generated by
bashbug about the line wrap issue when including \t, \T or \A at beginning of
PS1.
Configuration Information [Automatically
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/local
Yes, my main issue is that there are many computers connecting to one server.
Puppet is way above my pay scale and I decided to give up learning it.
Indeed this is way out of scope for this list but the right thing to do is
to set up SSH IdentityFiles. "man ssh_config" and read about IdentityFile
directive and also man ssh-keygen. For more information a quick google
search will pop up millions of easy tutorials.
If your problem is that you hav
The files in question are generated on the server and cannot be generated on
each machine. I need a way to distribute them and they are keyed to each
machines serial number.
They are security keys for talking to a third server.
The files in question are generated on the server and cannot be generated on
each machine. I need a way to distribute them and they are keyed to each
machines serial number.
probably out of scope of @bash, anyway:
On Tue, Jan 14, 2014 at 05:08:08AM -0800, janeit...@rockingham.k12.va.us wrote:
> Is there a way to log into a server without using passwords coded into
> the script?
Does it means that access to your script isn't safe ?
Couldn't `chmod 700` do the trick in
Is there a way to log into a server without using passwords coded into the
script?
I'm trying to retrieve files from a server for every computer I have based on
the serial number of the machine.
This is what I have so far. (I'm very new to bash. Any advice would be helpful)
#!/bin/sh
myseria
On 1/13/14 10:25 AM, Audrius Butkevicius wrote:
> Bash Version: 4.2
> Patch Level: 45
> Release Status: release
>
> Description:
>
> Login shell not setting HOME variable when using -l option,
> but is set when using - as argument zero. This is not
> differentiated in the
> > * Ability to link with patches. In fact, github allows submitters to attach
> > a patch, and admin can just merge it in with one click, provided there are
> > no conflicts.
>
> The number of issues we get with patches already attached are few. The
> number of patches that are applied verbatim,
12 matches
Mail list logo
