Re: Google calendar API limit
On Sat, 2016-09-17 at 07:34 -0600, Greg Woods wrote: > Google *Is* trying to discourage use of IMAP. They want everyone to use > their API's (via the web interface or a Gmail-specific app). Their tech > support people have told us this much. Whether they are actually causing > failures to discourage IMAP use is, of course, pure speculation. All I can > say there is that there are people who believe they are doing this based on > their own tests. Anecdotal evidence only. Take it for what it's worth. Just to follow up on this, the Google Developer's documentation on the Gmail API (https://developers.google.com/gmail/api/guides/) explicitly states that "The Gmail API should not be used to replace IMAP for full- fledged email client access. Instead, see IMAP and SMTP". They further state (https://developers.google.com/gmail/imap_extensions) that "Gmail provides a set of IMAP extensions to allow authors of IMAP clients provide a more Gmail-like experience through IMAP. Developers integrating Gmail features into their web or mobile apps may instead want to use the RESTful Gmail API." To paraphrase: if you want to use Gmail via a web app, use their API. If you want to use it via a client program, use IMAP. Seems fairly unambiguous to me. poc ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Anacron mail -
Have you considered installing something like IMAP on that machine to make mail more convenient to read? Boris. On Sat, Sep 17, 2016 at 12:25 PM, Bob Goodwin wrote: > > I have been using Linux for a long time and have yet to see a cron/anacron > mail message. > > In [root@Box10 bobg]# cat /etc/aliases I configured: > > # Person who should get root's mail > root:bobg > > And after a bit of googling I dnf installed mail. Mail is difficult to > use, has a long list of commands, but it did display about five hundred > messages of which it displays several pages and stops, those are old from a > couple of months ago while today's messages are all I am interested at the > moment. > > Is there a command to display only what I want, a specific day or perhaps > reverse the order so that today's messages are at the top, display first? > Better yet I would think would be to display them in Thunderbird but I > don't know how to do that ... > > Any help appreciated, > > Bob > > -- > Bob Goodwin - Zuni, Virginia, USA > http://www.qrz.com/db/W2BOD > box10 FEDORA-24/64bit LINUX XFCE POP3 > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Driver for RT3072
On 09/17/2016 08:13 PM, stan wrote: On Sat, 17 Sep 2016 18:59:10 -0600 jd1008 wrote: What is the driver's (or drivers') name (or names) for RT3072 which a usb dongle. This should get you going - rt2800usb https://wireless.wiki.kernel.org/en/users/drivers/rt2800usb OK, so I rebooted and then plugged in the rt3702 dongle dmesg shows: [ 3270.106423] usb 4-1.2: new high-speed USB device number 14 using ehci-pci [ 3270.210079] usb 4-1.2: New USB device found, idVendor=148f, idProduct=3072 [ 3270.210085] usb 4-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 3270.210088] usb 4-1.2: Product: 802.11 n WLAN [ 3270.210091] usb 4-1.2: Manufacturer: Ralink [ 3270.210094] usb 4-1.2: SerialNumber: 1.0 [ 3270.212400] === pAd = c90018175000, size = 598032 === [ 3270.212458] <-- RTMPAllocAdapterBlock, Status=0 [ 3270.213176] NVM is EFUSE Yet, there is no interface for ifcfg to play with :( ifcfg shows only: ifconfig em1: f lo: virbr0: wlp2s0b1: This is built-in to the mobo: 02:00.0 Network controller: Broadcom Corporation BCM43224 802.11a/b/g/n (rev 01) <<< built-in to mobo. So, the dongle is not visible to what It's driver? It's driver module is loaded. To wit: $ lsmod | grep rt5572sta rt5572sta 810817 0 Notice the driver module has no client drivers attached to it (as indicated by the trailing 0). PS: The driver source code does not name the driver module as rt3072.ko , So, it is not clear to me if it actually built a driver for that chipset. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: a stop job is running....
On Sun, Sep 18, 2016 at 9:58 AM, François Patte wrote: > Le 17/09/2016 22:53, Jon LaBadie a écrit : >> On Sat, Sep 17, 2016 at 11:34:54AM -0500, Rex Dieter wrote: >>> Tom Horsley wrote: >>> Because systemd has a gazillion bugs like this >>> >>> In cases like this in general, it's not systemd, >>> but the individual services that have bugs. >>> >> Does anyone else tire of hearing >> "its not systemd, its ..." > > I have no idea about this and systemd in general I have four > computers running under fedora systemd: a desktop under f21, no problem > of the like; sometimes I get this message: "a start job is running" > about some partitions installed on two disks in a raid-1 array, that I > added to the main system after the install. I suspect that it is an fsck > check but, systemd gives no info on the boot screen about this and I did > not check in the huge journal... > > two laptops under f23 with no problems abo some running jobs (start or stop) > > and one laptop under f24 which has these problems. What can we say? > there are bugs in fc 24 installation of systemd? These stop problems can > come from the way journalctl write in the /var partition: both partition > /var and /usr fail to be unmounted at shutdown (they are separate > partitions from /), is it because journalctl wants to write the logs > until the last second and the shutdown process wants to umount these two > partitions too earlier? I am not able to answer and solve these > problems... But are they systemd problems or a fedora configuration of > systemd problem? > > Who knows? The problem is there is some process in the user session that isn't quitting, and systemd doesn't force quit it for 1m30s at which time it obliterates the user session and everything running in it. You can use loginctl to list the contents of the user session, but in my experience I often can't get to a different tty to check on this. You can try one of two things: 1. Log out, then restart or shutdown. For whatever reason this works for me maybe 1/2 the time or more. 2. Edit /etc/systemd/logind.conf such that KillUserProcesses=yes i.e. remove the # that's currently there by default. This was slated to be the default for Fedora 25 but the feature has other consequences, namely it would kill screen and tmux in your user session also and so there are some unfinished work arounds to make those things use different scopes or sessions or whatever they're called. Just realize with this option set to use, literally everything running in your user session will get killed off. There is a way to use systemd-run blah blah you'll have to read about it, to launch tmux in a different session that doesn't get killed off. I have no idea how you reconnect to it, if anything else is different other than just running it that way because I haven't tried it. I have found some other things like btrfs balance and scrub, which can take hours or days, will get killed off also and I'm working with upstream Btrfs folks on a work around for that also, because the real work is done by the kernel so the operation isn't killed so much as the user process. So the user process needs to be killable and then able to reconnect to check status, pause or cancel correctly. -- Chris Murphy ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: Driver for RT3072
On 09/17/2016 08:13 PM, stan wrote: On Sat, 17 Sep 2016 18:59:10 -0600 jd1008 wrote: What is the driver's (or drivers') name (or names) for RT3072 which a usb dongle. This should get you going - rt2800usb https://wireless.wiki.kernel.org/en/users/drivers/rt2800usb Thank you Stan. I downloaded it, read the README for how to build, followed the instructions for modifying Makefile and os/linux/config.mk ran make. Had to fix a data structure in order for it to compile (a trivial mod). It built just fine. ran insmod tried to ifconfig the interface up. interface not found. Will retry and get back to ya. Cheers, JD ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: a stop job is running....
Le 17/09/2016 22:53, Jon LaBadie a écrit : > On Sat, Sep 17, 2016 at 11:34:54AM -0500, Rex Dieter wrote: >> Tom Horsley wrote: >> >>> Because systemd has a gazillion bugs like this >> >> In cases like this in general, it's not systemd, >> but the individual services that have bugs. >> > Does anyone else tire of hearing > "its not systemd, its ..." I have no idea about this and systemd in general I have four computers running under fedora systemd: a desktop under f21, no problem of the like; sometimes I get this message: "a start job is running" about some partitions installed on two disks in a raid-1 array, that I added to the main system after the install. I suspect that it is an fsck check but, systemd gives no info on the boot screen about this and I did not check in the huge journal... two laptops under f23 with no problems abo some running jobs (start or stop) and one laptop under f24 which has these problems. What can we say? there are bugs in fc 24 installation of systemd? These stop problems can come from the way journalctl write in the /var partition: both partition /var and /usr fail to be unmounted at shutdown (they are separate partitions from /), is it because journalctl wants to write the logs until the last second and the shutdown process wants to umount these two partitions too earlier? I am not able to answer and solve these problems... But are they systemd problems or a fedora configuration of systemd problem? Who knows? -- François Patte UFR de mathématiques et informatique Laboratoire CNRS MAP5, UMR 8145 Université Paris Descartes 45, rue des Saints Pères F-75270 Paris Cedex 06 Tél. +33 (0)1 8394 5849 http://www.math-info.univ-paris5.fr/~patte signature.asc Description: OpenPGP digital signature ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
Re: DHCP: how to manage dynamic address for the hosts in a network
On Thu, 2016-09-15 at 12:05 +0200, Peter Boy wrote: > you can manually assign fix IP addresses to network devices. You > router will find out by itself about IP addresses in use and won’t > offer them in the DHCP process. How? And under what conditions? If I remember correctly, a DHCP server doesn't check that an IP address is in use, other than what it already knows about through its own database (this "checking if it's free" behaviour depends on how the DHCP server was programmed - whether it does any checks, or just assumes that it's the god of IP address assignments). You'd have to rely on a client being given an address, it trying it, and it refusing it if it (the client) finds an error (which it may not do if the first client to have that IP doesn't respond, or respond quick enough). If by in-use, you mean currently in-use, then a DHCP server may or may not know about some other device using that IP (and that may depend on network topology), and may work around it. For instance, if my DHCP server tried to give out 192.168.1.20 to some second device when it's already in use on my LAN (but that first device wasn't given that address by the DHCP server), it'll try to give out that IP to the second device, and it's only network errors that are going cause a problem. But, an address that another computer, for example, uses when its turned on, but is currently turned off, is not currently in-use, even if you did want it reserved. If you want things to have predictable IPs, you do need to fix them, not rely on good luck. If you're mixing static and dynamic IPs, you really need to pre-program the DHCP server to handle that. e.g. Tell the DHCP server that it can freely assign IPs in a range (like 192.168.1.100 to 192.168.1.199) to any random device, and you make sure that any static IPs that you set up are outside of that range. That applies whether you manually configure individual devices to use static IPs, or centrally use a DHCP server to give predetermined IPs to specific devices. On my LAN, I have four ranges of IP addresses within one subnet that I reserve for different purposes, and the DHCP server is configured accordingly: Static IPs configured in important devices (e.g. servers, routers), that need to be self-configuring, independent of any DHCP server that may not be available as they boot up. e.g. x.y.z.1 to x.y.z.50 Fixed IPs that are always assigned to the same devices by the DHCP server, for the usual client machines on the LAN. I want these devices to always have the same IP, for the sake of less headaches, but I want to centrally manage them. So the DHCP server is set to always give out the same IPs to the devices recognised by their MACs (network hardware). e.g. 192.168.1.51 to 192.168.1.100 Random dynamic IPs available to irregularly connected devices., for visiting, drop-in test machines, unimportant devices, that I don't care what their address is. They're generally only clients, and nothing else will need to connect *to* them. This lets random things (internet radios, games, whatever), simply work when plugged in. This is the only range that the DHCP is allowed to dole out randomly. e.g. 192.168.1.101 to 192.168.1.200 Spare IPs, that I may use when dealing with debugging devices. I can freely set a device to use an IP in this range, knowing that there's not going to be a bunfight with the DHCP server, and that nothing else should be using them. e.g. 192.168.1.201 to 192.168.1.253 They're all on the same subnet, and can all work with each other. The router (internet gateway) offers an isolated second subnet, so that visitors could get onto the internet without any ability to mess with the LAN (the router provides firewalling, as well as the network addressing causing sub-net isolation). e.g. 192.168.2.100 to 192.168.2.200 Networks can be as simple, or as complex as you need them to be. But messy "I don't know what I'm doing, and I'll randomly try things that seem to work" just causes all sorts of headaches, sometimes immediately, sometimes quite later. -- tim@localhost ~]$ uname -rsvp Linux 3.19.8-100.fc20.i686 #1 SMP Tue May 12 17:42:35 UTC 2015 i686 All mail to my mailbox is automatically deleted, there is no point trying to privately email me, I will only read messages posted to the public lists. George Orwell's '1984' was supposed to be a warning against tyranny, not a set of instructions for supposedly democratic governments. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org
how to correctly log without journald (and its blobs)?
In previous Fedora distros was (IMHO) right way to log only to syslog,
without journald and its (for me) unwanted annoying binary logs, by using
configuration as:
*) Set systemd log target to syslog:
systemd.log_target=syslog (syslog-or-kmsg) on kernel cmdline
systemd.default_standard_output=syslog --/
and
LogTarget=syslog in systemd.conf
DefaultStandardOutput=syslog--/
*) configuring rsyslog to listen on /dev/log unix socket:
$SystemLogSocketName /dev/log -- in rsyslog.conf
$ModLoad imuxsock /
$OmitLocalLogging off ---/
$AddUnixListenSocket /run/systemd/journal/syslog --/(legacy directives)
$AddUnixListenSocket /run/systemd/journal/socket -/
$AddUnixListenSocket /run/systemd/journal/stdout /
(not sure when all last three directives needed)
*) prevent to run journald:
systemctl mask systemd-journald.service
(and maybe mask systemd-journal-flush.service)
And it works fine.
But in actual Fedora 24 in systemd man page values syslog-or-kmsg and
syslog are missing in LogTarget option. As systemd/journald man pages
say hardly anything about exact mean of appropriate configuration for
this purpose, then please when someone more knowledgeable can advise:
- where to direct the systemd output? Maybe to kmsg an then read it in
rsyslog via imklog?
(rsyslog should have also imkmsg module, but is not in rsyslog-8.12.0-3.fc24)
- what about /run/log/journal/.../system.journal ?
On my test F24 system it have open rsyslogd, abrt-dump-journal-oops and
abrt-dump-journal-xorg (no need for these last two) processes. Uses it
also something else?
- what about /run/systemd/journal/{dev-log,socket,stdout} unix sockets?
Should rsyslogd listen on them?
- /dev/log seems be now symlink to /run/systemd/journal/dev-log socket
(as defined by systemd-journald-dev-log.socket) Should it be left
(because now something sends to /run/systemd/journal/dev-log), or can
be /run/systemd/journal/dev-log removed?
Thanks in advance for some clarification about this.
Franta Hanzlik
___
users mailing list -- users@lists.fedoraproject.org
To unsubscribe send an email to users-le...@lists.fedoraproject.org
