similar to: SAMBA HOWTO: time displayed in UNIX file listing

On 26 Oct 2013 08:38, "Tim R?hsen" <tim.ruehsen at gmx.de> wrote: [...] > With this change, the regression test fails (ssh dumps core). > 'addrs' stays NULL but is freed unconditionally a few lines further down. What platform is this on? POSIX says free(NULL) is a no-op. http://pubs.opengroup.org/onlinepubs/000095399/functions/free.html

On 04/30/2016 08:56 PM, Gordon Messmer wrote: > On Sat, Apr 30, 2016 at 12:44 PM, Alice Wonder <alice at domblogger.net> wrote: >> >> For e-mail sent to people, yes. >> >> But for what usernames are allowed when creating an account, I don't see why >> blacklisting characters that are not allowed in a username is a standards >> problem. > >

On 05/01/2016 01:57 AM, Leon Fauster wrote: > Am 01.05.2016 um 06:43 schrieb Alice Wonder <alice at domblogger.net>: >> On 04/30/2016 08:56 PM, Gordon Messmer wrote: >>> On Sat, Apr 30, 2016 at 12:44 PM, Alice Wonder <alice at domblogger.net> wrote: >>>> >>>> For e-mail sent to people, yes. >>>> >>>> But for what

sshd will die from an unhandled SIGALRM if you allow SSH1 connections, ssh in, HUP sshd, and don't ssh in again for KeyRegenerationInterval. The HUP handler calls exec which resets signal handlers but persists alarm timers. Chapter and verse: http://www.opengroup.org/onlinepubs/000095399/functions/alarm.html -- Andrew Gaul http://gaul.org/ -------------- next part -------------- Index:

sshd will die from an unhandled SIGALRM if you allow SSH1 connections, ssh in, HUP sshd, and don't ssh in again for KeyRegenerationInterval. The HUP handler calls exec which resets signal handlers but persists alarm timers. Chapter and verse:

On Sat, Apr 30, 2016 at 12:44 PM, Alice Wonder <alice at domblogger.net> wrote: > > For e-mail sent to people, yes. > > But for what usernames are allowed when creating an account, I don't see why > blacklisting characters that are not allowed in a username is a standards > problem. That's not how the RFC rules are defined. But, rather than argue that point at

Am 01.05.2016 um 06:43 schrieb Alice Wonder <alice at domblogger.net>: > On 04/30/2016 08:56 PM, Gordon Messmer wrote: >> On Sat, Apr 30, 2016 at 12:44 PM, Alice Wonder <alice at domblogger.net> wrote: >>> >>> For e-mail sent to people, yes. >>> >>> But for what usernames are allowed when creating an account, I don't see why

On 05/01/2016 05:10 AM, Alice Wonder wrote: > On 05/01/2016 01:57 AM, Leon Fauster wrote: >> Am 01.05.2016 um 06:43 schrieb Alice Wonder <alice at domblogger.net>: >>> On 04/30/2016 08:56 PM, Gordon Messmer wrote: >>>> On Sat, Apr 30, 2016 at 12:44 PM, Alice Wonder >>>> <alice at domblogger.net> wrote: >>>>> >>>>>

Dear all, During a recent package submission, we were highlighted that some lines in our configure script didn't follow the correct syntax. The lines looked like this: x=$(($y/10)) We were indicated at the time that this is because the statement does not use Bourne shell syntax, which is absolutely true, and also that the manual warns about this, which is true again. So far everything

rsync 3.0.4 will transform a path like '//machine/share/dir' to '/machine/share/dir' when the --protect flag is provided. This causes a problem with Cygwin, where the two leading slashes are meaningful (access of a remote Windows share). [[[ % rsync -s localhost://tela/downloads rsync: link_stat "/tela/downloads" failed: No such file or directory (2) rsync error: some

https://bugzilla.netfilter.org/show_bug.cgi?id=1037 Pablo Neira Ayuso <pablo at netfilter.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #1 from Pablo Neira Ayuso

Hi, There's exactly one usage of the dirent.d_ino member in the whole project, which is in the readdir loop in scp.c, like this: while (readdir) { if (d_ino == 0) continue; [...] } This loop is basically taken from rcp.c as far as I can see. However, I have two problems here. - First, I have no idea why and when readdir should return an entry with a 0 inode number. Is

For what it's worth, Autoconf does not assume that arithmetic expansion will be available. Instead, it emits the following shell code: if ( eval 'test $(( 1 + 1 )) = 2' ) 2>/dev/null; then eval 'func_arith () { func_arith_result=$(( $* )) }' else func_arith () { func_arith_result=`expr "$@"` } fi 2017-12-17 23:55 GMT+01:00 Rodrigo Tobar

I do not have a dog in this fight, but I have to ask: How much person time is worthwhile to invest in supporting Solaris 10? It has been closed-source (Post-Oracle) <https://en.wikipedia.org/wiki/Solaris_(operating_system)#Post-Oracle_closed_source_(Solaris_10_after_March_2010,_and_Solaris_11_(2011_and_later))> since March 2010. On Mon, Dec 18, 2017 at 1:23 PM, Kurt Hornik

Commit-ID: e168c38081489046ec1dc612597b718a5adee74c Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=e168c38081489046ec1dc612597b718a5adee74c Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 29 Sep 2014 22:52:41 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Fri, 25 Jan 2019 02:57:21 +0000 [klibc] [PARSER] Handle

On Tue, Jan 31, 2023 at 01:49:53PM +0100, Laszlo Ersek wrote: > On 1/28/23 13:47, Richard W.M. Jones wrote: > > systemd allows sockets passed through socket activation to be named > > with the protocol they require. We only ever pass one socket, name > > it. This environment variable is currently ignored by qemu-nbd and > > nbdkit, but might be used by

Commit-ID: 0b425be3b607419cc27bdab4de3f9178b637c7c7 Gitweb: http://git.kernel.org/?p=libs/klibc/klibc.git;a=commit;h=0b425be3b607419cc27bdab4de3f9178b637c7c7 Author: Herbert Xu <herbert at gondor.apana.org.au> AuthorDate: Mon, 29 Sep 2014 22:52:41 +0800 Committer: Ben Hutchings <ben at decadent.org.uk> CommitDate: Sat, 28 Mar 2020 21:42:54 +0000 [klibc] dash: [PARSER] Handle

On 1/28/23 13:47, Richard W.M. Jones wrote: > systemd allows sockets passed through socket activation to be named > with the protocol they require. We only ever pass one socket, name > it. This environment variable is currently ignored by qemu-nbd and > nbdkit, but might be used by qemu-storage-daemon: > > https://lists.nongnu.org/archive/html/qemu-devel/2023-01/msg06114.html

>>>>> I?aki ?car writes: Same from here: in addition to what the standards say, it always pays to be defensive and check "Portable Shell Programming" in the Autoconf manual. Among other things, this says '$((EXPRESSION))' Arithmetic expansion is not portable as some shells (most notably Solaris 10 '/bin/sh') don't support it. motivating

On Sun, Apr 11, 2010 at 2:41 PM, Kenneth Uildriks <kennethuil at gmail.com> wrote: > On Sun, Apr 11, 2010 at 4:09 PM, Jeffrey Yasskin <jyasskin at google.com> wrote: >> Kenneth Uildriks <kennethuil at gmail.com> wrote: >>> As I see it, the context switching mechanism itself needs to know >>> where to point the stack register when switching.  The C