search for: basedef

...andards >> problem. > > > That's not how the RFC rules are defined. But, rather than argue that > point at length, I'd point out that Open Group standards for usernames > are simple and will comply with the SMTP RFCs: > http://pubs.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_426 > > That is, [A-Za-z0-9._][A-Za-z0-9._-] > _______________________________________________ > CentOS mailing list > CentOS at centos.org > https://lists.centos.org/mailman/listinfo/centos > I think there is a mis-understanding. All I was looking for...

...return an entry with a 0 inode number. Is that historically? - Second, POSIX does not demand the existence of the d_ino member in dirent. Only systems which claim to be X/Open compatible are required to have the d_ino member in dirent. See http://www.opengroup.org/onlinepubs/009695399/basedefs/dirent.h.html and http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap02.html#tag_02_01_04 Since it's fairly tricky and time consuming to generate the correct inode number when running the Windows equivalent of readdir, the d_ino entry was faked in Cygwin by using a n...

..._ -" "The <hyphen> character should not be used as the first character of a portable user name." This allows a bit more things that NAME_REGEX though, but this still looks fine to me. For more info, see: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_431 http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_278 -- You are receiving this mail because: You are watching all bug changes. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.netfilter.or...

...request / suggestion for the latter group: use "8.3" > whenever possible. I will add a little reminder, maybe off topic. Assuming that we are trying to be as much POSIX compliant as possible, we could follow theses recommendations, cf. http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap03.html#tag_03_278 <quote> 3.278 Portable Filename Character Set The set of characters from which portable filenames are constructed. A B C D E F G H I J K L M N O P Q R S T U V W X Y Z a b c d e f g h i j k l m n o p q r s t u v w x y z 0 1 2 3 4 5 6 7 8 9 . _ - The last three ch...

On 04/30/2016 12:22 PM, Gordon Messmer wrote: > On 04/30/2016 11:28 AM, Alice Wonder wrote: >> Is there any advice on characters to allow in usernames? > ... >> I don't think a whitelist alphabet is best approach because of people >> with names that are not spelled with Latin characters. >> >> Is there an existing blacklist of characters that technically

...socket=$sock URIs; any reason we aren't using them here? > +++ b/tests/test-shutdown-plugin.c > + > +static int64_t > +shutdown_get_size (void *handle) > +{ > + return INT64_C (1024*1024); This looks fishy. POSIX says that: https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/stdint.h.html#tag_13_48 "The argument in any instance of these macros shall be an unsuffixed integer constant with a value that does not exceed the limits for the corresponding type. ...For example, if uint_least64_t is a name for the type unsigned long long, then UINT64_C(0x123) might exp...

Hello, I am working on replacing atoi () and atol() functions with strtol() and strtoul() . I came across many files which uses statement like these time_t secs= atoi(data_span.c_str()), here time_t Datatype is not known but wikipedia says that it is integer so is it necessary to replace atoi with strtol over here ?? And is their any document which helps me what each file function does like

...gt; >>> That's not how the RFC rules are defined. But, rather than argue that >>> point at length, I'd point out that Open Group standards for usernames >>> are simple and will comply with the SMTP RFCs: >>> http://pubs.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_426 >>> >>> That is, [A-Za-z0-9._][A-Za-z0-9._-] >>> _______________________________________________ >>> CentOS mailing list >>> CentOS at centos.org >>> https://lists.centos.org/mailman/listinfo/centos >>> >&...

...ot allowed in a username is a standards > problem. That's not how the RFC rules are defined. But, rather than argue that point at length, I'd point out that Open Group standards for usernames are simple and will comply with the SMTP RFCs: http://pubs.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_426 That is, [A-Za-z0-9._][A-Za-z0-9._-]

...>> >> >> That's not how the RFC rules are defined. But, rather than argue that >> point at length, I'd point out that Open Group standards for usernames >> are simple and will comply with the SMTP RFCs: >> http://pubs.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_426 >> >> That is, [A-Za-z0-9._][A-Za-z0-9._-] >> _______________________________________________ >> CentOS mailing list >> CentOS at centos.org >> https://lists.centos.org/mailman/listinfo/centos >> > > I think there is a m...

...> That's not how the RFC rules are defined. But, rather than argue that >>>> point at length, I'd point out that Open Group standards for usernames >>>> are simple and will comply with the SMTP RFCs: >>>> http://pubs.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap03.html#tag_03_426 >>>> >>>> >>>> That is, [A-Za-z0-9._][A-Za-z0-9._-] >>>> _______________________________________________ >>>> CentOS mailing list >>>> CentOS at centos.org >>>> https://lists.centos.org/m...

Hi, I have broken my OS (FreeBSD) after upgrade, making me unable to compile dovecot the usual way so I am seeking a 3rd eye. The config.log is at : http://bit.ly/2jE5djl Hoping someone can help me figure out what is broken. During configure, it fails with: checking for special C compiler options needed for large files... no checking for _FILE_OFFSET_BITS value needed for large files...

...lt; 3.0.16 behavior. This issue was seen in Buildroot Linux, in [5]. [1] https://sourceforge.net/p/gnu-efi/code/ci/189200d0b0f6fff473d302880d9569f45d4d8c4d [2] https://repo.or.cz/syslinux.git/blob/refs/tags/syslinux-6.03:/com32/include/stddef.h [3] https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/stddef.h.html [4] https://repo.or.cz/syslinux.git/blob/refs/tags/syslinux-6.03:/mk/efi.mk#l27 [5] https://lists.buildroot.org/pipermail/buildroot/2024-February/685971.html Signed-off-by: Julien Olivain <ju.o at free.fr> --- com32/include/stddef.h | 2 ++ 1 file changed, 2 insertions(+) di...

Why does inserting an empty quote ("") into a rsync command cause the current directory to be backed up? Not sure if this is a UNIX-syntax question or rsync-syntax question. Code: #!/bin/sh echo "\nspace between quotes has no effect; only music is backed up:" rsync -ilrtn " " /home/wolf/music /backups/backup1 echo "\nempty quotes backs up current directory

(R 2.8.0 on Debian GNU/Linux sid) ?file.info contains: mtime, ctime, atime: integer of class '"POSIXct"': file modification, creation and last access times. This implies that ctime is "file [...] creation [...] time" Has R implemented ctime differently to Unix? I understand, on Linux at least, that ctime is the last change time (not the creation time).

...delines for what goes in r-help and what in r-devel are clear enough without actively discouraging discussion of classes and methods. It's the nature of the question, not a litmus test for discussing this or that package that is the helpful distinction. .... > if (is.primitive(baseDef)) { > value <- genericForPrimitive(f) > > and it seems John Chambers has defined an S4 generic for as.character > with one arg, "x". Had he not done so it would have been (x, ...). My > guess is that this is because in S the arg list is (x) and he overloo...

...c: link_stat "/tela/downloads" failed: No such file or directory (2) rsync error: some files/attrs were not transferred (see previous errors) (code 23) at /home/lapo/packaging/rsync-3.0.4-1/src/rsync-3.0.4/main.c(1506) [receiver=3.0.4] ]]] http://www.opengroup.org/onlinepubs/000095399/basedefs/xbd_chap04.html#tag_04_11 mentions that "[a] pathname that begins with two successive slashes may be interpreted in an implementation-defined manner, although more than two leading slashes shall be treated as a single slash." The attached patch prevents two leading slashes from being...

..._IN_UTMPX if (utx->ut_type == USER_PROCESS) return (1); %%% It changes all uses of ut_name on utmpx structures to ut_user. Any chance this can go into CVS? Merry christmas, -- Ed Schouten <ed at 80386.nl> WWW: http://80386.nl/ [1] http://www.opengroup.org/onlinepubs/9699919799/basedefs/utmpx.h.html -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 196 bytes Desc: not available URL: <http://lists.mindrot.org/pipermail/openssh-unix-dev/attachments/20091225/eaa1565b/attachment.bin>

Hi all, I am running Xen 4.1.2 with ubuntu Dom0. I have essentially got 1000 Modified Mini-OS DomU''s running at the same time. When i try and access the 1000th domain console: xm console DOM1000 xenconsole: could not read tty from store: No such file or directory The domain is alive and running according to xentop, and has been for some time. I can successfully access the first 338

Hi all, I am running Xen 4.1.2 with ubuntu Dom0. I have essentially got 1000 Modified Mini-OS DomU''s running at the same time. When i try and access the 1000th domain console: xm console DOM1000 xenconsole: could not read tty from store: No such file or directory The domain is alive and running according to xentop, and has been for some time. I can successfully access the first 338